Implementation
Three concrete paths to put VN Core into practice.
Hospitals, vendors and public-sector teams start from different places. This page mirrors the Vietnamese implementation playbook: legal deadlines, suggested phases, common mistakes and links into the technical IG.
Playbook · Hospitals / care providers
Meet EMR and BHYT interoperability requirements without replacing everything at once.
VN Core helps providers standardize demographics, encounters, diagnoses, lab/imaging, medication, EMR documents and BHYT payment data on FHIR R4. It runs alongside the XML 4210/QĐ 3176 exchange already used today.
Main steps
-
Month 1
Survey and map source systems
Inventory HIS, EMR, LIS and PACS data. Map local fields to Patient, Encounter, Condition, Observation, Coverage and Claim.
Output: HIS-to-FHIR mapping table and a prioritized data-gap list
-
Months 2-3
Pilot identity and encounters
Stand up an internal FHIR endpoint and push Patient/Encounter from HIS. Use CCCD as the primary identifier; include BHXH/BHYT identifiers only in the right context.
Output: Patient + Encounter pilot in one or two departments
-
Months 4-5
Add lab, imaging and medication
Publish DiagnosticReport, Observation and MedicationDispense resources. Align laboratory items with QĐ 1227/QĐ-BYT and clinical content with the Vietnam terminology packages.
Output: Department-level pilot with lab and medication coverage
-
Month 6
Add BHYT payment exchange
Create Coverage, Claim and ExplanationOfBenefit data under QĐ 3176/QĐ-BYT and prepare the 12-cost-group statement under QĐ 697/QĐ-BYT.
Output: Parallel XML 4210 and FHIR Claim/EOB exchange
-
Month 7+
Conformance and rollout
Run validation against the VN Core package, add Consent/AuditEvent/Provenance according to Law 91/2025 and expand to additional care settings.
Common mistakes
- Do not use VNeID as the core patient identifier. CCCD is the core personal identifier; VNeID is an application/account layer.
- Do not switch off XML 4210 prematurely. There is no official replacement yet, so run FHIR in parallel.
- Do not use the old 63-province administrative model for new data. NQ 202/2025 changed the official model to 34 provinces and two tiers.
- Do not treat DPIA, Consent and audit trails as later add-ons. They are core compliance requirements under Law 91/2025 and NĐ 356/2025.
Reference resources
Playbook · HIS / EMR / LIS / middleware vendors
Build one reusable FHIR adapter instead of one-off integrations for every customer.
A vendor can keep its internal schema and expose a VN Core-compatible FHIR layer. That is usually faster and safer than rewriting product databases or creating a vendor-specific profile family.
Main steps
-
Weeks 1-2
Set up the development environment
Run a FHIR server, install SUSHI and the FHIR validator, then load the VN Core package.
Output: Local validation environment with VN Core package installed
-
Weeks 3-4
Implement the compatibility layer
Map native HIS tables into Patient, Encounter, Coverage and Observation. Start read-only if that lowers risk.
Output: Patient + Encounter resources passing VN Core validation
-
Months 2-3
Automate conformance checks
Run the official FHIR validator in CI. Treat errors as release blockers and document accepted warnings.
Output: CI validation against VN Core examples and sample customer data
-
Month 4+
Pilot with real deployments
Run with one or two provider customers, collect edge cases and feed gaps back into the community process.
Common mistakes
- Do not hardcode province/ward lists into product code. Use the VN Core terminology package so legal updates can be absorbed.
- Do not validate only against local schemas. Use the FHIR validator with the VN Core package.
- Do not drop Vietnamese extensions such as ethnicity, BHYT card details and insurance visit type. US Core is not a replacement for VN Core.
- Do not create a parallel vendor-only profile set unless there is a clear extension path back into VN Core.
Reference resources
Playbook · Regulators / MoH / VSS / provincial health departments
Use the community draft as a practical reference model before formal standardization.
VN Core is not an official national standard yet. It can still help public-sector teams evaluate field definitions, registry boundaries, BHYT mapping and EMR interoperability before issuing formal guidance.
Main steps
-
Phase 1
Review and comment
Technical and policy teams review the IG, confirm operational fit and send concrete feedback through the project channels.
-
Phase 2
Coordinate pilots
Select public hospitals and integration partners to test patient identity, EMR documents and Claim/EOB exchange on real workflows.
-
Phase 3
Formalize stable pieces
Move proven slices into official technical guidance while keeping backward compatibility with XML 4210/QĐ 3176 where required.
-
Phase 4
Support the HL7 Vietnam path
When there is enough evidence and governance maturity, transfer stewardship to a formal HL7 Vietnam structure.
Common mistakes
- Do not publish a hard standard before pilots show that the model works in real hospitals.
- Do not bind the ecosystem to a single vendor. VN Core is CC-BY-4.0 and designed for broad implementation.
- Do not ignore international interoperability. VN Core stays on HL7 FHIR R4 and remains comparable with JP Core, KR Core, US Core and other national IGs.
Reference resources
Next step
Need an implementation path for your organization?
Omi HealthTech can share practical FHIR implementation experience from Vietnam, Japan and Korea, then help you choose a pilot scope that is small enough to finish and real enough to validate.