Implementation Guide for FFB messaging (FFB udvekslingsdatasæt)
1.0.0 - release Denmark flag

This page is part of the KLFFBMessaging (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Data Type Profile: KLMessagingFFBEANIdentifier - Mappings

Active as of 2023-08-27

Mappings for the kl-messaging-ffb-eanIdentifier data type profile.

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

KLMessagingFFBEANIdentifier
IdentifierCX / EI (occasionally, more often EI maps to a resource id or a URL)
   useN/A
   typeCX.5
   systemCX.4 / EI-2-4
   valueCX.1 / EI.1
   periodCX.7 + CX.8
   assignerCX.4 / (CX.4,CX.9,CX.10)

Mappings for RIM Mapping (http://hl7.org/v3)

KLMessagingFFBEANIdentifier
Identifiern/a, 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]
   idn/a
   extensionn/a
   useRole.code or implied by context
   typeRole.code or implied by context
   systemII.root or Role.id.root
   valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
   periodRole.effectiveTime or implied by context
   assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper

Mappings for ServD (http://www.omg.org/spec/ServD/1.0/)

KLMessagingFFBEANIdentifier
IdentifierIdentifier
   system./IdentifierType
   value./Value
   period./StartDate and ./EndDate
   assigner./IdentifierIssuingAuthority