Hospital CIO
For deciding roadmap, risk, and how FHIR fits existing HIS/EMR estates.
Open playbook
Recommended reads
HL7 / FHIR Knowledge · Vietnam
A reading map from HL7 concepts to VN Core implementation
This knowledge hub is more than a beginner glossary. Each article places HL7, FHIR, and VN Core in real Vietnam healthcare problems: electronic medical records, BHYT, VNeID, personal data protection, clinical terminology, and interoperability governance.
Editorial principle
Standardize before accelerating: define terms clearly, cross-check legal context, connect prose to VN Core artifacts, and only make claims that have evidence. This is how Omi brings implementation knowledge from rigorous health systems back to Vietnam's data infrastructure.
HL7 FHIR R4VN Core IGBHYTEMRSensitive data
38
knowledge pages
Vietnamese and English in parallel
134
legal references
cross-checked in the registry
73
FHIR profiles
VN Core v0.6.0
139
CodeSystems
terminology and shared code systems
Six-layer implementation model
Read the hub as a path from policy to running data exchange.
A FHIR implementation team should not begin by copying sample JSON. The right order is: define the legal scope, understand the workflow, choose resources, apply profiles, bind terminology, then package and validate. The Knowledge Hub is organized around that path.
01
Policy and scope
Identify governing instruments, sensitive data, sharing responsibility, and the trial-use boundary before modeling data.
02
Workflow and events
Break the problem into EMR, BHYT, VNeID, referral, prescription, or immunization flows instead of designing resources around HIS screens.
03
Base resources
Choose the right Patient, Encounter, Observation, DiagnosticReport, MedicationRequest, Coverage, Claim, Bundle, and provenance relationships.
04
Profiles and extensions
Apply Vietnam constraints through Must Support, slicing, extensions, cardinality, and invariants; read them together with real examples.
05
Terminology and identifiers
Govern CodeSystems, ValueSets, NamingSystems, ConceptMaps, CCCD/BHYT/provider identifiers, and Coding.display behavior.
06
Bundles, validation, operations
Package exchange records, run validators, test through sandboxes/connectathons, and feed issues into a Working Group process.
Overview before the IG
Read VN Core as a system, not as isolated profiles.
The IG is the normative source for validation. This track is the orientation layer: it helps readers know which artifacts shape data, which artifacts govern codes, which artifacts define APIs, and how to test before implementation.
01
Artifact map
See how 73 profiles, 139 CodeSystems, 144 ValueSets, examples, capabilities, and operations fit together before opening the artifact index.
02
How to read a Profile
Read differential, snapshot, Must Support, slicing, bindings, extensions, and examples to locate Vietnam-specific constraints.
03
Terminology
Distinguish CodeSystems, ValueSets, ConceptMaps, NamingSystems, and Coding.display behavior in real data exchange.
04
Bundles and validation
Assemble resources into exchange records, claims, IPS documents, examples, and validator checks before go-live.
Read by job-to-be-done
Not every reader should start on the same page.
Pick a role-based path to move from practical questions to the right foundation, instead of reading the full library sequentially.
Developer
For endpoints, payloads, validation, and common implementation errors.
Open playbook
Recommended reads
Clinician and operations
For understanding how EMR, orders, results, and lifecycle care speak the same data language.
Open playbook
Recommended reads
Regulator
For governance, legal basis, sensitive data, and national interoperability capability.
Open playbook
Recommended reads
Vietnam context
The strongest content is where FHIR meets Vietnam's reality.
These articles connect international standards with legal requirements, hospital workflows, BHYT data, and personal data protection. They prevent teams from treating FHIR as just another generic API.
Electronic medical records
Reading Circular 13/2025 from a data perspective: identifiers, clinical documents, connectivity, and audit trails.
BHYT output data
Keep regulatory XML output while structuring internal data as Coverage, Claim, EOB, and Invoice.
VNeID and personal health records
FHIR as a model for personal health records, without confusing VNeID with the patient identifier itself.
Personal data protection
Distinguishing basic personal data, sensitive health data, consent, logging, and sharing responsibility.
Medical AI
FHIR data with provenance is a prerequisite for explainable, risk-controlled medical AI.
Full library
Eight content clusters from beginner topics to end-to-end use cases.
Conceptual foundation
Introduction
P0 · 6 pages
HL7, FHIR, history, comparisons, and the healthcare data standards map. Start here if you need a solid foundation before reading an IG.
What is HL7?
/en/knowledge/what-is-hl7/
What is FHIR?
/en/knowledge/what-is-fhir/
History of HL7
/en/knowledge/hl7-history/
HL7 v2 vs v3 vs CDA vs FHIR
/en/knowledge/hl7-v2-v3-cda-fhir-comparison/
Healthcare data standards map
/en/knowledge/healthcare-data-standards-map/
Why does Vietnam need standardization?
/en/knowledge/why-vietnam-needs-data-standardization/
From specification to implementation
FHIR Core Concepts
P0 · 5 pages
Resources, REST APIs, Profiles, Extensions, Terminology, and versioning — the concepts required to implement FHIR correctly.
FHIR Resources — the core data model
/en/knowledge/fhir-resources/
FHIR RESTful API
/en/knowledge/fhir-restful-api/
Profiling, Extensions, Implementation Guide
/en/knowledge/profiling-implementation-guide/
Terminology Binding (CodeSystem, ValueSet)
/en/knowledge/terminology-binding/
FHIR Versions: DSTU1 → R5
/en/knowledge/fhir-versions/
Read VN Core before implementation
VN Core Deep Dive
P0 · 4 pages
A reading map before entering the IG: which artifacts are normative, how to read profiles, how terminology is bound, and where bundles/validation fit.
Localized with evidence
Vietnam Context
P0 · 5 pages
FHIR in Vietnam-specific problems: electronic medical records, BHYT, VNeID, personal data protection, and medical AI.
FHIR in Electronic Medical Records (Circular 13/2025)
/en/knowledge/fhir-emr-vietnam/
FHIR and BHYT (XML 4210, Decisions 130/4750/3176)
/en/knowledge/fhir-bhyt/
FHIR and VNeID (Personal Health Record)
/en/knowledge/fhir-vneid/
FHIR and Law 91/2025 on Personal Data Protection
/en/knowledge/fhir-data-protection-law/
FHIR and AI Law 134/2025
/en/knowledge/fhir-ai-law/
Role-based reading paths
By Persona
P1 · 4 pages
Same foundation, different questions: CIOs need a roadmap, developers need APIs, clinicians need clinical meaning, regulators need governance.
Quick reference
Reference
P1 · 4 pages
EN-VI glossary, FAQ (50 entries), international FHIR map, VN timeline.
From workflow to resources
End-to-end Use Cases
P2 · 4 pages
Province-commune interoperability, electronic referral, e-prescription, expanded immunization.
Province ⇄ Commune interoperability
/en/knowledge/use-case/use-case-province-commune-interop/
Electronic referral
/en/knowledge/use-case/use-case-electronic-referral/
E-prescription
/en/knowledge/use-case/use-case-eprescription/
Expanded Immunization Program
/en/knowledge/use-case/use-case-immunization/
Editorial methodology
Written like implementation guidance, not promotional copy.
Each article should help technical, clinical, and regulatory teams make better decisions: define terms, understand legal boundaries, and find which VN Core artifacts are affected.
1. Legal cross-check
Every legal citation is cross-checked against 130 legal references in the Vietnam healthcare legal framework — ensuring document numbers, issuance dates, effective dates, and superseded status are accurate.
2. Tied to real artifacts
Articles do not stop at concepts. They connect to VN Core profiles, CodeSystems, ValueSets, packages, and implementation guidance so readers know where to implement.
3. Multi-round verification
Each page is reviewed across multiple passes: fact-checking, language polish, narrative flow, SEO, and automated validation that legal IDs match the FHIR spec and VN Core IG CodeSystem.