Mobile Cross-Enterprise Document Data Element Extraction (mXDE)
1.3.0 - Trial-Implementation International flag

This page is part of the Mobile Cross-Enterprise Document Data Element Extraction (mXDE) (v1.3.0: Publication) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Mobile Cross-Enterprise Document Data Element Extraction (mXDE)

Official URL: https://profiles.ihe.net/ITI/mXDE/ImplementationGuide/ihe.iti.mxde Version: 1.3.0
Active as of 2023-08-04 Computable Name: IHE_ITI_mXDE

This Mobiles Cross-Enterprise (mXDE) Profile provides the means to access data elements extracted from shared structured documents. The profile enables the deployment of health data exchange infrastructures where fine-grained access to health data coexists and complements the sharing of coarse-grained documents and the fine-grained data elements they contain.

Significant Changes, Open and Closed Issues

Organization of This Guide

This guide is organized into the following sections:

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.