EHDS Logical Information Models
0.4.0 - draft

EHDS Logical Information Models, published by Xt-EHR. This guide is not an authorized publication; it is the continuous build for version 0.4.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/ and changes regularly. See the Directory of published versions

Logical Model: EHDSPatientLaboratoryObligations - Detailed Descriptions

Draft as of 2026-03-16

Definitions for the EHDSPatientLaboratoryObligations logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. EHDSPatient
Definition

Model for information about a patient (subject of care).


Base definition for all types defined in FHIR type system.

ShortPatient modelBase for all types and resources
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. EHDSPatient.identifier
Definition

An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).

ShortAn identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
NoteThis is a business identifier, not a resource identifier (see discussion)
Control1..*
TypeIdentifier
Obligations
    ObligationsActorDocumentation
    SHALL:able-to-populateProducer

    EHR system SHALL be able to populate one or more business identifiers of the patient.

    SHOULD:displayConsumer

    SHALL process patient identifiers to ensure proper assignment of information.

    SHALL:processConsumer

    SHOULD display identifier when needed to users.

    4. EHDSPatient.name
    Definition

    Name might consist of name parts, e.g. Given name or names, family name/surname, name prefix etc.

    ShortName associated with the patient/subject.
    Control0..*
    Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSHumanName
    Obligations
      ObligationsActorDocumentation
      SHALL:able-to-populateProducer

      EHR system SHALL populate one or more names of the patient meeting conformity requirements on the name structure if a value is known and allowed to be shared.

      SHALL:displayConsumer
      6. EHDSPatient.dateOfBirth
      Definition

      Date of birth

      ShortDate of birth
      Control0..1
      TypedateTime
      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
      Obligations
        ObligationsActorDocumentation
        SHALL:able-to-populateProducer

        EHR system SHALL be able to populate date of birth of the patient.

        SHALL:displayConsumer
        8. EHDSPatient.deceased[x]
        Definition

        Whether the patient is deceased or date of death.

        ShortWhether the patient is deceased or date of death.
        Control0..1
        TypeChoice of: boolean, dateTime
        [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
        Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
        10. EHDSPatient.administrativeGender
        Definition

        This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere.

        ShortAdministrative gender
        Control0..1
        Binding

        HL7 Administrative Gender

        TypeCodeableConcept
        Obligations
          ObligationsActorDocumentation
          SHALL:able-to-populateProducer

          EHR system SHALL be able to populate administrative gender of the patient using valid code fro agreed code system.

          SHALL:displayConsumer
          12. EHDSPatient.address
          Definition

          The addresses are always sequences of address parts (e.g. street address line, country, postal code, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

          ShortMailing and home or office addresses.
          Control0..*
          Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSAddress
          14. EHDSPatient.telecom
          Definition

          Contact information.

          ShortContact information.
          Control0..*
          Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSTelecom

          Guidance on how to interpret the contents of this table can be foundhere

          0. EHDSPatient
          Logical ModelInstances of this logical model are not marked to be the target of a Reference
          2. EHDSPatient.identifier
          NoteThis is a business identifier, not a resource identifier (see discussion)
          Obligations
            ObligationsActorDocumentation
            SHALL:able-to-populateProducer

            EHR system SHALL be able to populate one or more business identifiers of the patient.

            SHOULD:displayConsumer

            SHALL process patient identifiers to ensure proper assignment of information.

            SHALL:processConsumer

            SHOULD display identifier when needed to users.

            4. EHDSPatient.name
            Obligations
              ObligationsActorDocumentation
              SHALL:able-to-populateProducer

              EHR system SHALL populate one or more names of the patient meeting conformity requirements on the name structure if a value is known and allowed to be shared.

              SHALL:displayConsumer
              6. EHDSPatient.dateOfBirth
              Obligations
                ObligationsActorDocumentation
                SHALL:able-to-populateProducer

                EHR system SHALL be able to populate date of birth of the patient.

                SHALL:displayConsumer
                8. EHDSPatient.administrativeGender
                Obligations
                  ObligationsActorDocumentation
                  SHALL:able-to-populateProducer

                  EHR system SHALL be able to populate administrative gender of the patient using valid code fro agreed code system.

                  SHALL:displayConsumer

                  Guidance on how to interpret the contents of this table can be foundhere

                  0. EHDSPatient
                  Definition

                  Model for information about a patient (subject of care).

                  ShortPatient model
                  Control0..*
                  Is Modifierfalse
                  Logical ModelInstances of this logical model are not marked to be the target of a Reference
                  2. EHDSPatient.identifier
                  Definition

                  An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).

                  ShortAn identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
                  NoteThis is a business identifier, not a resource identifier (see discussion)
                  Control1..*
                  TypeIdentifier
                  Obligations
                    ObligationsActorDocumentation
                    SHALL:able-to-populateProducer

                    EHR system SHALL be able to populate one or more business identifiers of the patient.

                    SHOULD:displayConsumer

                    SHALL process patient identifiers to ensure proper assignment of information.

                    SHALL:processConsumer

                    SHOULD display identifier when needed to users.

                    4. EHDSPatient.name
                    Definition

                    Name might consist of name parts, e.g. Given name or names, family name/surname, name prefix etc.

                    ShortName associated with the patient/subject.
                    Control0..*
                    Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSHumanName
                    Obligations
                      ObligationsActorDocumentation
                      SHALL:able-to-populateProducer

                      EHR system SHALL populate one or more names of the patient meeting conformity requirements on the name structure if a value is known and allowed to be shared.

                      SHALL:displayConsumer
                      6. EHDSPatient.dateOfBirth
                      Definition

                      Date of birth

                      ShortDate of birth
                      Control0..1
                      TypedateTime
                      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
                      Obligations
                        ObligationsActorDocumentation
                        SHALL:able-to-populateProducer

                        EHR system SHALL be able to populate date of birth of the patient.

                        SHALL:displayConsumer
                        8. EHDSPatient.deceased[x]
                        Definition

                        Whether the patient is deceased or date of death.

                        ShortWhether the patient is deceased or date of death.
                        Control0..1
                        TypeChoice of: boolean, dateTime
                        [x] NoteSeeChoice of Data Typesfor further information about how to use [x]
                        Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
                        10. EHDSPatient.administrativeGender
                        Definition

                        This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere.

                        ShortAdministrative gender
                        Control0..1
                        Binding

                        HL7 Administrative Gender

                        TypeCodeableConcept
                        Obligations
                          ObligationsActorDocumentation
                          SHALL:able-to-populateProducer

                          EHR system SHALL be able to populate administrative gender of the patient using valid code fro agreed code system.

                          SHALL:displayConsumer
                          12. EHDSPatient.address
                          Definition

                          The addresses are always sequences of address parts (e.g. street address line, country, postal code, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

                          ShortMailing and home or office addresses.
                          Control0..*
                          Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSAddress
                          14. EHDSPatient.telecom
                          Definition

                          Contact information.

                          ShortContact information.
                          Control0..*
                          Typehttp://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSTelecom