52
Profiles
FHIR profiles for patients, encounters, diagnoses, labs, medication, BHYT coverage, devices and clinical documents.
Omi HealthTech · v0.5.1 · FHIR R4 · CC-BY-4.0
Vietnam's FHIR core, legal-first and implementation-ready.
Omi HealthTech builds and publishes VN Core, an HL7 FHIR R4 Implementation Guide for Vietnamese healthcare. The current draft tracks 101 legal references and covers 52 profiles, 71 CodeSystems, 76 ValueSets, 158 example instances and the XML 4210 mapping layer for BHYT.
Release 0.5.1
What Omi HealthTech has built.
VN Core v0.5.1 combines legal research, healthcare workflow analysis and FHIR engineering. It is published openly under CC-BY-4.0.
71
CodeSystems
ICD-10 VN, CLS laboratory catalogue, Vietnam SNOMED CT batches, traditional medicine and operational catalogues.
Packages
A modular release structure: Core Base, BHYT Submission, clinical terminology, traditional medicine and aggregate Core.
131
Examples
Examples covering outpatient, inpatient, newborn, foreign-patient, BHYT and document workflows.
Designed by implementation group
Built for three practical audiences.
01
For HIS, EMR and HSSK teams
A common foundation for patient and clinical data.
Problem
Vietnamese HIS/EMR systems often model patients, encounters and lab results differently. Integration teams then write one-off mappings for every endpoint.
How VN Core helps
VN Core defines the shared representation for CCCD identity, 2-tier address data, patient demographics, ICD-10 VN diagnoses, lab observations and EMR documents.
02
For BHYT gateway and integration teams
Keep Core FHIR separate from payer-submission logic.
Problem
BHYT payment rules change quickly (QĐ 130 → QĐ 4750 → QĐ 3176 → QĐ 697). If insurance logic is mixed into the shared clinical model, every legal update creates unnecessary breakage.
How VN Core helps
VN Core separates Core Base from the BHYT Submission package, including 13 logical models, 3 business operations and round-trip examples for XML 4210 mapping.
03
For QA, compliance and project leads
Privacy, audit and legal traceability from the start.
Problem
Law 91/2025 treats health data as sensitive personal data, while TT 13/2025 makes EMR interoperability urgent. Adding consent and audit after the fact is expensive.
How VN Core helps
Consent, AuditEvent, Provenance and a legal-by-resource matrix are part of the foundation, so technical and compliance teams can review the same evidence.
Profile spotlight
One clinical visit, three core pieces.
Patient (who), Encounter (what happened), and Coverage (how BHYT applies) form the minimum set for outpatient and inpatient exchange. VN Core keeps Vietnamese extensions explicit while preserving FHIR R4 compatibility.
VNCorePatient
Patient identity
12-digit CCCD as the primary identifier, 54 ethnic groups, Vietnam nationality, 2-tier address model and BHYT card context.
- CCCD identifier: 12 digits, issued by the Ministry of Public Security
- Ethnicity extension bound to the 54-ethnic-group Vietnamese catalogue
- Ward and province extensions for the 2-tier address model
- BHYT card context for coverage and reimbursement workflows
VNCoreCoverage
BHYT coverage
Vietnam health-insurance card structure, benefit levels, initial KCB registration site and five-year-continuous coverage.
- Payor reference to Vietnam Social Security
- Coverage class for BHYT subject group and entitlement context
- Benefit-level extension aligned with NĐ 188/2025/NĐ-CP
- Five-year-continuous flag for co-payment cap handling
VNCoreEncounter
Clinical visit
Outpatient, inpatient and emergency encounters with insurance visit type, diagnosis role, service provider and timing.
- Insurance visit type for initial, referral and emergency workflows
- FHIR ActCode class for ambulatory, inpatient and emergency visits
- Diagnosis role handling for admission and complication diagnoses
- Service-provider reference to VNCoreOrganization
Implementation guidance
Choose the right path, not a linear reading order.
Different teams need different entry points. The technical IG contains the full details; the English getting-started page keeps the implementation playbooks aligned with the Vietnamese version.
The current priority is to keep the identity, EMR, BHYT payment and legal-traceability layers stable before expanding scope. These are the areas where ambiguity creates the highest integration cost.
Hospital and care-provider teams
Start with Patient + Encounter + Coverage, validate against VN Core, then expand to lab, imaging, medication and EMR document exchange.
Read playbookHIS, EMR, LIS and middleware vendors
Wrap existing schemas with a FHIR adapter instead of rewriting internal databases. Keep XML 4210 running while exposing VN Core resources.
Read playbookRegulators and public-sector programs
Use VN Core as a reference model for shared registries, national data exchange and future official guidance once pilot evidence is strong enough.
Read playbookLegal foundation
Vietnamese law directly shapes VN Core.
VN Core is not designed in isolation. Each profile, terminology decision and package boundary is connected to the current Vietnamese regulatory frame.
Last reviewed
2026-05-01
Reading rule
Law and data design move together
31 Dec 2024
Design driverQĐ 4152/QĐ-BYT
MoH digital architecture v3.0 moves sector architecture toward shared data, data warehouses and secure integration.
Impact on VN Core
Positions VN Core as a shared data-standardization layer.
19 Jun 2025
Design driverQĐ 2010/QĐ-BYT
Shared department and clinical-department codes become a foundation for VNCoreOrganizationDepartment and MA_KHOA mapping.
Impact on VN Core
Stabilizes organization and department coding.
01 Jul 2025
Design driverNQ 202/2025
34 provinces and the 2-tier local-government model reshape address and legacy district handling.
Impact on VN Core
Drives province/ward terminology and address extensions.
01 Jul 2025
Design driverNĐ 163/2025/NĐ-CP
New pharmacy-law implementation rules replace the older NĐ 54/2017 frame.
Impact on VN Core
Affects medication, prescription and registration-number modelling.
21 Jul 2025
Design driverTT 13/2025/TT-BYT
Electronic medical records become a central interoperability driver.
Impact on VN Core
Raises Composition, DocumentReference, identity and audit to core concerns.
25 Jul 2025
Design driverQĐ 2427/QĐ-BYT
Vietnam SNOMED CT batch 1 introduces body-structure terminology for imaging and pathology contexts.
Impact on VN Core
Supports bodySite and DiagnosticReport bindings.
15 Aug 2025
Design driverQĐ 2493/QĐ-BYT
Vietnam SNOMED CT batch 2 adds morphologic-abnormality terminology.
Impact on VN Core
Strengthens pathology conclusion terminology.
12 Nov 2025
Design driverQĐ 3516/QĐ-BYT
MoH digital-transformation strategy reinforces data, CCCD identity, EMR/HSSK and governed integration.
Impact on VN Core
Confirms the priority order for identity and record exchange.
01 Jan 2026
Design driverLaw 91/2025 + NĐ 356/2025
Health data is treated as sensitive personal data, making privacy-by-design mandatory.
Impact on VN Core
Makes Consent, AuditEvent, Provenance and data-minimization core.
19 Mar 2026
Design driverQĐ 697/QĐ-BYT
The new medical-cost statement changes 12 cost groups and BHYT payment reporting.
Impact on VN Core
Shapes Claim/EOB and the BHYT Submission package.
09 Mar 2026
Design driverQĐ 586/QĐ-BYT
The national 2026 EMR plan sets concrete deadlines for care providers.
Impact on VN Core
Keeps EMR document exchange and patient identity in scope.
Community draft
VN Core needs real pilots to become stable infrastructure.
The current draft is ready for review and pilot feedback. Hospitals, vendors, terminology specialists, privacy/compliance reviewers and public-sector teams can all help move it from a strong draft to a shared national asset.