Understand IHE mXDE (Mobile Cross-Enterprise Document Data Element Extraction) concepts and use cases

Steps

1. Review the IHE mXDE profile (ITI Technical Framework Supplement) to understand its purpose: mXDE enables FHIR-based access to data elements extracted from clinical documents stored in an IHE XDS or MHD repository, without requiring the consumer to parse full CDA or PDF documents.
2. Understand that mXDE acts as a translation layer: a Document Data Element Extractor (DDEE) actor reads documents from an XDS repository and maps their contents to FHIR resources (such as Condition, Observation, MedicationRequest), making them queryable via FHIR search.
3. Identify the provenance chain mXDE creates: each extracted FHIR resource is linked back to its source document via a FHIR Provenance resource, so consumers can trace any data element to the originating clinical document.
4. Understand that mXDE is complementary to MHD — consumers can use MHD to retrieve full documents and mXDE to access granular FHIR resources extracted from those documents, choosing the appropriate access pattern for their use case.
5. Recognize that mXDE's FHIR resources are derived views of document content; the authoritative source remains the original document, so clinical decisions should consider source document context.
6. Verify current IHE mXDE profile details and actor definitions against the published IHE ITI Technical Framework supplement, as profile details may be updated.