- FHIR Element Definition Resource
- Electronic Health Records Exchange Through FHIR
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
A plan definition is a pre-defined group of actions to be taken in particular circumstances, often including conditional elements, options, and other decision points. The resource is flexible enough to be used to represent a variety of workflows, as well as clinical decision support and quality improvement assets, including order sets, protocols, and decision support rules.
Plan Definitions can contain hierarchical groups of action definitions, where each action definition describes an activity to be performed (often in terms of an Activity Definition resource), and each group defines additional behavior, relationships, and applicable conditions between the actions in the overall definition.
In addition to describing what should take place, each action in a plan definition can specify when and whether the action should take place. For when the action should be taken, the trigger element specifies the action should be taken in response to some trigger occurring (such as a particular point in a workflow being reached, or as the result of a prescription being ordered). For whether the action should be taken, the condition element can be used to provide an expression that evaluates to true or false to indicate the applicability of the action to the specific context.
The process of applying a Plan Definition to a particular context typically produces request resources representing the actions that should be performed, typically grouped within a Care Plan and/or Request Group to capture relationships between the resulting request resources.
Each Activity Definition is used to construct a specific resource, based on the definition of the activity and combined with contextual information for the particular patient that the plan definition is being applied to.
Note that these mechanisms are provided on both the Activity Definition and the Plan Definition to allow both reusable transformation descriptions, as well as customization of those descriptions within specific contexts. As such, the transform descriptions specified on the Plan Definition override transform descriptions defined on the Activity Definition.
About this Dataset
John Snow Labs; Health Level Seven International;
|Source License URL|
|Source License Requirements||
FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR
FHIR Element Definition Resource, Electronic Health Records Exchange Through FHIR
|Concept_Name||Name of the concept in the FHIR structure||string||required : 1|
|Computer_Ready_Name||A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this.||string||-|
|Type||The type the structure describes.||string||-|
|Dollar_Ref||The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced.||string||-|
|Description||A free text natural language description of the structure and its use||string||-|
|Items||The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value.||string||-|
|Enum||The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.||string||-|
|Required||The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value.||string||-|
|Const||The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword.||string||-|
|Concept Name||Computer Ready Name||Type||Dollar Ref||Description||Items||Enum||Required||Const|
|PlanDefinition||resourceType||This is a PlanDefinition resource||PlanDefinition|
|PlanDefinition||id||#/definitions/id||The logical id of the resource|
|PlanDefinition||meta||#/definitions/Meta||The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.|
|PlanDefinition||implicitRules||#/definitions/uri||A reference to a set of rules that were followed when the resource was constructed|
|PlanDefinition||_implicitRules||#/definitions/Element||Extensions for implicitRules|
|PlanDefinition||language||#/definitions/code||The base language in which the resource is written.|
|PlanDefinition||_language||#/definitions/Element||Extensions for language|
|PlanDefinition||text||#/definitions/Narrative||A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data|
|PlanDefinition||contained||array||These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently|
|PlanDefinition||extension||array||May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable|