Magentus Practice Management FHIR Implementation Guide
1.2.60 - ci-build Australia flag

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

Resource Profile: EOrdersCoverage - Mappings

Active as of 2026-04-05

Mappings for the eorders-coverage resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternRIM MappingFiveWs Pattern MappingCanadian Dental Association eclaims standardHL7 v2 MappingCanadian Pharmacy Associaiton eclaims standarddoco
.. Coverage
Event
Coverage
... id
... meta
... implicitRules
... language
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... Slices for identifier
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]
  • CX / EI (occasionally
  • more often EI maps to a resource id or a URL)
.... identifier:mcn
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]
  • CX / EI (occasionally
  • more often EI maps to a resource id or a URL)
..... id
n/a
..... extension
n/a
..... use
Role.code or implied by context
N/A
..... type
Role.code or implied by context
CX.5
..... system
II.root or Role.id.root
CX.4 / EI-2-4
..... value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
CX.1 / EI.1
..... period
Role.effectiveTime or implied by context
CX.7 + CX.8
...... id
n/a
...... extension
n/a
...... start
./low
DR.1
...... end
./high
DR.2
..... assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
.... identifier:dva
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]
  • CX / EI (occasionally
  • more often EI maps to a resource id or a URL)
..... id
n/a
..... extension
n/a
..... use
Role.code or implied by context
N/A
..... type
Role.code or implied by context
CX.5
..... system
II.root or Role.id.root
CX.4 / EI-2-4
..... value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
CX.1 / EI.1
..... period
Role.effectiveTime or implied by context
CX.7 + CX.8
..... assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
.... identifier:insurancemembernumber
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]
  • CX / EI (occasionally
  • more often EI maps to a resource id or a URL)
... status
Event.status
Act.status
FiveWs.status
... type
FiveWs.class
IN1-15
.... id
n/a
.... extension
n/a
.... coding
  • union(.
  • ./translation)
  • C*E.1-8
  • C*E.10-22
..... id
n/a
..... extension
n/a
..... system
./codeSystem
C*E.3
..... version
./codeSystemVersion
C*E.7
..... code
./code
C*E.1
..... display
CV.displayName
C*E.2 - but note this is not well followed
..... userSelected
CD.codingRationale
Sometimes implied by being first
.... text
./originalText[mediaType/code="text/plain"]/data
C*E.9. But note many systems use C*E.2 for this
... policyHolder
FiveWs.subject
D01 through D09
  • IN1-16
  • 18
  • 19-name of insured
  • address
  • date of birth
C.35
... subscriber
FiveWs.subject
D01 through D09
  • IN1-16
  • 18
  • 19-name of insured
  • address
  • date of birth
C.35
... subscriberId
FiveWs.subject
D01 through D09
  • IN1-16
  • 18
  • 19-name of insured
  • address
  • date of birth
C.35
... beneficiary
Event.subject
FiveWs.subject
D01 through D09
  • IN1-16
  • 18
  • 19-name of insured
  • address
  • date of birth
C.35
.... id
n/a
.... extension
n/a
.... reference
N/A
.... type
N/A
.... identifier
.identifier
.... display
N/A
... dependent
C17
- No exact HL7 v2 equivalent concept seems to exist;
... relationship
C03
... period
Event.occurrence[x]
Act.effectiveTime
FiveWs.done[x]
IN1-12 / IN1-13
... payor
FiveWs.author
A05
IN1-3
C.30
.... id
n/a
.... extension
n/a
.... reference
N/A
.... type
N/A
.... identifier
.identifier
..... id
n/a
..... extension
n/a
..... use
Role.code or implied by context
N/A
..... type
Role.code or implied by context
CX.5
...... id
n/a
...... extension
n/a
...... coding
  • union(.
  • ./translation)
  • C*E.1-8
  • C*E.10-22
...... text
./originalText[mediaType/code="text/plain"]/data
C*E.9. But note many systems use C*E.2 for this
..... system
II.root or Role.id.root
CX.4 / EI-2-4
..... value
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
CX.1 / EI.1
..... period
Role.effectiveTime or implied by context
CX.7 + CX.8
..... assigner
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
.... display
N/A
... class
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... type
.... value
  • C11 (Division
  • Section)
IN1-8
C.31
.... name
  • C11 (Division
  • Section)
IN1-8
C.31
... order
- No exact HL7 v2 equivalent concept seems to exist;
... network
D10
... costToBeneficiary
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... type
.... value[x]
  • C11 (Division
  • Section)
IN1-8
C.31
.... exception
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... type
..... period
... subrogation
... contract
n/a
D01 through D09
  • IN1-16
  • 18
  • 19
C.35

doco Documentation for this format