Generic Functions for data exchange - Implementation Guide - Local Development build (v26.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON

Data Type Profile: NVI Identifier - Mappings

Mappings for the nl-gf-nvi-identifier data type profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

Name	HL7 v2 Mapping	RIM Mapping	ServD
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
Identifier / id		n/a
Identifier / extension		n/a
Identifier / use	N/A	Role.code or implied by context
Identifier / type	CX.5	Role.code or implied by context
Identifier / system	CX.4 / EI-2-4	II.root or Role.id.root	./IdentifierType
Identifier / value	CX.1 / EI.1	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)	./Value
Identifier / period	CX.7 + CX.8	Role.effectiveTime or implied by context	./StartDate and ./EndDate
Identifier / 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
Documentation for this format