Why Vietnam's healthcare needs data standardization

1. The interoperability problem in five real stories

Mrs. Lan's story in the opening is not unique. Every day, millions of clinical encounters across Vietnam run into invisible walls between information systems. The five scenarios below come from different settings but reveal the same problem: health data is trapped inside isolated systems.

Story 1 — Mrs. Lan's journey across three hospitals

Mrs. Lan passed through three healthcare facilities: a central-tier hospital that detected the disease, a specialized cancer hospital that delivered treatment, and a provincial hospital that handled follow-up. Each facility issued its own paper file along with a CD containing DICOM images. The downstream physicians had no time to re-read thirty pages of handwritten notes from the previous hospital, so they questioned her from scratch. Several routine blood tests were re-ordered because the original results were more than two weeks old and could not be retrieved quickly. The patient lost time and money — and worse, ran the risk of being treated on incomplete information.

Story 2 — A midnight emergency

A male patient was rushed unconscious into the Emergency Department at Cho Ray Hospital after a traffic accident. The on-call physician had no way to know whether this person had ever experienced a beta-lactam antibiotic allergy at another hospital two years earlier. The team had to fall back on the safest protocol option, which is not always the optimal one. A signed electronic patient summary retrievable through VNeID in thirty seconds could have completely changed the clinical decision at that moment.

Story 3 — BHYT reconciliation

The same total cholesterol test can be coded under different names at two different hospitals, because each one maintains its own internal procedure catalog. When the social insurance agency reconciles invoices via XML 4210, differences in spelling, ordering, or internal pricing all create discrepancies. Manual reconciliation remains the norm. When every encounter is packaged as a digitally signed FHIR Bundle with standard terminology codes (LOINC for tests, ICD-10 for diagnoses), the insurer can verify claims automatically at scale.

Story 4 — The COVID-19 pandemic and its data lessons

During 2021, the health sector needed near real-time aggregation of case counts, close-contact records, and vaccine doses from more than 1,500 healthcare facilities. In practice, most of this data moved through Excel files over email and Zalo, and was then keyed by hand into the central system. Several indicators arrived in reports days after the underlying outbreak had moved on. If hospitals had had an interoperability standard in place, lighting up a FHIR $export endpoint to push epidemiological reports to the central system would have been a configuration change, not a project.

Story 5 — A healthcare AI startup in Hanoi

A Vietnamese startup wanted to train an AI model to screen for cardiovascular risk based on electrocardiograms. They reached out to five hospitals and discovered that each one exported ECG files in a different vendor-specific format. The team had to write five separate converters, sign five separate data-sharing agreements, and spent close to a year just assembling a pilot dataset. Meanwhile, US-based startups can access multi-center datasets through the FHIR Bulk Data standard right after signing a single framework agreement. This gap is not a technology problem — it is a standardization problem.

2. Five reasons Vietnam needs interoperable health data

The five stories above translate into five concrete, measurable benefit categories. This is the argument framework you can take into hospital board meetings, regulator consultations, or investment committee reviews.

2.1. Patient quality and safety

When the receiving physician has access to a patient summary — current diagnoses, the active medication list, recorded allergies, the latest test results — clinical decision quality rises substantially. Systems can automatically flag drug interactions, check dosages against renal function, or surface recent tests to avoid duplicate orders. The Organisation for Economic Co-operation and Development (OECD) has documented a meaningful share of laboratory tests rated as low-value or inappropriate; data interoperability is a prerequisite to addressing that pattern.

2.2. Hospital operational efficiency

A typical hospital simultaneously runs HIS, LIS, RIS, a pharmacy system, a billing system, and several specialty modules. When every system pair needs its own integration, the number of connections grows multiplicatively. Adopting FHIR as a shared data backbone turns an N-by-M point-to-point problem into a hub-and-spoke model, lowering long-term maintenance costs and shortening time-to-integrate for new modules. Vendor lock-in also weakens because every supplier must speak the same language.

2.3. Transparency and faster BHYT settlement

When each encounter is packaged as a digitally signed FHIR Bundle under Decree 137/2024/NĐ-CP, Vietnam Social Security (BHXH) can verify automatically: who was seen, what was done, where, whether it falls within social health insurance (BHYT) entitlements, and whether it exceeds the 45-month-base-salary payment cap set by Decree 188/2025/NĐ-CP. The audit process shifts from random sampling to total verification at near-zero marginal cost. Hospitals get paid faster; the BHYT fund loses less to leakage.

2.4. Public health and real-time epidemiology

The Disease Prevention Law (Law 114/2025/QH15, effective July 1, 2026) raises the bar for immunization management, communicable disease surveillance, and rapid reporting of public health events. When data is standardized at the source, preventive medicine agencies can query nationwide epidemiological indicators in minutes rather than days. Sustainable Development Goal (SDG) reporting to the World Health Organization can also be automated rather than manually compiled.

2.5. Innovation: AI, research, and startups

Healthcare AI is only as good as its training data is large, diverse, and clean. FHIR-based standardization opens up the ability to export de-identified datasets through processes that comply with the Personal Data Protection Law (Law 91/2025/QH15). Multi-center clinical research can join data from many hospitals without building a separate ETL pipeline for each one. Vietnamese health startups get a real sandbox in which to build products — a precondition for the local HealthTech ecosystem to compete regionally.

3. The legal framework driving standardization

Before 2025, health data standardization in Vietnam was largely encouraged. From mid-2025 through 2026, a wave of legal documents has turned it into a binding obligation tied to specific deadlines. The four documents below have the most direct impact on health system design at hospitals and regulators.

Beyond these four documents, Decision 1332/QĐ-BYT lays the groundwork for the Electronic Health Record (Sổ SKĐT) inside VNeID — the channel that puts data directly in the patient's hands. The full legal corpus is maintained in the VNLegalDocumentRefCS CodeSystem within the VN Core IG and published at khung pháp lý.

4. Why HL7 FHIR rather than building from scratch

A fair question: if Vietnam already uses XML 4210 for BHXH data, why not just extend that format to cover every interoperability need? The answer comes down to scope and community. XML 4210 was designed for a narrow purpose — sending billing data to social insurance — and its structure does not cover the diverse clinical workflows of a modern health system: patient summaries, care coordination, e-prescriptions, or real-time epidemiological reporting.

HL7 FHIR R4 (version 4.0.1) provides 146 Resources covering nearly every concept in modern healthcare, most of them Normative (locked, no breaking changes). Five decisive strengths:

• A global ecosystem: More than 50 countries already publish a national Implementation Guide (US Core, AU Core, JP Core, KR Core, CH Core, and others). Vietnam does not have to walk alone.
• Open source and free: The specification is published under CC-BY-4.0; reference servers HAPI FHIR (Java) and Firely (.NET) are both open source.
• Modern web APIs: REST, JSON, and OAuth 2.0 — the same vocabulary used by every web and mobile application, which makes VNeID integration straightforward.
• No vendor lock-in: Hospitals can change vendors without losing data, as long as every vendor exposes FHIR.
• An active Vietnamese community: A draft VN Core IG is being finalized at the canonical URL http://fhir.hl7.org.vn/core/, led by the Department of Information Technology under the Ministry of Health together with the community (including OmiGroup).

The alternatives have been considered and ruled out. Rolling a new standard from scratch would take 5-10 years just to reach minimum maturity, while isolating Vietnam from the international standards mainstream. HL7 v3 and openEHR have strong academic foundations but steep learning curves and limited support among Vietnamese vendors. Pure XML 4210 lacks coverage. FHIR is the balanced choice across technical maturity, adoption, and cost of implementation.

5. Four common hospital objections, addressed

In advisory sessions with hospital boards, OmiGroup hears the same four objections used to delay or deny investment in health data interoperability. Each one contains a kernel of truth, and each one collapses when measured against the reality of implementation and the 2026 legal deadlines.

"Our hospital already has an EMR — what more do we need?"

The EMR (electronic medical record) and interoperability are two different layers. An EMR is clinical data stored electronically inside one healthcare facility; interoperability is the ability for that data to move safely outside, to another tier of care, to the insurer, or to the patient. Circular 13/2025/TT-BYT requires both: medical records must be electronic and connected to the personal identifier and VNeID. FHIR is the implementation layer the VN Core IG proposes for that connectivity requirement.

"FHIR investment is too expensive — small hospitals can't afford it"

The minimum cost is much lower than perceived. An open-source HAPI FHIR server can run on a mid-tier VPS for a few million VND a month. The minimum staffing for an initial sandbox is one engineer who knows Java or .NET — not a ten-person team. Commercial vendors (Microsoft Azure FHIR, Google Cloud Healthcare API) are an acceleration option, not a requirement. The truly expensive scenario is the hospital that waits until the final month before the December 31, 2026 deadline and then hires under emergency conditions.

"Let's wait for the Ministry of Health to publish a complete national standard"

The Ministry of Health is leading work on the national standard, and the community draft of the VN Core IG is already available as reference material. Even so, there is plenty hospitals can do in parallel without waiting: clean up drug catalogs, procedure catalogs, and diagnosis lists against the Vietnamese ICD-10 (Decision 4469/QĐ-BYT); separate demographic data from clinical data in preparation for the Resource model; pilot exporting Patient and Encounter to FHIR in a sandbox environment. Once the national standard is officially adopted, prepared hospitals will align in weeks rather than quarters.

"Doctors don't care about coding standards"

Correct — and they shouldn't have to. A cardiologist does not need to know which SNOMED CT code maps to "essential hypertension"; the cardiologist needs an EMR interface that displays the right Vietnamese term and lets them pick it quickly. Terminology standardization is a layer below the user — the job of the EMR vendor and the data integration team. The doctor's experience stays in Vietnamese, with fast keyboard input and smart suggestions; behind the scenes, the system records the standard code so the rest of the health sector can interoperate with it.

6. A 24-month roadmap for hospitals

The roadmap below draws on OmiGroup's advisory experience with hospitals in Vietnam and Japan, calibrated against the December 31, 2026 deadlines in Circular 13/2025 and Decree 278/2025. Each phase has a clear goal, deliverables, and acceptance criteria.

A more detailed roadmap for the CIO role, including a KPI checklist and common risks, is available at For hospital CIOs.

7. Continue reading