EHDS Logical Information Models
0.1.0 - ci-build

EHDS Logical Information Models, published by Xt-EHR. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Xt-EHR/xt-ehr-common/tree/main 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-06-10 Computable Name: EHDSCarePlan

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:

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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.statuspreferred
EHDSCarePlan.addressespreferred

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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 (Differential)

PathConformanceValueSetURI
EHDSCarePlan.statuspreferred
EHDSCarePlan.addressespreferred
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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.statuspreferred
EHDSCarePlan.addressespreferred

This structure is derived from Base

Summary

Mandatory: 0 element(2 nested mandatory elements)

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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.statuspreferred
EHDSCarePlan.addressespreferred

Differential View

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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 (Differential)

PathConformanceValueSetURI
EHDSCarePlan.statuspreferred
EHDSCarePlan.addressespreferred

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. EHDSCarePlan 0..* Base Care plan model
Instances of this logical model can be the target of a Reference
... identifier 0..* Identifier Identifier for the care plan
... subject 1..1 EHDSPatient The patient whose intended care is described by the 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
... description 0..1 string A description of the scope and nature of the 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.statuspreferred
EHDSCarePlan.addressespreferred

This structure is derived from Base

Summary

Mandatory: 0 element(2 nested mandatory elements)

 

Other representations of profile: CSV, Excel