Difference between revisions of "PlanDefinition FHIR Resource Proposal"
Bryn rhodes (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
Bryn rhodes (talk | contribs) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =PlanDefinition= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 26: | Line 26: | ||
* Be consistent with other similar resources | * Be consistent with other similar resources | ||
--> | --> | ||
| + | |||
| + | The PlanDefinition resource represents a pre-defined and approved group of activities to be performed related to a particular clinical condition (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission to Coronary Care Unit). The resource captures metadata about the plan definition, as well as a hierarchical grouping of any number of actions to be taken, each of which describes a specific activity to be performed. | ||
| + | |||
| + | The PlanDefinition resource is definitional in nature, it describes a patient-independent set of activities for a particular setting. In addition, the resource allows for behaviors to be defined for each action, as well as for relationships between the actions to be defined. Conditional logic describing how the plan definition is realized with respect to a particular context can be attached using the Library resource. | ||
| + | |||
| + | The intent of the resource is to establish a standard mechanism to enable automated sharing of knowledge artifacts such as order sets, protocols, and decision support rules. The resource is a concrete realization of the logical model defined by the [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=337 HL7 Standard: Clinical Decision Support Knowledge Artifact Specification]. | ||
==Owning committee name== | ==Owning committee name== | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Clinical_Decision_Support_Workgroup|Clinical Decision Support Work Group]] |
| + | |||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | * 2016-07-06 | |
| + | * STU3 Ballot Submission: 2016-08-03 | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | * Work Group | + | *[[Clinical_Quality_Information_Work_Group|Clinical Quality Information Work Group]] |
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| − | + | [http://www.hl7.org/Special/committees/dss/projects.cfm?action=edit&ProjectNumber=1234 1234: FHIR-Based Clinical Quality Framework (CQF-on-FHIR)] | |
| + | |||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 57: | Line 64: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | A PlanDefinition is a knowledge artifact that enables the representation and sharing of pre-defined clinical activities. It differs from a CarePlan in that it is not specific to a given patient, rather it defines a set of activities that can be realized for a patient, resulting in a CarePlan. | ||
| + | |||
| + | PlanDefinitions can be used both within and between healthcare delivery environments, both as part of an catalog, as well as by content providers for sharing and distribution of order sets, protocols, and rules. | ||
| + | |||
| + | The resource is flexible enough to be used to describe plan definitions for any discipline and locale. | ||
==RIM scope== | ==RIM scope== | ||
| Line 76: | Line 89: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | Order sets are a key component of facilitating placement and fulfillment of orders related to specific conditions and workflows, but management of order sets is often built directly into healthcare delivery systems in a way that prevents sharing of the definitions. In addition, order set content providers often use proprietary formats to distribute their content, resulting in different implementations for each combination of consumer and provider systems. | ||
| + | |||
| + | The Clinical Decision Support Knowledge Artifact Specification provides a standard mechanism for representing order sets, and enabling that content to be represented as a FHIR resource will extend the reach of that specification. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to expose the content, effectively enabling another potential role of a FHIR server as Order Set Catalog. | ||
| + | |||
| + | The resource can also be used to model diverse types of protocols such as research protocols, specimen handling protocols, or disease treatment plans. | ||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | |||
| + | Motive Medical | ||
| + | Cognitive Medical Systems | ||
| + | NCCN | ||
| + | Plexina | ||
==Content sources== | ==Content sources== | ||
| Line 86: | Line 110: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | |||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=391 Clinical Quality Common Metadata Conceptual Model] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=337 Clinical Decision Support Knowledge Artifact Specification] | ||
| + | *[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=287 Order Set Publication] | ||
| + | |||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | ===Low Suicide Risk=== | ||
| + | When assessing a patient for suicide risk, the actions that should be taken as a result of the assessment is defined as an order set. | ||
| + | |||
| + | ===Obesity Determination Protocol=== | ||
| + | Example of A medical algorithm for assessment and treatment of overweight and obesity | ||
| + | |||
| + | ===Research Protocols=== | ||
| + | Clinical trials and other types of research specify protocols to ensure the research produces valid data. The resource can be used to specify actions to be taken in the clinical trial. | ||
| + | |||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 101: | Line 140: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | This resource will make use of the [http://hl7.org/fhir/library.html Library] resource to represent any logic involved in defining the behavior of the plan definition. | ||
| + | |||
| + | The resource will also make use of the [http://hl7.org/fhir/activitydefinition.html ActivityDefinition] resource to represent the detail for the activities involved in describing the plan definition. | ||
| + | |||
| + | In addition, the resource makes use of the following common data types: | ||
| + | |||
| + | * [http://hl7.org/fhir/contactdetail.html ContactDetail] | ||
| + | * [http://hl7.org/fhir/contributor.html Contributor] | ||
| + | * [http://hl7.org/fhir/relatedresource.html RelatedResource] | ||
| + | * [http://hl7.org/fhir/usagecontext.html UsageContext] | ||
| + | * [http://hl7.org/fhir/triggerdefinition.html TriggerDefinition] | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | September 2016 Ballot Cycle in support of the [http://hl7.org/fhir/cqif/cqif.html CQF IG]. | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | brynrhodes | ||
==When Resource Proposal Is Complete== | ==When Resource Proposal Is Complete== | ||
'''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | '''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]''' | ||
Latest revision as of 15:08, 21 August 2017
This page documents a Approved FHIR Resource Proposal
Contents
- 1 PlanDefinition
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
PlanDefinition
The PlanDefinition resource represents a pre-defined and approved group of activities to be performed related to a particular clinical condition (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission to Coronary Care Unit). The resource captures metadata about the plan definition, as well as a hierarchical grouping of any number of actions to be taken, each of which describes a specific activity to be performed.
The PlanDefinition resource is definitional in nature, it describes a patient-independent set of activities for a particular setting. In addition, the resource allows for behaviors to be defined for each action, as well as for relationships between the actions to be defined. Conditional logic describing how the plan definition is realized with respect to a particular context can be attached using the Library resource.
The intent of the resource is to establish a standard mechanism to enable automated sharing of knowledge artifacts such as order sets, protocols, and decision support rules. The resource is a concrete realization of the logical model defined by the HL7 Standard: Clinical Decision Support Knowledge Artifact Specification.
Owning committee name
Clinical Decision Support Work Group
Committee Approval Date:
- 2016-07-06
- STU3 Ballot Submission: 2016-08-03
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
1234: FHIR-Based Clinical Quality Framework (CQF-on-FHIR)
Scope of coverage
A PlanDefinition is a knowledge artifact that enables the representation and sharing of pre-defined clinical activities. It differs from a CarePlan in that it is not specific to a given patient, rather it defines a set of activities that can be realized for a patient, resulting in a CarePlan.
PlanDefinitions can be used both within and between healthcare delivery environments, both as part of an catalog, as well as by content providers for sharing and distribution of order sets, protocols, and rules.
The resource is flexible enough to be used to describe plan definitions for any discipline and locale.
RIM scope
Resource appropriateness
Order sets are a key component of facilitating placement and fulfillment of orders related to specific conditions and workflows, but management of order sets is often built directly into healthcare delivery systems in a way that prevents sharing of the definitions. In addition, order set content providers often use proprietary formats to distribute their content, resulting in different implementations for each combination of consumer and provider systems.
The Clinical Decision Support Knowledge Artifact Specification provides a standard mechanism for representing order sets, and enabling that content to be represented as a FHIR resource will extend the reach of that specification. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to expose the content, effectively enabling another potential role of a FHIR server as Order Set Catalog.
The resource can also be used to model diverse types of protocols such as research protocols, specimen handling protocols, or disease treatment plans.
Expected implementations
Motive Medical Cognitive Medical Systems NCCN Plexina
Content sources
- Clinical Quality Common Metadata Conceptual Model
- Clinical Decision Support Knowledge Artifact Specification
- Order Set Publication
Example Scenarios
Low Suicide Risk
When assessing a patient for suicide risk, the actions that should be taken as a result of the assessment is defined as an order set.
Obesity Determination Protocol
Example of A medical algorithm for assessment and treatment of overweight and obesity
Research Protocols
Clinical trials and other types of research specify protocols to ensure the research produces valid data. The resource can be used to specify actions to be taken in the clinical trial.
Resource Relationships
This resource will make use of the Library resource to represent any logic involved in defining the behavior of the plan definition.
The resource will also make use of the ActivityDefinition resource to represent the detail for the activities involved in describing the plan definition.
In addition, the resource makes use of the following common data types:
Timelines
September 2016 Ballot Cycle in support of the CQF IG.
gForge Users
brynrhodes
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
