Crate eehrxf 

The European interoperability software component of an EHR system (Regulation (EU) 2025/327 Art 2(2)(n), Art 15, Art 25(1)).

The Regulation asks an EHR system to provide and receive personal electronic health data of the priority categories of Art 14(1) in the European electronic health record exchange format. Until the Art 15(1) implementing act fixes that format, this crate holds the published proxies for it:

• dataset: the format-neutral dataset model, read as data from the Xt-EHR EHDS Logical Information Models package and keyed on its element paths, with the producer and consumer obligations of each element;
• category: the priority categories this build carries, one Cargo feature each, and the logical model and obligations profile of each;
• crosswalk: per category, the crosswalk from the Xt-EHR element paths to the eHealth Network element ids and to the elements and slices of the HL7 Europe profile, with the FHIRconnect contexts admitted to feed each, checked against the packages it names;
• document (features patient-summary and fhir-r4): the patient summary document, a FHIR R4 Bundle of the HL7 Europe Patient Summary profiles, assembled from the resources and sections a caller gives;
• mapping (feature openehr, which turns on fhir-r4): a FHIRconnect 1.0.0 mapping, compiled once against an operational template and run in process over a canonical-JSON composition, answering FHIR R4 resources with their Provenance;
• medication (feature fhir-r4 with prescription or dispensation): the electronic prescription and dispensation datasets, read from and written as the HL7 Europe Medication Prescription and Dispense resources, and checked against those profiles;
• receive (feature fhir-r4): a document received in the exchange format, read under the R4 document rules and checked against the profiles of its category; with openehr, mapped into one openEHR composition that keeps the original document beside the mapped content;
• terminology (feature fhir-r4): the terminology rules: a code as recorded, an equivalent mapping as a second coding and every other one in the narrative (with openehr), the required bindings held to the vendored expansions, and the seam to an optional FHIR terminology server, which fails closed when none is configured;
• transformation (feature fhir-r4): what one semantic transformation did, the facts the system that applied it logs (eHealth Network General Guidelines Release 3.1 Art 6(3)): the mapping and terminology versions in force and the elements transcoded, untranscoded and dropped, counted by path and never by value.

The feature fhir-r4 is the FHIR R4 serialisation and compiles no openEHR crate; only openehr brings in the openEHR side the mapping reads.

The crate depends on no logging component and on nothing of the system that serves the documents, so the interoperability component stays independent of the logging component (Art 2(2)(n), (o)).

Examples

use eehrxf::dataset::DatasetModel;

let package = std::fs::File::open("xtehr.eu.ehds.models-1.0.0.tgz")?;
let model = DatasetModel::read(package)?;
let summary = model
    .model("http://www.xt-ehr.eu/fhir/models/StructureDefinition/EHDSPatientSummary")
    .ok_or("the package holds no patient summary model")?;
assert!(summary.element("EHDSPatientSummary.allergiesAndIntolerances").is_some());

Modules

category

The priority categories of Art 14(1) this build carries.

crosswalk

The crosswalk of a category’s dataset to the eHealth Network guideline and to the HL7 Europe profile of its document.

dataset

The format-neutral dataset model of the exchange format.