Mobile access to Health Documents (MHD)
4.2.3 - Trial-Implementation International flag

Mobile access to Health Documents (MHD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 4.2.3 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.MHD/ and changes regularly. See the Directory of published versions

Data Type Profile: EntryUUIDIdentifier - Mappings

Active as of 2025-10-30

Mappings for the IHE.MHD.EntryUUID.Identifier data type profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameHL7 v2 MappingRIM MappingServDdoco
.. Identifier
  • CX / EI (occasionally
  • more often EI maps to a resource id or a URL)
II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT]
Identifier
... id
n/a
... extension
n/a
... use
N/A
Role.code or implied by context
... type
CX.5
Role.code or implied by context
... system
CX.4 / EI-2-4
II.root or Role.id.root
./IdentifierType
... value
CX.1 / EI.1
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
./Value
... period
CX.7 + CX.8
Role.effectiveTime or implied by context
./StartDate and ./EndDate
... assigner
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
./IdentifierIssuingAuthority

doco Documentation for this format