Magentus Practice Management FHIR Implementation Guide - Local Development build (v1.2.35) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• Content
• Detailed Descriptions
• JSON

Data Type Profile: EOrdersDoctorNumber - Mappings

Draft as of 2025-03-02

Mappings for the eorders-doctornumber data type profile.

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

EOrdersDoctorNumber
Identifier	CX / EI (occasionally, more often EI maps to a resource id or a URL)
use	N/A
type	CX.5
system	CX.4 / EI-2-4
value	CX.1 / EI.1
period	CX.7 + CX.8
assigner	CX.4 / (CX.4,CX.9,CX.10)

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

EOrdersDoctorNumber
Identifier	n/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]
id	n/a
extension	n/a
use	Role.code or implied by context
type	Role.code or implied by context
system	II.root or Role.id.root
value	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period	Role.effectiveTime or implied by context
assigner	II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
id	n/a
extension	n/a
reference	N/A
type	N/A
identifier	.identifier
display	N/A

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

EOrdersDoctorNumber
Identifier	Identifier
system	./IdentifierType
value	./Value
period	./StartDate and ./EndDate
assigner	./IdentifierIssuingAuthority