FHIR R4 in Vietnam: Adoption Status and What It Means for You

FHIR (Fast Healthcare Interoperability Resources) is the international standard for healthcare data exchange developed by HL7. FHIR R4 defines a set of data structures (Resources) and APIs for exchanging clinical information — patient records, lab results, prescriptions, imaging, and more — between systems.

For Vietnam, FHIR matters because it is the foundation of the Ministry of Health's national health data exchange roadmap. The National Health Portal and the Health ID programme (Hồ Sơ Sức Khỏe Điện Tử) are designed around FHIR-based APIs. HealthTech companies that build FHIR-native integrations will have a significant advantage as the ecosystem matures.

As of 2026, FHIR adoption in Vietnam is patchy but accelerating. Large private hospital groups — particularly those with international affiliations like Vinmec and FV — have FHIR-capable systems either through their HIS vendors or through direct development. International hospitals that use Epic-compatible modules have FHIR as a first-class feature.

The majority of public hospitals still run on legacy HIS platforms that communicate via HL7 v2 at best, or proprietary formats in many cases. Full FHIR compliance at these institutions is a 3–5 year roadmap item, not a current reality. This means most HealthTech integrations at public hospitals still require HL7 v2 or custom API work.

Circular 46/2018/TT-BYT set early requirements for HIS data standards. Subsequent MoH guidance has moved toward FHIR R4 as the target standard for national data exchange. The National Health Information System (NHIS) uses FHIR-based APIs for data submission by connected facilities.

Any HealthTech product that claims to contribute to or consume national health records will need FHIR compatibility. For products that operate only within a single hospital's walls and do not connect to national systems, HL7 v2 compatibility with the local HIS may be sufficient in the near term.

Build your product with FHIR as the internal data model even if your first hospital integrations use HL7 v2 or proprietary APIs. This architecture means you can add FHIR-native endpoints as hospitals upgrade without rebuilding your core data layer.

For resource mapping, start with the most common resources: Patient, Encounter, Observation, DiagnosticReport, MedicationRequest, and ServiceRequest. These cover the majority of integration needs for diagnostic AI, EMR, and telemedicine products.

Vietnamese hospital IT teams vary widely in their FHIR knowledge. Include clear FHIR-based API documentation in Vietnamese as part of your integration package. The more work you do to reduce the hospital's integration burden, the faster you can deploy.

Test your FHIR implementation against the FHIR R4 validator and Touchstone test suite before approaching hospitals. Showing a test report demonstrates technical credibility to hospital IT teams.

Join the HL7 Vietnam affiliate community. This is a small but active group that tracks regulatory developments and shares implementation experience. It is an efficient way to stay current on MoH policy changes affecting interoperability requirements.