3.1. Logical Models
Logical Models represent data structures, and contain data elements and their constraints and relationships. They allow data requirements to be described from a functional perspective. In this IG, the functional dataset and the underlying use cases for the information models that are not present in ART-DECOR, are represented by FHIR Logical Models (note that this link redirects to the R5 specification, as there is no dedicated page for Logical Models in the STU3 specification). These use FHIR to capture the data structures (namely by specifying a StructureDefinition and underlying ElementDefinitions, for each data structure), but they are not (directly) attached to FHIR resources.
The Logical Models contain all functional concepts, including corresponding data type, terminology binding (if applicable) and an id.
- For each concept, an id is assigned by MedMij. These ids are also added as mappings in the FHIR profiles, and therefore form the linking pin between Logical Models and FHIR profiles.
- For each concept it is indicated whether it is repeating (i.e. by setting its maximum cardinality to
1 or *). Moreover, for each concept it is indicated whether it is (conditionally) required by setting the minimum cardinality to 1 (or adding a constraint which specifies when the concept is required).
- The FHIR data types are used in the Logical Models, even though these might bring 'physical' constraints, formats, etc. into the abstract logical data models which are not intended or applicable on the logical level. For instance, elements of the Attachment data type need to satisfy the att-1 constraint, which states that the element SHALL have a
contentType, provided the element has non-empty data. Even though this constraint makes sense on a technical level, the aforementioned attributes contentType and data are not present in a logical data model. Therefore, such constraints may be 'ignored' in the Logical Models; instead, these constraints are taken into account in the corresponding FHIR profiles.
- Since the Logical Models defined in this IG are meant to represent the use case,
.abstract is set to false.
- For all Logical Models the scope is implicitly set to a single patient. This relation is not explicitly modeled, similar to the approach of the zibs.
3.1.1. Nursing Report
A report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse.
| LzLmNursingReport (lz-lm-NursingReport) | | | Element | Element idlz-lm-NursingReport Short descriptionNursing report Alternate namesDagrapportage DefinitionA report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse.
Data typeElement ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) Mappings- rim: n/a
- lz-dataset-100-rc3-20260811: lz-dataelement-1
- SNOMED: 11591000146107
|
| id | | 0..1 | string | There are no (further) constraints on this element Element idlz-lm-NursingReport.id Short descriptionxml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
CommentsNote that FHIR strings may not exceed 1MB in size
Data typestring ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) Mappings |
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idlz-lm-NursingReport.extension Short descriptionAdditional Content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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.
CommentsThere can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Data typeExtension SlicingUnordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) - ext-1: Must have either extensions or value[x], not both
extension.exists() != value.exists() Mappings |
| ReportTitle | | 0..1 | string | Element idlz-lm-NursingReport.ReportTitle Short descriptionReport title Alternate namesRapportageTitel DefinitionThe title of the nursing report.
CommentsThe title should be human readable and clear to the patient.
Data typestring ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) Mappings- rim: n/a
- lz-dataset-100-rc3-20260811: lz-dataelement-2
|
| ReportDateTime | | 1..1 | dateTime | Element idlz-lm-NursingReport.ReportDateTime Short descriptionReport date time Alternate namesRapportageDatumTijd DefinitionThe date/time on which the nursing report is registered.
Data typedateTime ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) Mappings- rim: n/a
- lz-dataset-100-rc3-20260811: lz-dataelement-3
|
| Performer | C | 1..1 | Reference(MedMijCoreLmHealthcareProvider | MedMijCoreLmHealthProfessional) | Element idlz-lm-NursingReport.Performer Short descriptionPerformer Alternate namesUitvoerder DefinitionThe health professional or organization who registered the nursing report.
CommentsReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
Data typeReference(MedMijCoreLmHealthcareProvider | MedMijCoreLmHealthProfessional) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) - ref-1: SHALL have a contained resource if a local reference is provided
reference.exists() implies (reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids')) or (reference='#' and %rootResource!=%resource)) Mappings- rim: n/a
- rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
- lz-dataset-100-rc3-20260811: lz-dataelement-4
|
| ReportContent | | 1..1 | string | Element idlz-lm-NursingReport.ReportContent Short descriptionReport content Alternate namesRapportageInhoud DefinitionThe content of the nursing report.
CommentsNote that FHIR strings may not exceed 1MB in size
Data typestring ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints- ele-1: All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count()) Mappings- rim: n/a
- lz-dataset-100-rc3-20260811: lz-dataelement-19
|
| Mapping name | Concept id | Logical element | Comments |
|---|
| lz-dataset-100-rc3-20260811 | lz-dataelement-1 | NursingReport | NursingReport |
| lz-dataset-100-rc3-20260811 | lz-dataelement-2 | NursingReport.ReportTitle | ReportTitle |
| lz-dataset-100-rc3-20260811 | lz-dataelement-3 | NursingReport.ReportDateTime | ReportDateTime |
| lz-dataset-100-rc3-20260811 | lz-dataelement-4 | NursingReport.Performer | Performer |
| lz-dataset-100-rc3-20260811 | lz-dataelement-19 | NursingReport.ReportContent | ReportContent |
| SNOMED | 11591000146107 | NursingReport | patiƫntcontactverslag |
<id value="lz-lm-NursingReport" />
--- We have skipped the narrative for better readability of the resource ---
</text>
<url value="http://medmij.nl/fhir/StructureDefinition/lz-lm-NursingReport" />
<system value="urn:ietf:rfc:3986" />
<value value="urn:oid:2.16.528.1.1023.3.4.1" />
</identifier>
<name value="LzLmNursingReport" />
<title value="NursingReport" />
<value value="info@medmij.nl" />
</telecom>
</contact>
<description value="A report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse." />
<purpose value="This LogicalModel represents the NursingReport Clinical Information Model (CIM) for patient use cases in the context of Long-term Healthcare. It is based on the [ANW v2024.1](https://nuts-foundation.gitbook.io/bolts/anw/v2024.1#id-5.2-wegschrijven-van-informatie) specification." />
<copyright value="Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise." />
<identity value="lz-dataset-100-rc3-20260811" />
<name value="Dataset Langdurige Zorg MedMij 1.0.0-rc.3 20260811" />
</mapping>
<uri value="http://snomed.info/sct" />
<name value="SNOMED CT" />
</mapping>
<type value="lz-lm-NursingReport" />
<baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" />
<path value="lz-lm-NursingReport" />
<short value="Nursing report" />
<definition value="A report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse." />
<alias value="Dagrapportage" />
<identity value="lz-dataset-100-rc3-20260811" />
<map value="lz-dataelement-1" />
</mapping>
<map value="11591000146107" />
<comment value="patiëntcontactverslag" />
</mapping>
</element>
<element id="lz-lm-NursingReport.ReportTitle">
<path value="lz-lm-NursingReport.ReportTitle" />
<short value="Report title" />
<definition value="The title of the nursing report." />
<comment value="The title should be human readable and clear to the patient." />
<alias value="RapportageTitel" />
</type>
<identity value="lz-dataset-100-rc3-20260811" />
<map value="lz-dataelement-2" />
</mapping>
</element>
<element id="lz-lm-NursingReport.ReportDateTime">
<path value="lz-lm-NursingReport.ReportDateTime" />
<short value="Report date time" />
<definition value="The date/time on which the nursing report is registered." />
<alias value="RapportageDatumTijd" />
<code value="dateTime" />
</type>
<identity value="lz-dataset-100-rc3-20260811" />
<map value="lz-dataelement-3" />
</mapping>
</element>
<element id="lz-lm-NursingReport.Performer">
<path value="lz-lm-NursingReport.Performer" />
<short value="Performer" />
<definition value="The health professional or organization who registered the nursing report." />
<alias value="Uitvoerder" />
<code value="Reference" />
<targetProfile value="http://medmij.nl/fhir/StructureDefinition/medmij-core-lm-HealthProfessional" />
</type>
<code value="Reference" />
<targetProfile value="http://medmij.nl/fhir/StructureDefinition/medmij-core-lm-HealthcareProvider" />
</type>
<identity value="lz-dataset-100-rc3-20260811" />
<map value="lz-dataelement-4" />
</mapping>
</element>
<element id="lz-lm-NursingReport.ReportContent">
<path value="lz-lm-NursingReport.ReportContent" />
<short value="Report content" />
<definition value="The content of the nursing report." />
<alias value="RapportageInhoud" />
</type>
<identity value="lz-dataset-100-rc3-20260811" />
<map value="lz-dataelement-19" />
</mapping>
</element>
</differential>
</StructureDefinition>
{
"id": "lz-lm-NursingReport",
--- We have skipped the narrative for better readability of the resource ---
},
"url": "http://medmij.nl/fhir/StructureDefinition/lz-lm-NursingReport",
{
"system": "urn:ietf:rfc:3986",
"value": "urn:oid:2.16.528.1.1023.3.4.1"
}
],
"name": "LzLmNursingReport",
"title": "NursingReport",
{
{
"value": "info@medmij.nl",
}
]
}
],
"description": "A report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse.",
"purpose": "This LogicalModel represents the NursingReport Clinical Information Model (CIM) for patient use cases in the context of Long-term Healthcare. It is based on the [ANW v2024.1](https://nuts-foundation.gitbook.io/bolts/anw/v2024.1#id-5.2-wegschrijven-van-informatie) specification.",
"copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
{
"identity": "lz-dataset-100-rc3-20260811",
"name": "Dataset Langdurige Zorg MedMij 1.0.0-rc.3 20260811"
},
{
"uri": "http://snomed.info/sct",
}
],
"type": "lz-lm-NursingReport",
{
"id": "lz-lm-NursingReport",
"path": "lz-lm-NursingReport",
"short": "Nursing report",
"definition": "A report documenting a patient contact in a long-term healthcare nursing setting. The report can be recorded by different types of health professionals and is not necessarily written by a nurse.",
],
{
"identity": "lz-dataset-100-rc3-20260811",
"map": "lz-dataelement-1",
},
{
}
]
},
{
"id": "lz-lm-NursingReport.ReportTitle",
"path": "lz-lm-NursingReport.ReportTitle",
"comment": "The title should be human readable and clear to the patient.",
],
],
{
"identity": "lz-dataset-100-rc3-20260811",
"map": "lz-dataelement-2",
}
]
},
{
"id": "lz-lm-NursingReport.ReportDateTime",
"path": "lz-lm-NursingReport.ReportDateTime",
"short": "Report date time",
"definition": "The date/time on which the nursing report is registered.",
],
],
{
"identity": "lz-dataset-100-rc3-20260811",
"map": "lz-dataelement-3",
}
]
},
{
"id": "lz-lm-NursingReport.Performer",
"path": "lz-lm-NursingReport.Performer",
"definition": "The health professional or organization who registered the nursing report.",
],
{
"targetProfile": "http://medmij.nl/fhir/StructureDefinition/medmij-core-lm-HealthProfessional"
},
{
"targetProfile": "http://medmij.nl/fhir/StructureDefinition/medmij-core-lm-HealthcareProvider"
}
],
{
"identity": "lz-dataset-100-rc3-20260811",
"map": "lz-dataelement-4",
}
]
},
{
"id": "lz-lm-NursingReport.ReportContent",
"path": "lz-lm-NursingReport.ReportContent",
"short": "Report content",
"definition": "The content of the nursing report.",
],
],
{
"identity": "lz-dataset-100-rc3-20260811",
"map": "lz-dataelement-19",
}
]
}
]
}
}