ÚNICAS Rare Diseases HL7 FHIR Implementation Guide
0.0.1 - draft

ÚNICAS Rare Diseases HL7 FHIR Implementation Guide - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: UNICASAppointment - Mappings

Draft as of 2025-08-12

Mappings for the UNICASAppointment resource profile.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameWorkflow PatternFiveWs Pattern MappingRIM MappingiCalendarHL7 V2 Mappingdoco
.. Appointment
Request
workflow.scheduling
  • Entity
  • Role
  • or Act
  • Act[@moodCode <= 'INT']
VEVENT
... id
... meta
... implicitRules
... language
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... identifier
Request.identifier
FiveWs.identifier
.id
UID
  • SCH-1
  • SCH-2
  • ARQ-1
  • ARQ-2
.... 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)
... status
Request.status
FiveWs.status
.statusCode
STATUS
SCH-25
... cancellationReason
n/a
... class
FiveWs.class
.inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
PV1-2
... serviceCategory
  • n/a
  • might be inferred from the ServiceDeliveryLocation
CATEGORIES
.... 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
... serviceType
Request.code
  • n/a
  • might be inferred from the ServiceDeliveryLocation
  • ARQ-8
  • SCH-8
.... id
n/a
.... extension
n/a
.... concept
N/A
..... 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
.... reference
N/A
... specialty
FiveWs.class
.performer.AssignedPerson.code
... appointmentType
.code
CLASSIFICATION
  • ARQ-7
  • SCH-7
... reason
Request.reason
.reasonCode
AIS-3
.... id
n/a
.... extension
n/a
.... concept
N/A
..... 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
.... reference
N/A
... priority
Request.priority
FiveWs.class
.priorityCode
PRIORITY
  • ARQ-12
  • SCH-11.6 / TQ1-9
... description
.text
SUMMARY
NTE-3
... replaces
Request.replaces
FiveWs.context
.inboundRelationship[@typeCode = 'SPRT'].observation
ATTACH
... virtualService
N/A
... supportingInformation
Request.supportingInfo
FiveWs.context
.inboundRelationship[@typeCode = 'SPRT'].observation
ATTACH
... previousAppointment
FiveWs.context
N/A
... originatingAppointment
FiveWs.context
N/A
... start
Request.occurrence[x]
FiveWs.init
.effectiveTime.low
DTSTART
  • ARQ-11.1
  • SCH-11.4 / TQ1-7
... end
Request.occurrence[x]
FiveWs.done[x]
.effectiveTime.high
DTEND
SCH-11.5 / TQ1-8/ calculated based on the start and the duration which is in ARQ-9
... minutesDuration
Request.occurrence[x]
  • type = ('SXPR_TS'
  • 'PIVL_TS')].width
DURATION (e.g. PT15M)
... requestedPeriod
Request.occurrence[x]
  • type = ('SXPR_TS'
  • 'PIVL_TS')]
ARQ-11
... slot
.outboundRelationship[@typeCode = 'REFR'].act[@classCode = 'ACT'][@moodCode = 'SLOT']
... account
.pertains.A_Account
... created
Request.authoredOn
.author.time
CREATED
... cancellationDate
... note
Request.note
.subjectOf.observation[@moodCode = 'EVN'][code = 'annotation'].value
DESCRIPTION (for internal use)
NTE-3
.... id
n/a
.... extension
n/a
.... author[x]
Act.participant[typeCode=AUT].role
N/A
.... time
Act.effectiveTime
N/A
.... text
Act.text
N/A
... patientInstruction
.subjectOf.observation[@moodCode = 'EVN'][code = 'annotation'].value
DESCRIPTION (for patient use)
NTE-3
... basedOn
Request.basedOn
.outboundRelationship[@typeCode = 'FLFS'].act[@classCode < 'ActCareProvisionRequestType'][@moodCode = 'RQO']
... subject
FiveWs.who
subject.patient
PID-3-Patient ID List
.... 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
....... 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
..... 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
... Slices for participant
  • Request.performer
  • Request.subject
performer | reusableDevice | subject | location
ATTENDEE component to be created
  • PID
  • AIP
  • AIG
  • AIL
.... participant:All Slices
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... type
(performer | reusableDevice | subject | location).@typeCode
n/a
  • AIP-4
  • AIG-4
..... period
n/a
..... actor
FiveWs.who
performer.person | reusableDevice.manufacturedDevice | subject.patient | location.serviceDeliveryLocation
(Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
PID-3-Patient ID List | AIL-3 | AIG-3 | AIP-3
..... required
(performer | reusableDevice | subject | location).@performInd
ROLE=REQ-PARTICIPANT (roleparam)
..... status
(performer | reusableDevice | subject | location).statusCode
mailto:john@doe.com (rsvpparam | partstatparam)
  • AIP-12
  • AIG-14
.... participant:ProfesionalSanitarioParticipante
  • Request.performer
  • Request.subject
performer | reusableDevice | subject | location
ATTENDEE component to be created
  • PID
  • AIP
  • AIG
  • AIL
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... type
(performer | reusableDevice | subject | location).@typeCode
n/a
  • AIP-4
  • AIG-4
..... period
n/a
..... actor
FiveWs.who
performer.person | reusableDevice.manufacturedDevice | subject.patient | location.serviceDeliveryLocation
(Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
PID-3-Patient ID List | AIL-3 | AIG-3 | AIP-3
...... id
n/a
...... extension
n/a
...... reference
N/A
...... type
N/A
...... identifier
.identifier
....... id
n/a
....... Slices for extension
n/a
........ extension:numeroColegiadoProfesionalSanitario
....... 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
......... 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
....... 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
..... required
(performer | reusableDevice | subject | location).@performInd
ROLE=REQ-PARTICIPANT (roleparam)
..... status
(performer | reusableDevice | subject | location).statusCode
mailto:john@doe.com (rsvpparam | partstatparam)
  • AIP-12
  • AIG-14
.... participant:ServicioAsistencialParticipante
  • Request.performer
  • Request.subject
performer | reusableDevice | subject | location
ATTENDEE component to be created
  • PID
  • AIP
  • AIG
  • AIL
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... type
(performer | reusableDevice | subject | location).@typeCode
n/a
  • AIP-4
  • AIG-4
..... period
n/a
..... actor
FiveWs.who
performer.person | reusableDevice.manufacturedDevice | subject.patient | location.serviceDeliveryLocation
(Need to provide the common name CN and also the MAILTO properties from the practitioner resource) where the participant type is not "information-only"
PID-3-Patient ID List | AIL-3 | AIG-3 | AIP-3
...... 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
....... 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
..... required
(performer | reusableDevice | subject | location).@performInd
ROLE=REQ-PARTICIPANT (roleparam)
..... status
(performer | reusableDevice | subject | location).statusCode
mailto:john@doe.com (rsvpparam | partstatparam)
  • AIP-12
  • AIG-14
... recurrenceId
N/A
... occurrenceChanged
N/A
... recurrenceTemplate
N/A
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... timezone
N/A
TZID
.... recurrenceType
FREQ
.... lastOccurrenceDate
UNTIL
.... occurrenceCount
COUNT
.... occurrenceDate
RDATE
.... weeklyTemplate
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... monday
..... tuesday
..... wednesday
..... thursday
..... friday
..... saturday
..... sunday
..... weekInterval
.... monthlyTemplate
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... dayOfMonth
..... nthWeekOfMonth
..... dayOfWeek
..... monthInterval
.... yearlyTemplate
..... id
n/a
..... extension
n/a
..... modifierExtension
N/A
..... yearInterval
.... excludingDate
EXDATE
.... excludingRecurrenceId

doco Documentation for this format

ÚNICAS está impulsado por el Consejo Interterritorial del Sistema Nacional de Salud, y financiado con fondos Next Generation de la Unión Europea, en el marco del Plan de Recuperación, Transformación y Resiliencia del Gobierno de España. El Ministerio de Sanidad ejerce la coordinación del proyecto, y Cataluña lidera la parte del desarrollo de los activos tecnológicos para su implementación.