Mobile Cross-Enterprise Document Data Element Extraction (mXDE), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.3.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.mXDE/ and changes regularly. See the Directory of published versions

Significant Changes & Issues

Significant Changes

1.2.1

• add an example of a search set bundle
• switch away from #pattern slicing as that has been deprecated as duplicate of #value slicing

Significant Changes from Revision 1.2 (PDF)

1.3.0 Trial-Implementation

• Public Comment resolution
• Converted to an IG
• Moved definition of Provenance here from QEDm as that enables it to be more specific to where the data are transformed
• Added examples of transform and thus use of Provenance
• Include CapabilityStatements for the actors
• Architect using Content Consumer and grouping with Document Sharing
• Depends on MHD, PDQm, PIXm, and BALP

Issues

Submit an Issue

IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the ITI Public Comment form.

As issues are submitted they will be managed on the mXDE GitHub Issues, where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).

Open Issues

These issues were known as part of the publication and IHE invites comments.

The details are available on github at the link provided. Comments on these github issues are encouraged.

• mXDE_001: There is no “Transform Considerations” identified in mXDE, but should there be? Such as preserving original identifiers in the resulting FHIR Resources, even when those identifiers can’t be used to retrieve the original data, as they are still useful for de-duplication downstream.

Closed Issues

Purged for clarity. No new closed issues with the IG publisher version.