HL7 Europe Imaging Study Report
0.1.0-build - ci-build 150

HL7 Europe Imaging Study Report, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/oijauregui/ehdsimaging/ and changes regularly. See the Directory of published versions

Logical Model: Care plan model

Official URL: https://www.xt-ehr.eu/specifications/fhir/StructureDefinition/EHDSCarePlan Version: 0.1.0
Draft as of 2025-08-05 Computable Name: EHDSCarePlan

Copyright/Legal: Used by permission of HL7 Europe, all rights reserved Creative Commons License

EHDS simplified model for care plan. The model includes very minimal information and is not designed to cover the full functionality of care plans.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header 1..1 Base Common header for all patient-related data
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... authorship 1..* Base Authorship
..... author[x] 1..1 Author
...... authorEHDSHealthProfessional EHDSHealthProfessional
...... authorEHDSOrganisation EHDSOrganisation
...... authorEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of authoring/issuing
.... lastUpdate 0..1 dateTime Date and time of the last update to the resource
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
.... statusReason[x] 0..1 Reason for the current status of the resource.
..... statusReasonCodeableConcept CodeableConcept
..... statusReasonString string
.... language 0..1 CodeableConcept Language
Binding Description: (preferred): BCP 47
.... version 0..1 string Version
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... title 0..1 string Human-friendly name for the care plan
... period 0..1 Period Indicates when the plan did (or is intended to) come into effect and end.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.header.languagepreferred
EHDSCarePlan.addressespreferred

This structure is derived from EHDSDataSet

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
... title 0..1 string Human-friendly name for the care plan
... description 0..1 string A description of the scope and nature of the plan.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.addressespreferred
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header 1..1 Base Common header for all patient-related data
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... authorship 1..* Base Authorship
..... author[x] 1..1 Author
...... authorEHDSHealthProfessional EHDSHealthProfessional
...... authorEHDSOrganisation EHDSOrganisation
...... authorEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of authoring/issuing
.... lastUpdate 0..1 dateTime Date and time of the last update to the resource
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
.... statusReason[x] 0..1 Reason for the current status of the resource.
..... statusReasonCodeableConcept CodeableConcept
..... statusReasonString string
.... language 0..1 CodeableConcept Language
Binding Description: (preferred): BCP 47
.... version 0..1 string Version
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... title 0..1 string Human-friendly name for the care plan
... period 0..1 Period Indicates when the plan did (or is intended to) come into effect and end.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.header.languagepreferred
EHDSCarePlan.addressespreferred

This structure is derived from EHDSDataSet

Summary

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header 1..1 Base Common header for all patient-related data
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... authorship 1..* Base Authorship
..... author[x] 1..1 Author
...... authorEHDSHealthProfessional EHDSHealthProfessional
...... authorEHDSOrganisation EHDSOrganisation
...... authorEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of authoring/issuing
.... lastUpdate 0..1 dateTime Date and time of the last update to the resource
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
.... statusReason[x] 0..1 Reason for the current status of the resource.
..... statusReasonCodeableConcept CodeableConcept
..... statusReasonString string
.... language 0..1 CodeableConcept Language
Binding Description: (preferred): BCP 47
.... version 0..1 string Version
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... title 0..1 string Human-friendly name for the care plan
... period 0..1 Period Indicates when the plan did (or is intended to) come into effect and end.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.header.languagepreferred
EHDSCarePlan.addressespreferred

Differential View

This structure is derived from EHDSDataSet

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
... title 0..1 string Human-friendly name for the care plan
... description 0..1 string A description of the scope and nature of the plan.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.addressespreferred

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* EHDSDataSet
Elements defined in Ancestors:header, presentedForm
Care plan model
Instances of this logical model can be the target of a Reference
... header 1..1 Base Common header for all patient-related data
.... subject 1..1 EHDSPatient The patient whose intended care is described by the plan.
.... identifier 0..* Identifier Identifier for the care plan
.... authorship 1..* Base Authorship
..... author[x] 1..1 Author
...... authorEHDSHealthProfessional EHDSHealthProfessional
...... authorEHDSOrganisation EHDSOrganisation
...... authorEHDSDevice EHDSDevice
..... datetime 1..1 dateTime Date and time of authoring/issuing
.... lastUpdate 0..1 dateTime Date and time of the last update to the resource
.... status 1..1 CodeableConcept Indicates whether the plan is currently being acted upon, represents future intentions or is now a historical record.
Binding Description: (preferred): HL7 Request status
.... statusReason[x] 0..1 Reason for the current status of the resource.
..... statusReasonCodeableConcept CodeableConcept
..... statusReasonString string
.... language 0..1 CodeableConcept Language
Binding Description: (preferred): BCP 47
.... version 0..1 string Version
... presentedForm 0..* EHDSAttachment A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
... title 0..1 string Human-friendly name for the care plan
... period 0..1 Period Indicates when the plan did (or is intended to) come into effect and end.
... addresses 0..* CodeableConcept Conditions/problems/concerns/diagnoses/etc. whose management and/or mitigation are handled by this plan.
Binding Description: (preferred): ICD-10, SNOMED CT, Orphacode
... activity[x] 0..1 The details of the proposed activity represented in a specific resource.
.... activityString string
.... activityReference Reference(Any)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
EHDSCarePlan.header.statuspreferred
EHDSCarePlan.header.languagepreferred
EHDSCarePlan.addressespreferred

This structure is derived from EHDSDataSet

Summary

 

Other representations of profile: CSV, Excel