HL7 Vietnam VN Core FHIR Implementation Guide

Bộ Hướng dẫn Triển khai Core FHIR cho Việt Nam
0.4.0 - STU1 Draft Viet Nam cờ

Bộ Hướng dẫn Triển khai Core FHIR cho Việt Nam - Local Development build (v0.4.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Hồ sơ tài nguyên: Khoa/Phòng VN Core — VN Core Organization Department Profile - Ánh xạ

Draft tại thời điểm 2026-04-14

Ánh xạ cho vn-core-organization-department hồ sơ tài nguyên.

Mappings to Structures in this Implementation Guide

No Mappings Found

Mappings to other Structures

No Mappings Found

Other Mappings

NameHL7 v2 MappingRIM MappingServDFiveWs Pattern Mappingdoco
.. Organization
(also see master files messages)
  • Organization(classCode=ORG
  • determinerCode=INST)
Organization
... id
... meta
... implicitRules
... text
Act.text?
... contained
N/A
... extension
N/A
... modifierExtension
N/A
... Slices for identifier
XON.10 / XON.3
.scopes[Role](classCode=IDENT)
./Identifiers
FiveWs.identifier
.... identifier:departmentCode
XON.10 / XON.3
.scopes[Role](classCode=IDENT)
./Identifiers
FiveWs.identifier
..... id
n/a
..... extension
n/a
..... use
N/A
Role.code or implied by context
..... type
CX.5
Role.code or implied by context
...... id
n/a
...... extension
n/a
...... coding
  • C*E.1-8
  • C*E.10-22
  • union(.
  • ./translation)
...... text
C*E.9. But note many systems use C*E.2 for this
./originalText[mediaType/code="text/plain"]/data
..... system
CX.4 / EI-2-4
II.root or Role.id.root
./IdentifierType
..... value
CX.1 / EI.1
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
./Value
..... period
CX.7 + CX.8
Role.effectiveTime or implied by context
./StartDate and ./EndDate
..... assigner
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
./IdentifierIssuingAuthority
.... identifier:localCode
XON.10 / XON.3
.scopes[Role](classCode=IDENT)
./Identifiers
FiveWs.identifier
..... id
n/a
..... extension
n/a
..... use
N/A
Role.code or implied by context
..... type
CX.5
Role.code or implied by context
...... id
n/a
...... extension
n/a
...... coding
  • C*E.1-8
  • C*E.10-22
  • union(.
  • ./translation)
...... text
C*E.9. But note many systems use C*E.2 for this
./originalText[mediaType/code="text/plain"]/data
..... system
CX.4 / EI-2-4
II.root or Role.id.root
./IdentifierType
..... value
CX.1 / EI.1
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
./Value
..... period
CX.7 + CX.8
Role.effectiveTime or implied by context
./StartDate and ./EndDate
..... assigner
  • CX.4 / (CX.4
  • CX.9
  • CX.10)
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
./IdentifierIssuingAuthority
... active
No equivalent in HL7 v2
.status
  • ./Status (however this concept in ServD more covers why the organization is active or not
  • could be delisted
  • deregistered
  • not operational yet) this could alternatively be derived from ./StartDate and ./EndDate and given a context date.
FiveWs.status
... type
No equivalent in v2
.code
n/a
FiveWs.class
... name
XON.1
.name
.PreferredName/Name
... alias
.name
... telecom
ORC-22?
.telecom
./ContactPoints
... address
ORC-23?
.address
./PrimaryAddress and ./OtherAddresses
... partOf
No equivalent in HL7 v2
.playedBy[classCode=Part].scoper
n/a
... contact
.contactParty
.... id
n/a
.... extension
n/a
.... modifierExtension
N/A
.... purpose
./type
.... name
  • PID-5
  • PID-9
./name
.... telecom
  • PID-13
  • PID-14
./telecom
.... address
PID-11
./addr
... endpoint
n/a

doco Documentation for this format