HL7/FHIR Glossary — bilingual EN-VI reference

A national member organization of HL7 International, authorized to sub-publish Implementation Guides, run ballots, and represent the health standards community in its country. Each Affiliate operates with financial independence while complying with HL7 International copyright policy and ballot procedures. (Tổ chức quốc gia thành viên HL7)

Vietnam context: Omi HealthTech is preparing the technical foundation and Working Group mechanism for the HL7 Affiliate Vietnam path. If an Affiliate is established, the VN Core IG stewardship role will need to be confirmed through formal governance.

A core concept in openEHR. An Archetype models a single clinical concept (such as Blood Pressure or Body Temperature) at maximum scope, independent of any particular use case. In real-world deployments, Archetypes are composed into Templates that match specific data entry forms. (Mẫu cấu trúc lâm sàng — openEHR)

Vietnam context: The Archetype `openEHR-EHR-OBSERVATION.blood_pressure.v2` is widely used in open EHR systems. Vietnam can reference this Archetype when mapping to FHIR Observation.

An IHE Profile for audit trails and node authentication in the applicable actors and transactions. ATNA, transport, and mutual-authentication requirements must be read from the selected profile, actor, option, and version; they are not identical duties for every node.

Vietnam context: For an IHE-based HIE, build an actor/transaction matrix and apply ATNA where the selected profile requires it. ATNA supports technical controls but does not itself prove compliance with Law 91/2025.

A FHIR Resource that records security and privacy events worth auditing — such as logins, record access, data modifications, and exports. AuditEvent is commonly used to build audit logs for legal compliance, but it does not automatically capture every access; the scope is determined by the system and the Implementation Guide. (Sự kiện kiểm toán)

Vietnam context: To support accountability under Law 91/2025/QH15 and Decree 356/2025/NĐ-CP, a deployment should define auditable events from its legal analysis, threat model, and access policy, then test the corresponding AuditEvent records.

Vietnam's national social health insurance scheme (Bảo hiểm Y tế), administered by Vietnam Social Security (BHXH). VN Core v0.9.0 supports two card-number formats: the current 10-digit number (the same numeric value as the BHXH identifier) and the legacy 15-character form of 2 letters plus 13 digits. A 12-digit CCCD is a separate identifier and must not be recorded under `sid/bhyt`. (Bảo hiểm Y tế)

Vietnam context: The VN Core IG maps the BHYT card to FHIR Coverage; the identifier uses the URI `http://fhir.hl7.org.vn/core/sid/bhyt`. BHYT payment rules are governed by Decree 188/2025/NĐ-CP.

The level at which a ValueSet is enforced for an element. FHIR R4 defines four levels: required (must use a code from the ValueSet), extensible (use a code from the ValueSet if a suitable concept exists), preferred (recommended but not required), and example (illustrative only). (Cường độ ràng buộc)

Vietnam context: In VN Core Patient, the `gender` element has binding strength = required against the AdministrativeGender ValueSet, while `maritalStatus` is typically extensible to allow local codes.

A FHIR Resource that packages multiple Resources into a single container. FHIR R4 defines nine values for `Bundle.type` (required binding): document, message, transaction, transaction-response, batch, batch-response, history, searchset, and collection. Each type carries its own server-side processing rules. (Gói tài nguyên)

Vietnam context: When a FHIR server returns search results for `GET /Patient?name=Nguyen`, the response is a Bundle with `type=searchset`. When sending a complete medical record (Composition plus several Resources), use `type=document`.

A unique, immutable identifier URL for a FHIR artifact (Profile, Extension, ValueSet, CodeSystem). A Canonical URL differs from a file access URL: it is a logical identifier that may not always resolve, but it must remain stable across versions. (URL chuẩn — canonical)

Vietnam context: VN Core Patient has the canonical URL `http://fhir.hl7.org.vn/core/StructureDefinition/vn-core-patient`. An instance may list this URL in `Patient.meta.profile` to claim conformance; the claim still requires validation and is not the sole condition for actual profile conformance.

A FHIR Resource that describes the Resources and Operations a FHIR server or client supports. Servers must expose their CapabilityStatement at the `GET [base]/metadata` endpoint. Clients use it to discover server capabilities before calling the API. (Tuyên bố năng lực server)

Vietnam context: When integrating with a hospital HIS over FHIR, vendors typically begin with `GET https://fhir.bv.vn/metadata` to discover which Resources (Patient, Encounter) and search parameters the server supports.

The minimum and maximum number of times an element may appear in an instance. The notation min..max produces patterns such as `0..1` (optional, single), `1..1` (required, single), `0..*` (optional, repeating), and `1..*` (required, repeating). A Profile may tighten the cardinality of a base Resource but never relax it. (Số lượng — min..max)

Vietnam context: Patient.identifier has a base cardinality of `0..*`; VNCorePatient tightens it to `1..*` and requires the CCCD slice at `1..1`. When no CCCD value is available, the slice remains present with `data-absent-reason` and a valid alternative basis under the profile invariant.

The 12-digit national personal identifier issued by the Ministry of Public Security and printed on the Vietnamese citizen ID card (Căn cước công dân or Căn cước). Effective from July 1, 2025, the CCCD is the primary identifier for Vietnamese citizens, gradually replacing the older 9-digit CMND and the personal tax code as part of the VNeID integration roadmap. (Căn cước công dân)

Vietnam context: In VN Core Patient, the CCCD is a Must Support identifier with the system URI `http://fhir.hl7.org.vn/core/sid/cccd`. Article 1(3) of Circular 13/2025/TT-BYT requires EMR information to be linked to the personal identification number of Vietnamese citizens and of foreign nationals who have been issued an electronic identification account; it does not make a VNeID account an alternative patient identifier.

The HL7 v3 standard for structured XML clinical documents. CDA consists of a header (identifiers, authors, creation date) and a body (clinical content). CDA Release 2 remains widely used for discharge summaries, prescriptions, and lab reports. (Clinical Document Architecture)

Vietnam context: Japan's SS-MIX2 standardized storage is based mainly on HL7 v2 messages and can manage documents in the appropriate content layer; SS-MIX2 should not be equated with CDA. Vietnam should select CDA or a FHIR document from the contract and use case.

An HL7 standard that lets EMRs invoke Clinical Decision Support (CDS) services at defined hooks within the clinical workflow — such as opening a patient chart, prescribing medication, or ordering a procedure. The CDS service responds with Cards containing alerts, suggestions, or links to SMART apps. (Móc gọi CDS thời gian thực)

Vietnam context: A CDS Hook fired when a clinician prescribes an antibiotic can return a Card warning of allergies based on the patient's AllergyIntolerance, supporting compliance with Law 134/2025/QH15 on AI with human oversight.

A FHIR data type that wraps multiple `Coding` instances (each a system + code pair) and an optional free-text `text` field. It allows a single concept to be encoded in multiple terminologies simultaneously — for example, both SNOMED CT and ICD-10 VN. (Khái niệm có mã)

Vietnam context: The diagnosis "essential hypertension" can be represented as a CodeableConcept with two Codings: ICD-10 VN `I10` and SNOMED CT `38341003`, plus Vietnamese text for human readers.

A FHIR Resource that describes a code system and how its content is published. A CodeSystem has a canonical URL and may have a version; `content` states whether the artifact carries all concepts, a fragment, a supplement, or no concepts. It is the foundation for ValueSets and Codings. (Hệ mã)

Vietnam context: `vn-ethnicity-cs` packages concepts in the IG; by contrast, `vn-icd10-cs` is a metadata wrapper with `content = not-present`, so the complete 15,026-code Vietnamese ICD-10 dataset is distributed through a separate download surface.

The most basic FHIR data type for encoding a concept: it includes `system` (the canonical URL of the CodeSystem), `code` (the code value), `display` (a human-readable label), and optional `version` and `userSelected` fields. A CodeableConcept contains one or more Codings. (Cặp mã)

Vietnam context: Under current VN Core guidance, an ICD-10 coding uses `system = http://hl7.org/fhir/sid/icd-10`; the `vn-icd10-cs` artifact in the IG is a metadata wrapper, not packaged code content for a validator to resolve automatically.

A FHIR Resource that organizes the content and attestation context of a clinical document. Its role is comparable to, but not identical with, a CDA header. In a document Bundle, Composition is the first entry and its sections may reference other Resources in the package. (Hợp phần / Header bệnh án)

Vietnam context: A record exchange can use a document Bundle with Composition as its first entry. Composition records type, date, author, and attester; a cryptographic signature, where required, follows the applicable signature policy and a mechanism such as Bundle.signature or Provenance.signature.

A FHIR Resource that declares relationships between concepts in code systems or value sets. R4 equivalence values include relatedto, equivalent, equal, wider, subsumes, narrower, specializes, inexact, unmatched, and disjoint; direction must be explicit. (Bản đồ ánh xạ mã)

Vietnam context: VN Core can publish a ConceptMap between BHYT cost-group codes and adjudication codes. A complete XML-to-Claim/EOB transformation requires a structural mapping specification or adapter, not a ConceptMap.

A testing event hosted by HL7, IHE, or an implementation community where multiple systems run published conformance/interoperability scenarios. Results are evidence only for the tested actor, option, version, and test case; they do not by themselves prove that an entire IG or product is production-ready. (Sự kiện kiểm thử liên thông đa vendor)

Vietnam context: Omi HealthTech's direction is to prepare a Vietnam FHIR connectathon or testing sandbox once the Working Group and implementation partners have enough scenarios, sample data, and a public results process.

A FHIR Resource that represents a patient's choices or commitments regarding how their data is processed and shared. Consent models privacy obligations, but its use is not automatically required by Vietnamese law — that decision is left to each Implementation Guide. (Tài nguyên đồng ý)

Vietnam context: When modeling consent obligations under Law 91/2025/QH15 and Decree 356/2025/NĐ-CP, systems can use Consent to record the timing, scope, and purpose of data processing.

The international standard for medical imaging and related data, governed by NEMA. DICOM defines the file format (.dcm), the transport protocol (DIMSE over TCP), the data dictionary, and the information model for many modalities (CT, MRI, X-ray, ultrasound). (Digital Imaging and Communications in Medicine)

Vietnam context: Many PACS/RIS products support DICOM, but implementers must inspect the exact product/version DICOM Conformance Statement. VN Core can reference a study through FHIR ImagingStudy.

The HTTP/REST successor to traditional DIMSE services, comprising WADO-RS (image retrieval), QIDO-RS (metadata queries), STOW-RS (image submission), and UPS-RS (workflow). It enables DICOM integration into modern web and cloud architectures. (DICOM phiên bản RESTful)

Vietnam context: A browser-based viewer can call `GET /studies?PatientID={cccd}` (QIDO-RS) to list a patient's studies and then use WADO-RS to load DICOM frames.

A personal-data processing impact assessment documents a processing activity and its risks. Law 91/2025 and Decree 356/2025 assign duties by processing role, with a Form 10 report and applicable conditions or exemptions; a separate dossier is not assumed for every API.

Vietnam context: When adding a FHIR server or VNeID integration, compare the new processing with the existing dossier and update or create the required record for the actual role, scope, and legal conditions.

Data Protection Officer is a common label for a personal-data-protection function or individual. The staffing obligation applies generally under Law 91/2025/QH15 Article 33(2); the narrow Article 38(2)-(3) carve-outs do not cover organizations that directly process sensitive data, such as healthcare providers. Personnel conditions follow Decree 356/2025/NĐ-CP Articles 13-16.

Vietnam context: There is no universal threshold based only on hospital class, and the DPO does not automatically sign every DPIA. Determine accountability and the point of contact for the actual processing activity.

A legacy HL7 ballot status applied to standards that have passed community trial but are not yet Normative. Since 2017, HL7 has renamed it to STU (Standard for Trial Use). FHIR DSTU1 launched on September 30, 2014, DSTU2 in 2015, followed by STU3 (2017), R4 (2019), and R5 (2023). (Draft Standard for Trial Use)

Vietnam context: In older documentation, "FHIR DSTU2" is equivalent to "FHIR STU2"; both refer to the March 2015 release that has since been superseded by R4.

The medical technical services catalogue (Dịch vụ kỹ thuật y tế) issued by the Ministry of Health, currently governed by Circular 23/2024/TT-BYT (effective October 18, 2024, replacing Circulars 43/2013 and 21/2017). Each DVKT entry has a code, name, unit price, and specialty classification. (Dịch vụ kỹ thuật y tế)

Vietnam context: In VN Core's FHIR Claim, `Claim.item.productOrService` maps to DVKT codes; for example, "general abdominal ultrasound" has a specific DVKT code in Circular 23/2024.

The query language of SNOMED CT, used to express concept constraints based on hierarchy and attributes. ECL is the standard mechanism for defining intensional ValueSets (subsets) in FHIR. (Expression Constraint Language)

Vietnam context: The expression `<< 73211009 |Diabetes mellitus|` selects every concept that is a kind of "Diabetes mellitus" — used as a filter in the ValueSet `vn-diabetes-vs`.

Electronic Health Record — a comprehensive longitudinal health record that combines data from multiple care facilities and specialties across a patient's lifetime. Unlike an EMR (limited to a single facility), an EHR is inherently interoperable. (Hồ sơ sức khỏe điện tử)

Vietnam context: The Personal Health Record (Sổ Sức khỏe điện tử) on VNeID, established by Decision 1332/QĐ-BYT, is a national-scale EHR that aggregates a citizen's clinical data from many hospitals.

Electronic Medical Record — the digital version of a medical record within a single care facility. It includes history, diagnoses, lab results, prescriptions, and nursing forms. Circular 13/2025/TT-BYT sets September 30, 2025 for hospitals and December 31, 2026 for other healthcare facilities. (Bệnh án điện tử)

Vietnam context: A FHIR document Bundle is one technical option for record exchange; Circular 13/2025/TT-BYT does not by itself require a facility to export a FHIR Bundle to VNeID. The format and endpoint must come from an interoperability specification published by the competent authority.

A FHIR Resource representing an interaction between a patient and a healthcare facility — outpatient visit, inpatient admission, emergency, or telehealth consultation. An Encounter has start and end times, a type, a reason, participants (Practitioner), and a location. (Lượt khám / Đợt điều trị)

Vietnam context: In VN Core Encounter, the Extension `tuyenKCB` records whether the encounter is in-tier, out-of-tier, or cross-tier — a BHYT payment policy under Decree 188/2025/NĐ-CP.

A FHIR Resource that contains the insurer's detailed response to a Claim: approved items, denied items, denial reasons, paid amounts, and patient copay. (ExplanationOfBenefit)

Vietnam context: When Vietnam Social Security responds to a payment request based on Decision 697/QĐ-BYT (the 12-category billing summary template), the returned data can be mapped to ExplanationOfBenefit.

The FHIR mechanism for adding fields to a base Resource or DataType without breaking interoperability. Each Extension has its own canonical URL, definition (StructureDefinition), and context indicating where it can be applied. (Phần mở rộng)

Vietnam context: VN Core defines the Extension `vn-ext-ethnicity` (54 ethnic groups) for use on Patient. Canonical URL: `http://fhir.hl7.org.vn/core/StructureDefinition/vn-ext-ethnicity`.

HL7's standard for exchanging electronic health data. FHIR is most often deployed as REST + JSON, but it also supports XML, Turtle, and non-REST patterns such as messaging, documents, and services. Each data type is modeled as a Resource with its own URL. (Fast Healthcare Interoperability Resources)

Vietnam context: The VN Core IG is based on FHIR R4 (4.0.1, published 2019). The VN Core canonical URL is `http://fhir.hl7.org.vn/core/`.

A path expression language for navigating and querying FHIR instances, similar to XPath for XML. It is used in invariants (validation rules), search parameters, slicing discriminators, and CDS Hooks. (Ngôn ngữ truy vấn FHIRPath)

Vietnam context: The expression `Patient.identifier.where(system = 'http://fhir.hl7.org.vn/core/sid/cccd').value` extracts the patient's CCCD number.

A model that rates the maturity of a FHIR artifact on a 0–5 scale. FMM and Standards Status are separate axes: Normative, Trial Use, Draft, or Informative is not a “next level” after FMM 5. FMM reflects implementation evidence, testing, and stability under the HL7 process. (FHIR Maturity Model)

Vietnam context: When assessing a Resource for VN Core, read both its FMM and its Standards Status for the exact FHIR release; do not infer Normative status from a high FMM alone.

A domain-specific language for authoring Profiles, Extensions, ValueSets, and Examples more concisely than raw JSON or XML. FSH is compiled to StructureDefinition JSON by SUSHI and is the de facto standard for building IGs. (FHIR Shorthand)

Vietnam context: The VN Core IG is written in FSH inside the `input/fsh/` folder. For example: `Profile: VNCorePatient` followed by the constraint `* identifier 1..* MS` to tighten cardinality.

A FHIR Resource that represents the output of a Clinical Decision Support service, such as the result of a CDS Hook or an AI inference. It contains the decision (status), recommendation, evidence, and provenance. (Phản hồi gợi ý CDS)

Vietnam context: When a clinician orders a contrast-enhanced CT, a CDS service can return a GuidanceResponse warning of kidney injury risk based on the patient's most recent creatinine Observation.

The leading open-source Java implementation of FHIR (server, client, and data layer), maintained by Smile CDR and the University Health Network. It is the most widely deployed FHIR server in research, prototyping, and several large production systems. (HAPI FHIR — open source Java)

Vietnam context: A typical FHIR proof of concept can start with HAPI FHIR because it is free, well documented, and easy to run as an internal sandbox.

Infrastructure that enables health data sharing across multiple organizations — hospitals, clinics, pharmacies, and payers. An HIE typically includes a patient registry, a document registry, a terminology service, and security policies. (Health Information Exchange)

Vietnam context: The Personal Health Record on VNeID is a national-scale HIE. Decree 278/2025/NĐ-CP mandates connection and data sharing, with December 31, 2026 as the milestone for standardization.

The international health data standards organization, founded in 1987 and headquartered in Ann Arbor, Michigan, USA. "Level 7" refers to the Application layer of the OSI model. HL7 publishes the v2, v3, CDA, FHIR, and CDS Hooks standards. (Health Level Seven)

Vietnam context: HL7 International operates a network of national Affiliates. Omi HealthTech is preparing the technical foundation and governance file for an HL7 Affiliate Vietnam path once conditions are met.

The WHO's disease classification system. Vietnam published a localized release per Decision 4469/QĐ-BYT (October 28, 2020), later extended with COVID-19 codes (U07.1, U07.2) by Decision 98/QĐ-BYT (January 14, 2022). (International Classification of Diseases, revision 10)

Vietnam context: `vn-icd10-cs` on the public IG has `content = not-present`; the complete dataset is on the download surface. `VNCoreCondition.code` is required, but its `vn-condition-code-vs` binding is extensible, and ICD-10 codings use the standard system `http://hl7.org/fhir/sid/icd-10`.

A standardized documentation package for a use case or country, containing Profiles, Extensions, ValueSets, CodeSystems, Examples, narrative pages, and CapabilityStatements. An IG is published as both an npm package and a static website. (Implementation Guide)

Vietnam context: The VN Core IG (id `hl7.fhir.vn.core`) is an Implementation Guide for the Vietnamese healthcare context, initiated by Omi HealthTech and published at fhir.hl7.org.vn.

An international consortium that publishes integration Profiles built on top of foundational standards (HL7, DICOM, W3C). Each Profile (XDS, PIX, ATNA, MHD, and others) describes how to combine multiple standards to address a specific workflow. (Integrating the Healthcare Enterprise)

Vietnam context: MHD is one reference for FHIR document sharing when the parties select the exact actors, transactions, options, and version. Only end-to-end conformance testing demonstrates interoperability within the tested scope.

HL7's international IG for a minimum patient summary used in cross-border exchange. IPS defines a Composition with required sections (allergies, current medications, clinical problems) plus several recommended sections. (International Patient Summary)

Vietnam context: IPS can be evaluated as a Patient Summary pattern; it is not automatically generated from VNeID. Use it only when the dataset and contract permit it and validate the instance against the exact package, version, and terminology.

A code system for laboratory tests, clinical observations, and document types, maintained by the Regenstrief Institute under the LOINC licence. Use LOINC in `Observation.code` when the binding, use case, and receiving system require or accept the applicable code and version.

Vietnam context: The LOINC code `718-7` (Hemoglobin [Mass/volume]) is used in complete blood count Observations, paired with the UCUM unit `g/dL`.

An IHE Profile for exchanging health documents through FHIR. The R4 profiles use `DocumentReference`, `List`, `Bundle`, and `Binary`; SubmissionSets and Folders use `List`, not `DocumentManifest`. MHD is not a one-to-one replacement for XDS.

Vietnam context: Select MHD for a personal health record only when the contract requires the exact actor, transaction, option, and version; adding a PDF or JPEG does not establish MHD conformance.

A TCP transport protocol for HL7 v2 messaging. Each v2 message is wrapped in the frame `<VT>...message...<FS><CR>` and sent over a TCP socket. MLLP remains widely used in HIS-LIS-PACS integrations today. (Minimal Lower Layer Protocol)

Vietnam context: A HIS-to-analyzer interface may use MLLP plus an HL7 v2 ORU^R01 message where the device supports it. TLS, VPN, or equivalent controls follow the threat model and security contract; the law does not prescribe TLS for every MLLP link.

A flag on a Profile element. When marked `MS`, the Implementation Guide must explicitly define what "meaningful support" means — it can mean read, write, display, or some combination. MS is not the same as cardinality and does not automatically require both read and write; the Profile or IG specifies the details. (Phải hỗ trợ)

Vietnam context: VN Core Patient marks `identifier MS`, and the narrative explains: FHIR servers in Vietnam must read and store the CCCD; clients must display it on the medical record UI.

A FHIR Resource that registers the URIs used as the `system` for Identifiers (CCCD, BHYT, BHXH, MRN, passport, and so on). NamingSystem helps stakeholders agree on how to disambiguate identifiers issued by different authorities. (Hệ định danh)

Vietnam context: VN Core v0.9.0 publishes 36 NamingSystem artifacts spanning citizen, insurance, facility/workforce, document, transaction, and integration-endpoint namespaces. The core identifier group includes CCCD, CMND, BHXH, BHYT, healthcare facility code, practitioner license, passport, MRN, and birth certificate. Sample URI: `http://fhir.hl7.org.vn/core/sid/cccd`.

An HL7 Standards Status with strict change-control rules intended to protect backward compatibility. Normative is independent of FMM and does not guarantee that every detail is immutable in every later release. (Đã chuẩn hoá — cam kết bất biến)

Vietnam context: When moving VN Core to another FHIR release, implementers must still assess deltas and package dependencies even when the base Resource has Standards Status = Normative.

The IETF authorization framework in RFC 6749; OAuth 2.0 is not itself authentication. SMART App Launch profiles OAuth/OIDC for FHIR use cases, while a FHIR endpoint may use another mechanism when its IG and security contract allow it.

Vietnam context: PKCE applies to the relevant client and flow under the selected OAuth/SMART profile. Law 91/2025 and Decree 356/2025 do not themselves mandate OAuth, PKCE, or refresh tokens for every FHIR server.

A FHIR Resource that represents errors, warnings, or processing information through `issue` entries with severity, code, and diagnostics. FHIR recommends OperationOutcome for FHIR-layer errors, but it is not required in every 4xx/5xx response; proxy, authentication, or infrastructure failures may have an empty or non-FHIR body. (Kết quả thao tác)

Vietnam context: When a Patient fails VN Core validation, a server may return the HTTP status appropriate to the interaction and API contract with an OperationOutcome identifying the offending element; clients must still handle the absence of an OperationOutcome safely.

Two IHE Profiles for identity management: PIX cross-references patient identifiers across domains, while PDQ queries demographic information by identifier. The FHIR-native equivalents are IHE PIXm and PDQm. Applying these profiles to VNeID or the Personal Health Record is currently a reference architecture, not an API prescription, because no public official API specification is available. (Patient Identifier Cross-reference / Patient Demographics Query)

Vietnam context: A future architecture could use PIXm to link an internal MRN to the personal identification number and PDQm to query demographics, but only if the official national-service specification defines the corresponding endpoints and profiles.

A StructureDefinition derived from a base Resource or DataType that adds constraints: cardinality, terminology bindings, slicing, MS flags, and invariants. A Profile does not create a new Resource — it narrows how a base Resource is used. (Cấu hình ràng buộc)

Vietnam context: VNCorePatient (id `vn-core-patient`, canonical `http://fhir.hl7.org.vn/core/StructureDefinition/vn-core-patient`) derives from FHIR Patient, adds CCCD/BHYT/MRN identifier slicing, and carries the ethnicity extension. Addresses use VNCoreAddress with coded province and ward extensions.

A FHIR Resource that records the origin and creation, modification, or transformation of a Resource: agents, time, source entities, and an optional signature. Provenance does not by itself create a complete audit trail, non-repudiation, or legal validity; those properties also depend on the signing mechanism, certificate, signed bytes, and operational controls. (Nguồn gốc dữ liệu)

Vietnam context: When a workflow requires an electronic signature, `Provenance.signature` can carry the signature and related metadata; the system must still verify it and satisfy the applicable legal policy.

Three version milestones must be distinguished. R4 (4.0.1, published 2019) is the VN Core baseline, combines Normative and STU content, and defines 146 Resources. R5 (5.0.0, published March 2023) is the latest published major release and remains Trial Use. R6 is currently a CI/ballot build, not a stable release. (FHIR Release 4 / Release 5 / Release 6)

Vietnam context: The VN Core sushi-config sets `fhirVersion: 4.0.1`. Publishing VN Core on another version should follow compatibility assessment of target IGs, package dependencies, validators, and endpoints.

The core data unit in FHIR — each type of health data (Patient, Encounter, Observation, MedicationRequest, and so on) is represented by a Resource type. FHIR R4 has 146 Resource types. REST interactions such as GET, POST, PUT, and DELETE are available only when the endpoint declares support for them in its CapabilityStatement. (Tài nguyên FHIR)

Vietnam context: `GET https://fhir.bv.vn/Patient/12345` returns a Patient Resource as JSON, with Resource.id = "12345" and a Resource.meta.versionId that increments on each update.

The architectural style for web APIs described by Roy Fielding in his 2000 dissertation. Its hallmarks are statelessness, resource orientation, HTTP verbs (GET, POST, PUT, DELETE), and URLs that represent resources. The FHIR REST API is the most common deployment pattern of FHIR. (Representational State Transfer)

Vietnam context: A FHIR REST call: `GET /Patient?identifier=cccd|012345678901` searches for a patient by CCCD. The server returns a Bundle (searchset) with the matching Patients.

The foundational information model of HL7 v3, defining six root classes (Act, Entity, Role, Participation, RoleLink, ActRelationship) from which every v3 message is derived. RIM is highly abstract — one of the reasons v3 was difficult to deploy. (Reference Information Model)

Vietnam context: Although FHIR does not use RIM directly, several Resources (Encounter, Observation) borrow the Act-Participation pattern to model actions and participants.

A definition of how to query a Resource by specific fields: name, identifier, date, _id, _lastUpdated, and so on. Each Resource has standard search parameters, and an IG may publish additional parameters tailored to local context. (Tham số tìm kiếm)

Vietnam context: VN Core can publish a `cccd` search parameter for Patient so clients write `GET /Patient?cccd=012345678901` instead of the more complex `identifier=http://fhir.hl7.org.vn/core/sid/cccd|012345678901`.

A Profile mechanism for partitioning an array element into multiple slices using a discriminator (a distinguishing value or pattern). Each slice carries its own cardinality and constraints. (Cắt lát)

Vietnam context: VNCorePatient v0.9.0 slices `identifier` with a `#pattern` discriminator at path `type`: CCCD `1..1 MS`, BHYT `0..1 MS`, and MRN `0..* MS`. MRNs use per-facility `system` URIs; the CCCD slice may carry `data-absent-reason` in a valid exception.

The HL7 standard for launching healthcare apps (EHR-launched or standalone) on a FHIR server, using OAuth 2.0, OpenID Connect, and health-specific scopes (`patient/Observation.read`, `user/*.read`). It is the foundation of the FHIR app ecosystem. (SMART on FHIR)

Vietnam context: When deploying a mobile app for citizens to view their VNeID Personal Health Record, SMART on FHIR is the standard pattern for letting the app sign in via VNeID and read Patient and Observation Resources from the national FHIR server (reference architecture — pending official spec).

The world's largest clinical terminology, governed by SNOMED International, with roughly 350,000 concepts arranged in a multi-axial hierarchy. Vietnam is building SNOMED CT VN through Decisions 2427/QĐ-BYT (Body Structure), 2493/QĐ-BYT (Morphologic Abnormality), and 2805/QĐ-BYT (Allergy + Finding) issued in 2025. (SNOMED Clinical Terms)

Vietnam context: The SNOMED CT concept `38341003 |Hypertensive disorder, systemic arterial|` is translated into Vietnamese and published in the CodeSystem `vn-snomed-cs` per Decision 2805/QĐ-BYT.

An open-source terminology server for SNOMED CT, built on Elasticsearch and developed by SNOMED International. It supports ECL and the FHIR Terminology Service operations ($lookup, $expand, $validate-code). (Snowstorm — terminology server)

Vietnam context: When building a national terminology service, Snowstorm can be self-hosted in Vietnam, loaded with SNOMED CT VN, ICD-10 VN, and DVKT, and exposed as a FHIR Terminology Service for every HIS to query.

The compiler that turns FSH source into StructureDefinition, ValueSet, and CodeSystem JSON. SUSHI is written in TypeScript and runs on Node.js. It is the de facto standard build tool for every modern FHIR IG. (SUSHI — FSH compiler)

Vietnam context: The VN Core build pipeline: write FSH inside `input/fsh/` → run `sushi .` to compile to JSON → run the IG Publisher to render the static website.

A FHIR Resource that defines the schema of a Resource type, DataType, Profile, or Extension. It is the foundational metadata — an IG is essentially a collection of StructureDefinitions plus ValueSets, CodeSystems, and narrative pages. (Định nghĩa cấu trúc)

Vietnam context: Every Profile (VNCorePatient, VNCoreEncounter) and Extension (vn-ext-ethnicity, vn-ext-bhyt-card-type) in VN Core is a StructureDefinition.

Standardized code sets that ensure consistency and machine readability — including CodeSystems (which define codes) and ValueSets (which select code subsets for specific fields). Terminology is at the heart of semantic interoperability in FHIR. (Thuật ngữ chuẩn hoá)

Vietnam context: VN Core terminology includes ICD-10 VN, SNOMED CT VN, LOINC, UCUM, DVKT (Circular 23/2024), the 54 Vietnamese ethnic groups, and the 34 administrative divisions per Resolution 202/2025.

The standard code set for units of measure in healthcare and science, maintained by the Regenstrief Institute. Base FHIR Quantity does not require UCUM; a Profile or Implementation Guide can require or recommend UCUM to support unit validation and conversion. (Unified Code for Units of Measure)

Vietnam context: A glucose Observation can use `{ value: 5.5, unit: "mmol/L", system: "http://unitsofmeasure.org", code: "mmol/L" }`. Convert only after checking the measured property, laboratory context, and profile rules; UCUM alone does not make every conversion clinically valid.

A FHIR Resource that defines a subset of codes drawn from one or more CodeSystems and bound to an element. A ValueSet can be extensional (an explicit list of codes) or intensional (defined by filters or ECL). (Tập giá trị)

Vietnam context: The VN Core ValueSet `vn-ethnicity-vs` selects all 54 concepts from the CodeSystem `vn-ethnicity-cs`. It is bound to Patient.extension.ethnicity with binding strength = required.

Vietnam's national digital identification app, operated by the Ministry of Public Security. VNeID integrates the CCCD, BHXH/BHYT, driving licenses, and the Personal Health Record (Decision 1332/QĐ-BYT). It is the primary channel through which citizens interact with digital public services. (Vietnam Electronic Identification)

Vietnam context: Article 1(3) of Circular 13/2025/TT-BYT requires electronic-record information to be linked to the personal identification number of Vietnamese citizens and of foreign nationals who have been issued an electronic identification account. It does not itself define a VNeID API, payload, or synchronization flow.

An IHE Profile for cross-enterprise document sharing using the ebXML Registry Information Model and web services. An XDS Affinity Domain includes actors such as Document Source, Document Repository, Document Registry, and Document Consumer. MHD offers FHIR-based interfaces for a subset of document-sharing use cases; it is not a complete replacement for XDS/XCA. (Cross-Enterprise Document Sharing)

Vietnam context: A project selects XDS, MHD, or a FHIR-native model according to its use case, installed infrastructure, and conformance requirements; Vietnam has no default migration path.

The XML format issued by the Ministry of Health for output data submitted to Vietnam Social Security. Decision 4210/QĐ-BYT was the original document, superseded by Decision 130/QĐ-BYT (2023), which was then amended by Decision 4750/QĐ-BYT (2023) and Decision 3176/QĐ-BYT (2024). The name "XML 4210" remains in common use even though the underlying chain of decisions has moved on. (Định dạng XML 4210 — BHXH legacy)

Vietnam context: When specifying a transformation from current XML to FHIR Claim/EOB, use the Decision 130, 4750, and 3176 chain rather than relying only on the original Decision 4210.