Mapped version 0.2.1: https://www.xt-ehr.eu/fhir/models/0.2.1/index.html

(Current published version 0.3.0: https://www.xt-ehr.eu/fhir/models/)

Legend:

Red indicates a gap/difference between the EHDS LM and openEHR archetypes.

Blue means that the data item has not been modelled in the mapping templates.

Orange highlights a suggestion for a Change Request in an openEHR archetype.

Purple comments highlight differences between the EHDS LM and IPS/EPS/EU core FHIR profiles.

In addition, differences between versions 0.2.1 and 0.3.0 of the EHDS LMs are noted in the separate highlighted comments.

EHDS Logical Models / openEHR Mapping Comments [IN PROGRESS]

Common Data Elements

Empty Reason

• Definition: “Reason for absence of data”
• The reason why a section is empty can be handled by two separate archetypes in openEHR:
  • The Exclusion - global EVALUATION archetype records explicit exclusions of allergies, problems, medications, procedures or family history - this may be because it has been tested or because the patient/carer indicated that they do not have any known allergies/problems/medications etc
    • On the FHIR side this relates to the emptyReason code nilknown, which is to be used to assert a clinical judgment that there are no known items for this list after reasonable investigation
      • Note that this a positive statement by a clinical user, and not a default position asserted by a computer system in the lack of other information
• The Absence of information EVALUATION archetype is used to record an explicit statement that specified health information is not available for inclusion in the health record or record extract at the time of recording
  • On the FHIR side this may relate to any other emptyReason code (excluding nilknown), i.e. notasked, withheld, unavailable, notstarted and closed
• We have used both archetypes in each section template, with the exception of EHDS Medical Devices and Implants (see section 4 for comments)

Narrative