PlanDefinition (20)

#NameSourceVerDescription
1CPG Computable Plan Definitionhl7.fhir.uv.cpg#currentR4Defines the minimum expectations and behavior for a computable plan definition
2CPG Order Set Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition as a Order Set for use with CPG Implementation Guide
3CPG Pathway Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition as a Clinical Pathway for use with CPG Implementation Guide. A pathway provides groupings of strategies to provide a longitudinal view of the guideline
4CPG Publishable Plan Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition that defines the minimum expectations for a publishable plan definition
5CPG Recommendation Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition as a Recommendation Definition for use with CPG Implementation Guide
6CPG Shareable Plan Definitionhl7.fhir.uv.cpg#currentR4Defines the minimum expectations for a shareable plan definition for use with computable guideline content. This profile derives from the ShareablePlanDefinition profile defined in the base FHIR specification, and adds support for declaring knowledge representation level and knowledge artifact capabilities.
7CPG Strategy Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition as a Strategy Definition for use with CPG Implementation Guide. Strategies are used to group recommendations together, typically focused on a particular condition or state within the overall guideline or pathway
8CPG Workflow Definitionhl7.fhir.uv.cpg#currentR4Profile of PlanDefinition as a Workflow Definition for use with CPG Implementation Guide
9CRMI Publishable PlanDefinitionhl7.fhir.uv.crmi#currentR4Supports declaration of the PlanDefinition metadata required by HL7 and other organizations that share and publish plandefinitions with a focus on the aspects of that metadata that are important for post-publication activities including distribution, inclusion in repositories, consumption, and implementation.
10CRMI Shareable PlanDefinitionhl7.fhir.uv.crmi#currentR4Enforces the minimum information set for the plan definition metadata required by HL7 and other organizations that share and publish plan definitions
11Laboratory Service Definitionhl7.fhir.uv.order-catalog#currentR5The LabServiceDefinition profile constrains the PlanDefinition resource to represent a laboratory diagnostic service for the clinicians using such services. Clinicians typically order laboratory services and use the results thereof in the course of their delivery of clinical care. A laboratory diagnostic service is a kind of clinical artifact that falls within the scope of PlanDefinition. It involves preparation of the patient, collection and delivery to the lab of biological/digital specimens , tests and panels performed on these specimens, interpretation of the results by the pathologist, and delivery of the results and diagnostic report back to the ordering clinician and possibly other recipients, including the patient. PlanDefinition conveys the general properties of the lab service. It describes the usage of the service, the contexts and situations in which this service is useful, and may also detail the goals that the laboratory service contributes to, such as screening or diagnostic of a particular pathology, monitoring of a long course treatment ... An instance of PlanDefintion, thus, represents a laboratory service. It references one or more instances of ActivityDefinition, describing the service in terms of laboratory procedures, with their input and output observations. The PlanDefinition also references the instances of SpecimenDefinition representing the kinds of specimens needed to perform the service. A service may be a panel or super-panel grouping other laboratory services that may also be ordered independently. In that case, the PlanDefinition of the encompassing service references the PlanDefinition resources representing the included services (relatedArtifact, type composed-of). Reflex tests are represented as sub-actions grouped in a logical group with behavior any, meaning that any number of members of the group may be performed. Each sub-action is associated with a trigger conveying the named event, which reflexes it. A definition of a laboratory diagnostic service conforming to this profile can be used in a laboratory compendium/catalog as well as in other contexts. A laboratory service is fulfilled through the execution of one or more laboratory procedures. The logical combinations of these procedures may be conjunctions (execute each of them) or disjunctions (execute at most one of them), or a mixture of both logical structures. The closest resource that may represent a service as a set of activities logically combined with this flexibility is PlanDefinition. PlanDefinition is therefore selected to represent a laboratory service, and the laboratory procedures needed to achieve this service are represented by instances of ActivityDefinition referenced by PlanDefinition, from logical groups defined in PlanDefinition.
12PlanDefinition - Drug Specification dx-PQhl7.fhir.uv.dx-pq#currentR5Section 12.2 - Drug Specification
13PlanDefinition - dx-PQhl7.fhir.uv.dx-pq#currentR5TBD
14PlanDefinition - Manufacturing Process dx-PQhl7.fhir.uv.dx-pq#currentR5Section 5 - Manufacturing Process
15PlanDefinition - Stability Study Protocol dx-PQhl7.fhir.uv.dx-pq#currentR5Section 11 - Stability Study - Protocol
16PlannedStudyVisitSoahl7.fhir.uv.vulcan-schedule#currentR4A profile that further qualifies the StudyVisitSoa profile so that it can represent a planned visit.
17RecommendationPlanhl7.fhir.uv.ebm#currentR5Profile of PlanDefinition for EBMonFHIR IG
18SoaPlanDefinitionhl7.fhir.uv.ebm#currentR5Profile of PlanDefinition for temporary testing to coordination with M11 use.
19StudyProtocolSoahl7.fhir.uv.vulcan-schedule#currentR4A profile that lists the data elements of a PlanDefinition that must be supported so that it can represent an entire set of visits and activities for a given study protocol.
20StudyVisitSoahl7.fhir.uv.vulcan-schedule#currentR4An abstract profile that lists the data elements of a PlanDefinition that must be supported so that it can represent a Study Visit.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
PlanDefinition C C D
PlanDefinition.id
PlanDefinition.meta
PlanDefinition.implicitRules
PlanDefinition.language
PlanDefinition.text
PlanDefinition.contained
PlanDefinition.extension S C (2) S C (3) S C S C (5) S (8) S (2)
PlanDefinition.modifierExtension
PlanDefinition.url C
PlanDefinition.identifier
PlanDefinition.version C
PlanDefinition.versionAlgorithm[x]
PlanDefinition.name
PlanDefinition.title C C
PlanDefinition.title.extension S D (2)
PlanDefinition.subtitle
PlanDefinition.type C F F F F F D B M
PlanDefinition.status
PlanDefinition.experimental
PlanDefinition.subject[x]
PlanDefinition.date C C
PlanDefinition.publisher
PlanDefinition.contact
PlanDefinition.description C D
PlanDefinition.description.extension S D (2)
PlanDefinition.useContext S C D (6)
PlanDefinition.useContext.value[x] F B M (5)
PlanDefinition.useContext.code F (5)
PlanDefinition.jurisdiction
PlanDefinition.purpose
PlanDefinition.usage D
PlanDefinition.copyright
PlanDefinition.copyrightLabel
PlanDefinition.approvalDate
PlanDefinition.lastReviewDate
PlanDefinition.effectivePeriod
PlanDefinition.topic B M D
PlanDefinition.author
PlanDefinition.editor
PlanDefinition.reviewer
PlanDefinition.endorser
PlanDefinition.relatedArtifact S D (5)
PlanDefinition.relatedArtifact.label C D
PlanDefinition.relatedArtifact.type F D B M (4)
PlanDefinition.relatedArtifact.document D
PlanDefinition.relatedArtifact.document.title D
PlanDefinition.relatedArtifact.document.url D
PlanDefinition.relatedArtifact.resource C D (2)
PlanDefinition.relatedArtifact.url
PlanDefinition.relatedArtifact.display C C D
PlanDefinition.library C
PlanDefinition.goal
PlanDefinition.goal.extension
PlanDefinition.goal.modifierExtension
PlanDefinition.goal.category
PlanDefinition.goal.description
PlanDefinition.goal.priority
PlanDefinition.goal.start
PlanDefinition.goal.addresses
PlanDefinition.goal.documentation
PlanDefinition.goal.target
PlanDefinition.goal.target.extension
PlanDefinition.goal.target.modifierExtension
PlanDefinition.goal.target.measure
PlanDefinition.goal.target.detail[x]
PlanDefinition.goal.target.due
PlanDefinition.actor
PlanDefinition.actor.extension
PlanDefinition.actor.modifierExtension
PlanDefinition.actor.title
PlanDefinition.actor.description
PlanDefinition.actor.option
PlanDefinition.actor.option.extension
PlanDefinition.actor.option.modifierExtension
PlanDefinition.actor.option.type
PlanDefinition.actor.option.typeCanonical
PlanDefinition.actor.option.typeReference
PlanDefinition.actor.option.role
PlanDefinition.action C C D
PlanDefinition.action.extension S C (4) S D (2)
PlanDefinition.action.modifierExtension
PlanDefinition.action.linkId
PlanDefinition.action.prefix
PlanDefinition.action.title C C C C
PlanDefinition.action.description C C C D
PlanDefinition.action.textEquivalent
PlanDefinition.action.priority D
PlanDefinition.action.code C B M C B M C B M C D
PlanDefinition.action.code.coding S C (2)
PlanDefinition.action.code.coding.system F
PlanDefinition.action.reason
PlanDefinition.action.documentation
PlanDefinition.action.goalId
PlanDefinition.action.subject[x]
PlanDefinition.action.trigger S D (2)
PlanDefinition.action.trigger.name C D
PlanDefinition.action.trigger.type F
PlanDefinition.action.condition
PlanDefinition.action.condition.extension
PlanDefinition.action.condition.modifierExtension
PlanDefinition.action.condition.kind
PlanDefinition.action.condition.expression
PlanDefinition.action.input C C D
PlanDefinition.action.input.extension
PlanDefinition.action.input.modifierExtension
PlanDefinition.action.input.title
PlanDefinition.action.input.requirement
PlanDefinition.action.input.relatedData
PlanDefinition.action.output C C D
PlanDefinition.action.output.extension
PlanDefinition.action.output.modifierExtension
PlanDefinition.action.output.title
PlanDefinition.action.output.requirement
PlanDefinition.action.output.relatedData
PlanDefinition.action.relatedAction C
PlanDefinition.action.relatedAction.actionId
PlanDefinition.action.relatedAction.extension S C (2) S C (2)
PlanDefinition.action.relatedAction.modifierExtension
PlanDefinition.action.relatedAction.targetId
PlanDefinition.action.relatedAction.relationship
PlanDefinition.action.relatedAction.endRelationship
PlanDefinition.action.relatedAction.offset[x]
PlanDefinition.action.timing[x] S C (2)
PlanDefinition.action.location
PlanDefinition.action.participant
PlanDefinition.action.participant.extension S C (2)
PlanDefinition.action.participant.modifierExtension
PlanDefinition.action.participant.actorId
PlanDefinition.action.participant.type
PlanDefinition.action.participant.typeCanonical
PlanDefinition.action.participant.typeReference
PlanDefinition.action.participant.role B M
PlanDefinition.action.participant.function
PlanDefinition.action.type C C C
PlanDefinition.action.groupingBehavior C C C F
PlanDefinition.action.selectionBehavior C C
PlanDefinition.action.requiredBehavior C C C
PlanDefinition.action.precheckBehavior C C C
PlanDefinition.action.cardinalityBehavior C C C
PlanDefinition.action.definition[x] D
PlanDefinition.action.transform C C C
PlanDefinition.action.dynamicValue C C C
PlanDefinition.action.dynamicValue.extension
PlanDefinition.action.dynamicValue.modifierExtension
PlanDefinition.action.dynamicValue.path
PlanDefinition.action.dynamicValue.expression
PlanDefinition.action.action
PlanDefinition.asNeeded[x]
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023