StructureDefinition: ComputablePlanDefinition

Language of the resource content
Binding: All Languages ( required ): IETF language tag for a human language

text 0..1 Narrative Text summary of the resource, for human interpretation contained 0..* Resource Contained, inline Resources extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored url Σ C 0..1 uri Canonical identifier for this plan definition, represented as a URI (globally unique) identifier Σ 0..* Identifier Additional identifier for the plan definition version Σ 0..1 string Business version of the plan definition versionAlgorithm[x] Σ 0..1 How to compare versions Binding: Version Algorithm ( extensible ) versionAlgorithmString string versionAlgorithmCoding Coding name Σ C 0..1 string Name for this plan definition (computer friendly) title Σ 0..1 string Name for this plan definition (human friendly) subtitle 0..1 string Subordinate title of the plan definition type Σ 0..1 CodeableConcept order-set | clinical-protocol | eca-rule | workflow-definition Binding: Plan Definition Type ( extensible ): The type of PlanDefinition. status ?! Σ 1..1 code draft | active | retired | unknown Binding: PublicationStatus ( required ): The lifecycle status of an artifact. experimental Σ 0..1 boolean For testing purposes, not real usage subject[x] 0..1 Type of individual the plan definition is focused on Binding: Participant Resource Types ( extensible ): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.). subjectCodeableConcept CodeableConcept subjectReference Reference ( Group | MedicinalProductDefinition | SubstanceDefinition | AdministrableProductDefinition | ManufacturedItemDefinition | PackagedProductDefinition ) subjectCanonical canonical ( EvidenceVariable ) date Σ 0..1 dateTime Date last changed publisher Σ 0..1 string Name of the publisher/steward (organization or individual) contact Σ 0..* ContactDetail Contact details for the publisher description Σ 0..1 markdown Natural language description of the plan definition useContext Σ 0..* UsageContext The context that the content is intended to support jurisdiction Σ XD 0..* CodeableConcept Intended jurisdiction for plan definition (if applicable) Binding: Jurisdiction ValueSet ( extensible ): Countries and regions within which this artifact is targeted for use. purpose 0..1 markdown Why this plan definition is defined usage 0..1 markdown Describes the clinical usage of the plan copyright 0..1 markdown Use and/or publishing restrictions copyrightLabel 0..1 string Copyright holder and year(s) approvalDate 0..1 date When the plan definition was approved by publisher lastReviewDate 0..1 date When the plan definition was last reviewed by the publisher effectivePeriod Σ 0..1 Period When the plan definition is expected to be used topic XD 0..* CodeableConcept E.g. Education, Treatment, Assessment Binding: Definition Topic ( example ): High-level categorization of the definition, used for searching, sorting, and filtering. author 0..* ContactDetail Who authored the content editor 0..* ContactDetail Who edited the content reviewer 0..* ContactDetail Who reviewed the content endorser 0..* ContactDetail Who endorsed the content relatedArtifact 0..* RelatedArtifact Additional documentation, citations library 1..1 canonical ( Library ) Logic used by the plan definition goal C 0..* BackboneElement What the plan is trying to accomplish id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized category 0..1 CodeableConcept E.g. Treatment, dietary, behavioral Binding: Goal Category ( example ): Example codes for grouping goals for filtering or presentation. description 1..1 CodeableConcept Code or text describing the goal Binding: SNOMED CT Clinical Findings ( example ): Describes goals that can be achieved. priority 0..1 CodeableConcept high-priority | medium-priority | low-priority Binding: Goal Priority ( preferred ): Indicates the level of importance associated with reaching or sustaining a goal. start 0..1 CodeableConcept When goal pursuit begins Binding: Goal Start Event ( example ): Identifies the types of events that might trigger the start of a goal. addresses 0..* CodeableConcept What does the goal address Binding: Condition/Problem/Diagnosis Codes ( example ): Identifies problems, conditions, issues, or concerns that goals may address. documentation 0..* RelatedArtifact Supporting documentation for the goal target 0..* BackboneElement Target outcome for the goal id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized measure 0..1 CodeableConcept The parameter whose value is to be tracked Binding: LOINC Codes ( example ): Identifies types of parameters that can be tracked to determine goal achievement. detail[x] 0..1 The target value to be achieved detailQuantity Quantity detailRange Range detailCodeableConcept CodeableConcept detailString string detailBoolean boolean detailInteger integer detailRatio Ratio due 0..1 Duration Reach goal within actor 0..* BackboneElement Actors within the plan id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized title 0..1 string User-visible title description 0..1 markdown Describes the actor option 1..* BackboneElement Who or what can be this actor id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized type 0..1 code careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson Binding: Action Participant Type ( required ): The type of participant in the activity. typeCanonical 0..1 canonical ( CapabilityStatement ) Who or what can participate typeReference 0..1 Reference ( CareTeam | Device | DeviceDefinition | Endpoint | Group | HealthcareService | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson ) Who or what can participate role 0..1 CodeableConcept E.g. Nurse, Surgeon, Parent Binding: Action Participant Role ( example ) action C 0..* BackboneElement Action defined by the plan id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized linkId 0..1 string Unique id for the action in the PlanDefinition prefix 0..1 string User-visible prefix for the action (e.g. 1. or A.) title 0..1 string User-visible title description 0..1 markdown Brief description of the action textEquivalent 0..1 markdown Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system priority 0..1 code routine | urgent | asap | stat Binding: RequestPriority ( required ): Identifies the level of importance to be assigned to actioning the request. code 0..1 CodeableConcept Code representing the meaning of the action or sub-actions Binding: Action Code ( example ): Provides examples of actions to be performed. reason 0..* CodeableConcept Why the action should be performed Binding: Action Reason Code ( example ): Provides examples of reasons for actions to be performed. documentation 0..* RelatedArtifact Supporting documentation for the intended performer of the action goalId C 0..* id What goals this action supports subject[x] 0..1 Type of individual the action is focused on Binding: Participant Resource Types ( extensible ): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.). subjectCodeableConcept CodeableConcept subjectReference Reference ( Group ) subjectCanonical canonical (Any) trigger 0..* TriggerDefinition When the action should be triggered condition 0..* BackboneElement Whether or not the action is applicable id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized kind 1..1 code applicability | start | stop Binding: Action Condition Kind ( required ): Defines the kinds of conditions that can appear on actions. expression 0..1 Expression Boolean-valued expression input C 0..* BackboneElement Input data requirements id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized title 0..1 string User-visible title requirement C 0..1 DataRequirement What data is provided relatedData C 0..1 id What data is provided output C 0..* BackboneElement Output data definition id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized title 0..1 string User-visible title requirement C 0..1 DataRequirement What data is provided relatedData C 0..1 string What data is provided relatedAction C 0..* BackboneElement Relationship to another action id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized targetId C 1..1 id What action is this related to relationship 1..1 code before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end Binding: Action Relationship Type ( required ): Defines the types of relationships between actions. endRelationship 0..1 code before | before-start | before-end | concurrent | concurrent-with-start | concurrent-with-end | after | after-start | after-end Binding: Action Relationship Type ( required ): Defines the types of relationships between actions. offset[x] 0..1 Time offset for the relationship offsetDuration Duration offsetRange Range timing[x] 0..1 When the action should take place timingAge Age timingDuration Duration timingRange Range timingTiming Timing location 0..1 CodeableReference ( Location ) Where it should happen participant 0..* BackboneElement Who should participate in the action id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized actorId 0..1 string What actor type 0..1 code careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson Binding: Action Participant Type ( required ): The type of participant in the activity. typeCanonical 0..1 canonical ( CapabilityStatement ) Who or what can participate typeReference 0..1 Reference ( CareTeam | Device | DeviceDefinition | Endpoint | Group | HealthcareService | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson ) Who or what can participate role 0..1 CodeableConcept E.g. Nurse, Surgeon, Parent Binding: Action Participant Role ( example ): Defines roles played by participants for the action. function 0..1 CodeableConcept E.g. Author, Reviewer, Witness, etc Binding: Action Participant Function ( example ) type 0..1 CodeableConcept create | update | remove | fire-event Binding: Action Type ( extensible ): The type of action to be performed. groupingBehavior 0..1 code visual-group | logical-group | sentence-group Binding: Action Grouping Behavior ( required ): Defines organization behavior of a group. selectionBehavior 0..1 code any | all | all-or-none | exactly-one | at-most-one | one-or-more Binding: Action Selection Behavior ( required ): Defines selection behavior of a group. requiredBehavior 0..1 code must | could | must-unless-documented Binding: Action Required Behavior ( required ): Defines expectations around whether an action or action group is required. precheckBehavior 0..1 code yes | no Binding: Action Precheck Behavior ( required ): Defines selection frequency behavior for an action or group. cardinalityBehavior 0..1 code single | multiple Binding: Action Cardinality Behavior ( required ): Defines behavior for an action or a group for how many times that item may be repeated. definition[x] 0..1 Description of the activity to be performed definitionCanonical canonical ( ActivityDefinition | MessageDefinition | ObservationDefinition | PlanDefinition | Questionnaire | SpecimenDefinition ) definitionUri uri transform 0..1 canonical ( StructureMap ) Transform to apply the template dynamicValue 0..* BackboneElement Dynamic aspects of the definition id 0..1 string Unique id for inter-element referencing extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized path 0..1 string The path to the element to be set dynamically expression 0..1 Expression An expression that provides the dynamic value for the customization action 0..* See action (PlanDefinition) A sub-action asNeeded[x] Σ 0..1 Preconditions for service Binding: SNOMED CT Medication As Needed Reason Codes ( example ): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc. asNeededBoolean boolean asNeededCodeableConcept CodeableConcept Documentation for this format  < xmlns="http://hl7.org/fhir" >  < <</meta> < < < Text summary of the resource, for human interpretation</text> <</contained> <<a href="computableplandefinition-definitions.html#PlanDefinition.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < Canonical identifier for this plan definition, represented as a URI (globally unique) < Additional identifier for the plan definition</identifier> < <</versionAlgorithm[x]> < < < <</type> < < <</subject[x]> < < < Contact details for the publisher</contact> < < The context that the content is intended to support</useContext> <</jurisdiction> < < < < < < < When the plan definition is expected to be used</effectivePeriod> <</topic> <</author> <</editor> <</reviewer> <</endorser> < Additional documentation, citations</relatedArtifact> < < <<a href="computableplandefinition-definitions.html#PlanDefinition.goal.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> <</category> <</description> <</priority> <</start> <</addresses> < Supporting documentation for the goal</documentation> < <<a href="computableplandefinition-definitions.html#PlanDefinition.goal.target.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> <</measure> <| The target value to be achieved</detail[x]> < Reach goal within</due> </target> </goal> < <<a href="computableplandefinition-definitions.html#PlanDefinition.actor.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < < <<a href="computableplandefinition-definitions.html#PlanDefinition.actor.option.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < < Who or what can participate</typeReference> <</role> </option> </actor> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < < < < Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system < <</code> <</reason> < Supporting documentation for the intended performer of the action</documentation> < <)| </subject[x]> < When the action should be triggered</trigger> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.condition.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < Boolean-valued expression</expression> </condition> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.input.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < What data is provided</requirement> < </input> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.output.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < What data is provided</requirement> < </output> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.relatedAction.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < < < Time offset for the relationship</offset[x]> </relatedAction> < When the action should take place</timing[x]> < Where it should happen</location> < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.participant.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < < < Who or what can participate</typeReference> <</role> <</function> </participant> <</type> < < < < < < Description of the activity to be performed</definition[x]> < < <<a href="computableplandefinition-definitions.html#PlanDefinition.action.dynamicValue.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"></modifierExtension> < < An expression that provides the dynamic value for the customization</expression> </dynamicValue> <</action> </action> <</asNeeded[x]> </PlanDefinition> { // // from Element: " " " " " "<a href="computableplandefinition-definitions.html#PlanDefinition.modifierExtension" title="May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself) (this element modifies the meaning of other elements)" class="dict"> " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " } This structure is derived from PlanDefinition . Summary Mandatory: 1 element ~~The definition of a plan for a series of actions, independent of any specific patient or context~~ ~~library 1..1 canonical ( Library ) Logic used by the plan definition~~ Documentation for this format Snapshot View This provides the consolidated view (aka snapshot) of the profile after applying the changes in this profile to the base PlanDefinition structure. Name Flags Card. Type Description & Constraints PlanDefinition C 1..1 PlanDefinition The definition of a plan for a series of actions, independent of any specific patient or context id Σ 0..1 id Logical id of this artifact meta Σ 0..1 Meta Metadata about the resource implicitRules ~~?! Σ 0..1~~ ~~A set of rules under which this content was created~~ ~~language 0..1 code Language of the resource content Binding: All Languages ( required ): IETF language tag for a human language~~

~~Differential View~~ Additional Bindings ~~This indicates the differences between this profile and the base PlanDefinition structure. Name Flags Card. Type Description & Constraints PlanDefinition 1..1 PlanDefinition~~

Purpose

Common Languages

~~uri~~ Starter Set

text

0..1

Narrative

Text summary of the resource, for human interpretation

contained

0..*

Resource

Contained, inline Resources

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored

url

Σ C

0..1

uri

Canonical identifier for this plan definition, represented as a URI (globally unique)

identifier

0..*

Identifier

Additional identifier for the plan definition

version

0..1

Business version of the plan definition

versionAlgorithm[x]

0..1

How to compare versions
Binding: Version Algorithm ( extensible )

versionAlgorithmString

versionAlgorithmCoding

Coding

name

Σ C

0..1

Name for this plan definition (computer friendly)

0..1

Name for this plan definition (human friendly)

subtitle

0..1

Subordinate title of the plan definition

type

0..1

order-set | clinical-protocol | eca-rule | workflow-definition
Binding: Plan Definition Type ( extensible ): The type of PlanDefinition.

status

?! Σ

1..1

draft | active | retired | unknown
Binding: PublicationStatus ( required ): The lifecycle status of an artifact.

experimental

0..1

boolean

For testing purposes, not real usage

subject[x]

0..1

Type of individual the plan definition is focused on
Binding: Participant Resource Types ( extensible ): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).

subjectCodeableConcept

subjectReference

subjectCanonical

canonical ( EvidenceVariable )

date

0..1

dateTime

Date last changed

publisher

0..1

Name of the publisher/steward (organization or individual)

contact

0..*

Contact details for the publisher

0..1

Natural language description of the plan definition

useContext

0..*

UsageContext

The context that the content is intended to support

jurisdiction

Σ XD

0..*

Intended jurisdiction for plan definition (if applicable)
Binding: Jurisdiction ValueSet ( extensible ): Countries and regions within which this artifact is targeted for use.

purpose

0..1

Why this plan definition is defined

usage

0..1

Describes the clinical usage of the plan

0..1

Use and/or publishing restrictions

copyrightLabel

0..1

approvalDate

0..1

date

When the plan definition was approved by publisher

lastReviewDate

0..1

date

When the plan definition was last reviewed by the publisher

effectivePeriod

0..1

Period

When the plan definition is expected to be used

topic

0..*

E.g. Education, Treatment, Assessment
Binding: Definition Topic ( example ): High-level categorization of the definition, used for searching, sorting, and filtering.

author

0..*

Who authored the content

editor

0..*

Who edited the content

reviewer

0..*

Who reviewed the content

endorser

0..*

Who endorsed the content

relatedArtifact

0..*

RelatedArtifact

Additional documentation, citations

library

1..1

canonical ( Library )

Logic used by the plan definition

goal

0..*

What the plan is trying to accomplish

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

category

0..1

E.g. Treatment, dietary, behavioral
Binding: Goal Category ( example ): Example codes for grouping goals for filtering or presentation.

1..1

Code or text describing the goal
Binding: SNOMED CT Clinical Findings ( example ): Describes goals that can be achieved.

priority

0..1

high-priority | medium-priority | low-priority
Binding: Goal Priority ( preferred ): Indicates the level of importance associated with reaching or sustaining a goal.

start

0..1

When goal pursuit begins
Binding: Goal Start Event ( example ): Identifies the types of events that might trigger the start of a goal.

addresses

0..*

What does the goal address
Binding: Condition/Problem/Diagnosis Codes ( example ): Identifies problems, conditions, issues, or concerns that goals may address.

documentation

0..*

RelatedArtifact

Supporting documentation for the goal

target

0..*

Target outcome for the goal

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

measure

0..1

The parameter whose value is to be tracked
Binding: LOINC Codes ( example ): Identifies types of parameters that can be tracked to determine goal achievement.

detail[x]

0..1

The target value to be achieved

detailQuantity

Quantity

detailRange

Range

detailCodeableConcept

detailString

detailBoolean

detailInteger

detailRatio

Ratio

due

0..1

Duration

Reach goal within

actor

0..*

Actors within the plan

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

0..1

User-visible title

0..1

Describes the actor

option

1..*

Who or what can be this actor

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

type

0..1

typeCanonical

0..1

canonical ( CapabilityStatement )

Who or what can participate

typeReference

0..1

Who or what can participate

role

0..1

E.g. Nurse, Surgeon, Parent
Binding: Action Participant Role icon

( example )

action

0..*

Action defined by the plan

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

linkId

0..1

Unique id for the action in the PlanDefinition

prefix

0..1

User-visible prefix for the action (e.g. 1. or A.)

0..1

User-visible title

0..1

Brief description of the action

textEquivalent

0..1

Static text equivalent of the action, used if the dynamic aspects cannot be interpreted by the receiving system

priority

0..1

routine | urgent | asap | stat
Binding: RequestPriority ( required ): Identifies the level of importance to be assigned to actioning the request.

0..1

Code representing the meaning of the action or sub-actions
Binding: Action Code ( example ): Provides examples of actions to be performed.

reason

0..*

Why the action should be performed
Binding: Action Reason Code ( example ): Provides examples of reasons for actions to be performed.

documentation

0..*

RelatedArtifact

Supporting documentation for the intended performer of the action

goalId

0..*

What goals this action supports

subject[x]

0..1

Type of individual the action is focused on
Binding: Participant Resource Types ( extensible ): The possible types of subjects for a plan definition (E.g. Patient, Practitioner, Organization, Location, etc.).

subjectCodeableConcept

subjectReference

Reference ( Group )

subjectCanonical

canonical (Any)

trigger

0..*

TriggerDefinition

When the action should be triggered

condition

0..*

Whether or not the action is applicable

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

kind

1..1

applicability | start | stop
Binding: Action Condition Kind ( required ): Defines the kinds of conditions that can appear on actions.

expression

0..1

Expression

Boolean-valued expression

input

0..*

Input data requirements

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

0..1

User-visible title

requirement

0..1

DataRequirement

What data is provided

relatedData

0..1

What data is provided

output

0..*

Output data definition

0..1

Unique id for inter-element referencing

0..*

Additional content defined by implementations

?! Σ

0..*

Extensions that cannot be ignored even if unrecognized

0..1

User-visible title

requirement

0..1

DataRequirement

What data is provided

relatedData

0..1

What data is provided

relatedAction

0..*

Relationship to another action

0..1