Magentus Practice Management FHIR Implementation Guide
1.2.16 - ci-build

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

## Resource Profile: EOrdersCommunicationRequestPatient - Mappings

Draft as of 2024-08-15

Mappings for the eorders-communicationrequest-patient resource profile.

### Mappings for Workflow Pattern (http://hl7.org/fhir/workflow)

EOrdersCommunicationRequestPatient
CommunicationRequest | Request
identifier | Request.identifier
basedOn | Request.basedOn
replaces | Request.replaces
status | Request.status
statusReason | Request.statusReason
priority | Request.priority
doNotPerform | Request.doNotPerform
subject | Request.subject
about | Request.supportingInfo
encounter | Request.context
payload |
content[x] | Request.note
occurrence[x] | Request.occurrence[x]
authoredOn | Request.authoredOn
requester | Request.requester
recipient | Request.performer
sender | Request.performer
reasonCode | Request.reasonCode
reasonReference | Request.reasonReference
note | Request.note

### Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

EOrdersCommunicationRequestPatient
CommunicationRequest |
identifier | FiveWs.identifier
status | FiveWs.status
category | FiveWs.class
priority | FiveWs.grade
subject | FiveWs.subject[x], FiveWs.subject
about | FiveWs.context
encounter | FiveWs.context
occurrence[x] | FiveWs.planned
authoredOn | FiveWs.recorded
requester | FiveWs.author
recipient | FiveWs.actor
sender | FiveWs.actor
reasonCode | FiveWs.why[x]
reasonReference | FiveWs.why[x]

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

EOrdersCommunicationRequestPatient
CommunicationRequest | Entity. Role, or Act
text | Act.text?
contained | N/A
extension | N/A
modifierExtension | N/A
basedOn | .outboundRelationship[typeCode=FLFS].target
replaces | .outboundRelationship[typeCode=RPLC].target
groupIdentifier | 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]
statusReason | .inboundRelationship[typeCode=SUBJ].source[classCode=CACT, moodCode=EVN].reasonCOde
medium |
id | n/a
extension | n/a
coding | union(., ./translation)
text | ./originalText[mediaType/code="text/plain"]/data
about |
id | n/a
extension | n/a
reference | N/A
type | N/A
identifier | .identifier
display | N/A
payload |
id | n/a
extension | n/a
modifierExtension | N/A
requester | .participation[typeCode=AUT].role
id | n/a
extension | n/a
reference | N/A
type | N/A
identifier | .identifier
display | N/A
recipient |
id | n/a
extension | n/a
reference | N/A
type | N/A
identifier | .identifier
display | N/A
sender |
id | n/a
extension | n/a
reference | N/A
type | N/A
identifier | .identifier
display | N/A
reasonCode | .reasonCode
reasonReference | .outboundRelationship[typeCode=RSON].target
note | .inboundRelationship(typeCode=SUBJ].source[classCode=ANNGEN, moodCode=EVN].value[xsi:type=ST]