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/stakeholder-consultation-D6-2 and changes regularly. See the Directory of published versions

## Logical Model: Health professional model

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

EHDS refined base model for Health professional (HP)

Usage:

- Use this Logical Model Profile: Condition model, DataSet model, Device use model, Document model... Show 13 more, Hospital Discharge Report body model, Hospital Discharge Report header model, Imaging report body model, Imaging report header model, Immunization model, Laboratory order body model, Laboratory order header model, Laboratory report body model, Medication dispense model, Medication prescription model, Observation model, Patient summary model and Procedure model
- Refer to this Logical Model Profile: Alert flag model, Encounter model, Hospital Discharge Report header model, Imaging report header model... Show 4 more, Laboratory order header model, Laboratory report header model, Media model and Observation model

### Formal Views of Profile Content

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

- Key Elements Table
- Differential Table
- Snapshot Table
- Statistics/References
- All

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

This structure is derived from Base

Summary

Key Elements View

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

Differential View

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

Snapshot View

Name | Flags | Card. | Type | Description & Constraints
--- | --- | --- | --- | ---
EHDSHealthProfessional |  | 0..* | Base | Health professional model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.
name |  | 0..1 | EHDSHumanName | Name of the health professional that has been treating or taking responsibility for the patient.
address |  | 0..1 | EHDSAddress | Mailing and office or home addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, 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.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.
role |  | 0..* | CodeableConcept | Health professional role. Multiple roles could be provided. Binding Description (No ValueSet): (preferred): ISCO, SNOMED CT
organization |  | 0..1 | EHDSOrganization | The organization where this role is available
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that describes the functional role they are practicing at a given organization
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSHealthProfessional.role | preferred |

This structure is derived from Base

Summary

Other representations of profile: CSV, Excel