Extensions for Using Data Elements from FHIR R4 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R4 in FHIR R4B - Downloaded Version null See the Directory of published versions

Resource Profile: Profile_R4_AppointmentResponse_R4B - Mappings

Page standards status: Trial-use Maturity Level: 0

Mappings for the profile-AppointmentResponse resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternRIM MappingiCalendarFiveWs Pattern MappingHL7 v2 Mappingdoco
.. AppointmentResponse
Request
Appointment[@moodCode <= 'PRMS']
VEVENT
workflow.scheduling
... id
... meta
... implicitRules
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... identifier
Request.identifier
.id
UID
FiveWs.identifier
... appointment
Request.basedOn
scheduleRequest.ActAppointmentRequest[@moodCode <= 'ARQ']
... start
Request.occurrence[x]
.effectiveTime.low
FiveWs.init
... end
Request.occurrence[x]
.effectiveTime.high
FiveWs.done[x]
... participantType
Request.performerType
(performer | reusableDevice | subject | location).@typeCode
n/a
... actor
Request.performer
performer.person | reusableDevice.manufacturedDevice | subject.patient | location.serviceDeliveryLocation
(Need to provide the common name CN and also the MAILTO properties from the practitioner resource)
FiveWs.who
PID-3-Patient ID List
... participantStatus
Request.status
(performer | reusableDevice | subject | location).statusCode
mailto:BPostlethwaite@data.com (rsvpparam | partstatparam)
... comment
Request.note
.subjectOf.observation[@moodCode = 'EVN'][code = 'annotation'].value
COMMENT

doco Documentation for this format