VigiCanPY - Local Development build (v0.9.0). See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Examples
• XML
• JSON
• TTL

Resource Profile: DatosHistoriaPY - Mappings

Active as of 2023-07-19

Mappings for the DatosHistoriaPY resource profile.

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

DatosHistoriaPY
Encounter	Event
identifier	Event.identifier
status	Event.status
type	Event.code
serviceType	Event.code
subject	Event.subject
episodeOfCare	Event.context
basedOn	Event.basedOn
participant	Event.performer
type	Event.performer.function
individual	Event.performer.actor
appointment	Event.basedOn
period	Event.occurrence[x]
length	Event.occurrence[x]
reasonCode	Event.reasonCode
reasonReference	Event.reasonCode
diagnosis
condition	Event.reasonReference
location
location	Event.location
serviceProvider	Event.performer.actor
partOf	Event.partOf

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

DatosHistoriaPY
Encounter	Entity. Role, or Act, Encounter[@moodCode='EVN']
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	.id
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
status	.statusCode
statusHistory	n/a
id	n/a
extension	n/a
modifierExtension	N/A
status	n/a
period	n/a
class	.inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
classHistory	n/a
id	n/a
extension	n/a
modifierExtension	N/A
class	n/a
period	n/a
type	.code
serviceType	n/a
priority	.priorityCode
subject	.participation[typeCode=SBJ]/role[classCode=PAT]
episodeOfCare	n/a
basedOn	.reason.ClinicalDocument
participant	.participation[typeCode=PFM]
id	n/a
extension	n/a
modifierExtension	N/A
type	.functionCode
period	.time
individual	.role
appointment	.outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
period	.effectiveTime (low & high)
length	.lengthOfStayQuantity
reasonCode	.reasonCode
reasonReference	.reasonCode
diagnosis	.outboundRelationship[typeCode=RSON]
id	n/a
extension	n/a
modifierExtension	N/A
condition	.outboundRelationship[typeCode=RSON].target
use	n/a
rank	.outboundRelationship[typeCode=RSON].priority
account	.pertains.A_Account
hospitalization	.outboundRelationship[typeCode=COMP].target[classCode=ENC, moodCode=EVN]
id	n/a
extension	n/a
modifierExtension	N/A
preAdmissionIdentifier	.id
origin	.participation[typeCode=ORG].role
admitSource	.admissionReferralSourceCode
reAdmission	n/a
dietPreference	.outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
specialCourtesy	.specialCourtesiesCode
specialArrangement	.specialArrangementCode
destination	.participation[typeCode=DST]
dischargeDisposition	.dischargeDispositionCode
location	.participation[typeCode=LOC]
id	n/a
extension	n/a
modifierExtension	N/A
location	.role
status	.role.statusCode
period	.time
serviceProvider	.particiaption[typeCode=PFM].role
partOf	.inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]

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

DatosHistoriaPY
Encounter
identifier	FiveWs.identifier
status	FiveWs.status
class	FiveWs.class
type	FiveWs.class
priority	FiveWs.grade
subject	FiveWs.subject[x], FiveWs.subject
episodeOfCare	FiveWs.context
participant
individual	FiveWs.who
period	FiveWs.done[x]
reasonCode	FiveWs.why[x]
reasonReference	FiveWs.why[x]
diagnosis
condition	FiveWs.why[x]
location
location	FiveWs.where[x]

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

DatosHistoriaPY
Encounter
identifier	PV1-19
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)
status	No clear equivalent in HL7 v2; active/finished could be inferred from PV1-44, PV1-45, PV2-24; inactive could be inferred from PV2-16
class	PV1-2
type	PV1-4 / PV1-18
serviceType	PV1-10
priority	PV2-25
subject	PID-3
episodeOfCare	PV1-54, PV1-53
participant	ROL
type	ROL-3 (or maybe PRT-4)
period	ROL-5, ROL-6 (or maybe PRT-5)
individual	ROL-4
appointment	SCH-1 / SCH-2
period	PV1-44, PV1-45
length	(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes
reasonCode	EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
reasonReference	EVN-4 / PV2-3 (note: PV2-3 is nominally constrained to inpatient admissions; HL7 v2 makes no vocabulary suggestions for PV2-3; would not expect PV2 segment or PV2-3 to be in use in all implementations )
diagnosis
condition	Resources that would commonly referenced at Encounter.indication would be Condition and/or Procedure. These most closely align with DG1/PRB and PR1 respectively.
hospitalization
preAdmissionIdentifier	PV1-5
admitSource	PV1-14
reAdmission	PV1-13
dietPreference	PV1-38
specialCourtesy	PV1-16
specialArrangement	PV1-15 / OBR-30 / OBR-43
destination	PV1-37
dischargeDisposition	PV1-36
location
location	PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43
serviceProvider	PL.6 & PL.1