Implementation Guide
Telematikinfrastruktur (TI) Common
Version 1.1.1-ballot.1 - draft

Data Type Profile: MedicationPlanIdentifier - Mappings

Draft as of 2025-08-01

Mappings for the medication-plan-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
... use
N/A
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