HL7中国FHIR Connectathon测试实施指南 - Local Development build (v2024.5.5) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

• 内容
• 详细描述
• 映射
• 示例
• XML
• JSON
• TTL

Resource Profile: Covid19Encounter - Mappings

Mappings for the profile-covid19-encounter resource profile.

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

Covid19Encounter
Encounter	Event
identifier	Event.identifier
status	Event.status
type	Event.code
serviceType	Event.code
subject	Event.subject
basedOn	Event.basedOn
partOf	Event.partOf
serviceProvider	Event.performer.actor
participant	Event.performer
type	Event.performer.function
actor	Event.performer.actor
appointment	Event.basedOn
actualPeriod	Event.occurrence[x]
length	Event.occurrence[x]
reason
value	Event.reason
diagnosis
condition	Event.reason
location
location	Event.location

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

Covid19Encounter
Encounter	workflow.encounter
identifier	FiveWs.identifier
status	FiveWs.status
class	FiveWs.class
priority	FiveWs.grade
type	FiveWs.what[x]
subject	FiveWs.subject[x]
episodeOfCare	FiveWs.context
participant
actor	FiveWs.who
actualPeriod	FiveWs.done[x]
reason
value	FiveWs.why[x]
diagnosis
condition	FiveWs.why[x]
location
location	FiveWs.where[x]

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

Covid19Encounter
Encounter	Entity, Role, or Act,PatientEncounter[@moodCode='EVN']
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	.id
status	.statusCode
class	.inboundRelationship[typeCode=SUBJ].source[classCode=LIST].code
priority	.priorityCode
type	.code
id	n/a
extension	n/a
coding	union(., ./translation)
text	./originalText[mediaType/code="text/plain"]/data
serviceType	n/a
subject	.participation[typeCode=SBJ]/role[classCode=PAT]
episodeOfCare	n/a
basedOn	.reason.ClinicalDocument
careTeam	n/a
partOf	.inboundRelationship[typeCode=COMP].source[classCode=COMP, moodCode=EVN]
serviceProvider	.participation[typeCode=PRF].role
participant	.participation[typeCode=PRF]
id	n/a
extension	n/a
modifierExtension	N/A
type	.functionCode
period	.time
actor	.role
appointment	.outboundRelationship[typeCode=FLFS].target[classCode=ENC, moodCode=APT]
virtualService	N/A
actualPeriod	.effectiveTime (low & high)
length	.lengthOfStayQuantity
reason
id	n/a
extension	n/a
modifierExtension	N/A
value	.reasonCode
diagnosis	.outboundRelationship[typeCode=RSON]
id	n/a
extension	n/a
modifierExtension	N/A
condition	.outboundRelationship[typeCode=RSON].target
use	n/a
account	.pertains.A_Account
dietPreference	.outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=EVN, code="diet"]
specialArrangement	.specialArrangementCode
specialCourtesy	.specialCourtesiesCode
admission	.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
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

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

Covid19Encounter
Encounter
identifier	PV1-19
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
priority	PV2-25
type	PV1-4 / PV1-18
coding	C*E.1-8, C*E.10-22
text	C*E.9. But note many systems use C*E.2 for this
serviceType	PV1-10
subject	PID-3
episodeOfCare	PV1-54, PV1-53
serviceProvider	PL.6 & PL.1
participant	ROL
type	ROL-3 (or maybe PRT-4)
period	ROL-5, ROL-6 (or maybe PRT-5)
actor	ROL-4
appointment	SCH-1 / SCH-2
actualPeriod	PV1-44, PV1-45
plannedStartDate	PV2-8
plannedEndDate	PV2-9
length	(PV1-45 less PV1-44) iff ( (PV1-44 not empty) and (PV1-45 not empty) ); units in minutes or PV2-11 (which is actual length in days)
reason
value	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.
use	DG1-6 (Diagnosis Type)
dietPreference	PV1-38
specialArrangement	PV1-15 / OBR-30 / OBR-43
specialCourtesy	PV1-16
admission
preAdmissionIdentifier	PV1-5
admitSource	PV1-14
reAdmission	PV1-13
destination	PV1-37
dischargeDisposition	PV1-36
location
location	PV1-3 / PV1-6 / PV1-11 / PV1-42 / PV1-43