v0.1.0 Mar 2026 Done
Initial trial-use draft
Initial foundation for profiles, extensions, code systems and example resources.
Roadmap
Product follows law, law shapes product.
VN Core tracks changes in Vietnam's health-data framework. A legal change is incorporated only after its status, scope, technical impact, and release classification have been reviewed; publication dates therefore depend on governance and quality gates.
Product roadmap
v0.2.0 Mar 2026 Done
Internal review
Hardened conformance rules and publication policy ahead of public release.
v0.3.0 Mar 2026 Done
Wave 1 — first public release
First public release covering demographics, BHYT submission, baseline terminology and outpatient workflows.
v0.4.0 Apr 2026 Done
Wave 2 — imaging, pharmacy, devices, departments
Six new profiles plus 2025-2026 legal-basis refresh.
v0.5.3 May 2026 Done
QĐ 697/QĐ-BYT readiness + structured legal reference + CHC contributions
The 0.5 line stabilized QĐ 697/QĐ-BYT readiness, legal registry work, and CHC/commune-health-station core-bound contributions. Scope: 12-group cost itemisation, basic commune-health services, facility-code lifecycle, devices, and future-effective markers; the current public legal registry has 134 source-linked references.
v0.6.1 Jun 2026 Done
Care management + structured health-checkup (KSK SDC) + IPS interoperability
An additive minor release with no canonical URL or package-id change. Focus areas: care management, HL7 SDC structured health-checkup capture, IPS/$summary interoperability, and QĐ 2919/QĐ-BYT; technical detail stays in the changelog/IG.
v0.7.0 Jul 2026 Done
BHYT data hardening + release audit + Jul 2026 legal rollover
Hardening release following the post-publication audit of v0.6.1 (v0.6.1 withdrawn): fixes the BHYT financial-mapping defect cluster and referral-letter signer, correct operation scopes, complete bhyt.submission packaging of the XML13–15 delta, rolls legal statuses over the 01 Jul 2026 milestone with a 145-document registry (adding 8 documents from the 01 Jul 2026 effective wave), and declares 3 outstanding breaking changes per SemVer with migration guidance. The former 0.7.0 interoperability-depth/telehealth scope moves to the v0.8.0 cycle.
v0.8.0 Jul 2026 Done
Health-checkup data restructuring per Decision 2062/QĐ-BYT + post-audit hardening
Minor release with breaking changes: periodic health-checkup data restructured per Decision 2062/QĐ-BYT (age-group forms, expanded subject codes, new exchange envelopes) plus a quality-hardening pass after two independent audits — legal citations aligned to the enacted texts, terminology era-splits with migration maps, and a durable naming policy (ADR-0017). v0.7.0 is frozen as published; the legal corpus reaches 172 documents. See the changelog for details.
v0.9.0 Q3 2026 Current
Itemized health-insurance billing, quarterly settlement, and artifact-semantics hardening
Breaking minor release focused on the health-insurance payment track: multi-stage itemized cost statements per Decision 697/QD-BYT and quarterly settlement minutes (Form 06/BH) per Circular 12/2026/TT-BTC. 100% of artifacts (618/618) now carry machine-readable legal bases with a regression-blocking gate; the legal registry reaches 209 documents. Completes all 15/15 BHYT XML StructureMaps, full ePrescription (chemical and traditional medicine), telehealth scheduling, and BALP emergency-access audit logging. Breaking: the vn-ext-encounter-code extension is removed; v0.8.0 is frozen as-is.
v1.0.0 Target Q3 2027 Planned
STU1 — Stable release, formal-governance readiness
Stabilization target after publicly disclosed or review-eligible implementation reports, conformance testing for the agreed scope, and priority KCB output XML ↔ FHIR ConceptMaps validated by scope. Affiliate filing material is prepared only if governance conditions are met. It also opens four externally-gated items, each with an explicit activation condition: Subscription (once at least one provider or payer states a concrete event requirement), the VNMedicationCodeVS drug code system and the full drug-identity model (once the pharmacy-database sandbox grants access to the drug_id catalogue), the EMR HUB electronic-record exchange specification (once the National Health Information Centre publishes an official API), and tested Bulk Data deployment (once a pilot server is available).2.
Legal milestones
07/2024 TT 17/2024/TT-BCA
Citizen ID (CCCD) and personal identifier validation rules.
10/2024 TT 23/2024/TT-BYT
New medical service catalogue replacing TT 43/2013/TT-BYT.
12/2024 QĐ 4152/QĐ-BYT
Ministry of Health digital architecture v3.0 — emphasises shared data.
06/2025 QĐ 2010/QĐ-BYT
54 shared department/clinic codes — basis for VNCoreOrganizationDepartment.
07/2025 NQ 202/2025/QH15 + TT 13/2025/TT-BYT + NĐ 163/2025/NĐ-CP
34-province administrative model; EMR requirements and transition dates; new pharmaceutical-law decree.
07-08/2025 QĐ 2427/QĐ-BYT + QĐ 2493/QĐ-BYT
Vietnam SNOMED CT batches 1 (Body Structure) and 2 (Morphologic Abnormality).
11/2025 QĐ 3516/QĐ-BYT
Digital transformation strategy emphasising data, citizen ID, and EMR/HSSK.
01/2026 Luật 91/2025/QH15 + NĐ 356/2025/NĐ-CP
Health data falls within sensitive personal data; controls depend on role, purpose, and legal basis.
03/2026 QĐ 697/QĐ-BYT + QĐ 586/QĐ-BYT
New invoice template (12 cost groups; legal effect 19/03/2026, software rollout by 01/07/2026) and national EMR plan 2026.
Release rules
Predictable cadence beats heroic dumps. Four rules govern every version bump.
Major (x.0.0)
Breaking change to a profile, terminology, or canonical contract. Release follows impact analysis, community review, migration guidance, and acceptance of a release candidate.
Minor (x.y.0)
Backward-compatible additions or reviewed scope expansion. No fixed cadence is promised before quality and governance gates are met.
Patch (x.y.z)
Corrections that preserve compatibility. Conformance changes are classified by impact rather than by file type.
Legal update
A new legal instrument is assessed for effect, scope, and IG impact. The version class follows compatibility impact; a legal change is not automatically a patch.
v1.0.0 readiness and governance
Version 1.0.0 is a maturity target, not a commitment to Affiliate status. It should follow published or review-eligible implementation evidence, conformance testing for the agreed scope, and stable governance. An HL7 Affiliate application may be considered separately if the governance and stakeholder requirements are met.