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: OmiGroup is working with the Vietnamese FHIR community to establish HL7 Affiliate Vietnam. Once incorporated, the Affiliate will become the official body coordinating the VN Core IG.

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 that specifies how health systems record audit logs and authenticate node-to-node using TLS mutual authentication. ATNA is mandatory for every node participating in an XDS affinity domain. (Audit Trail and Node Authentication)

Vietnam context: When deploying an HIE that connects hospitals through the IHE model, every node must comply with ATNA to satisfy the security requirements of Law 91/2025/QH15 on personal data protection.

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 compliance with Law 91/2025/QH15 (Personal Data Protection Law) and Decree 356/2025/NĐ-CP, FHIR servers in Vietnam should configure AuditEvent for every access to sensitive health data.

Vietnam's national social health insurance scheme (Bảo hiểm Y tế), administered by Vietnam Social Security (BHXH). A BHYT card number contains 15 characters (2 letters plus 13 digits) and encodes the beneficiary type, the province code, and the initial registered care facility. (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`. This URL is referenced from `Patient.meta.profile` on every conforming instance.

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..*`; VN Core Patient tightens it to `1..*` to require at least one identifier per patient (CCCD, BHYT, or MRN).

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`. Circular 13/2025/TT-BYT requires every electronic medical record to be linked to either a CCCD or a VNeID account.

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 standard uses CDA for inter-hospital data exchange. Vietnam can choose between FHIR Composition (FHIR-native) and CDA depending on the 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) along with a 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 defines a terminology and the attributes of each code. Every CodeSystem has a canonical URL, a version, and a list of concepts (code + display + multilingual designations). It is the foundation for ValueSets and Codings. (Hệ mã)

Vietnam context: VN Core publishes the CodeSystem `vn-icd10-cs` (the Vietnamese ICD-10 release per Decision 4469/QĐ-BYT) and `vn-ethnicity-cs` (the 54 Vietnamese ethnic groups per the General Statistics Office).

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: `{"system": "http://fhir.hl7.org.vn/core/CodeSystem/vn-icd10-cs", "code": "I10", "display": "Bệnh tăng huyết áp vô căn (nguyên phát)"}`.

A FHIR Resource that acts as the header of a clinical document, equivalent to the CDA header. Composition references other Resources (Patient, Encounter, Observation, MedicationStatement) to form a Bundle of type `document`. (Hợp phần / Header bệnh án)

Vietnam context: Electronic medical records under Circular 13/2025/TT-BYT can be represented as a Bundle/document with Composition as the first entry, describing the record type, signing date, and digital signer.

A FHIR Resource that declares mappings between codes from different CodeSystems. Each mapping carries a semantic relationship: equivalent, equal, wider, narrower, related-to, or unrelated. (Bản đồ ánh xạ mã)

Vietnam context: VN Core can publish a ConceptMap from ICD-10 VN to ICD-10 WHO, or from XML 4210 fields to FHIR Claim/EOB elements to support BHYT submissions.

A periodic event hosted by HL7 or IHE where vendors bring their software to test interoperability against one another using standardized scenarios. Connectathons are the primary mechanism for proving the maturity of an Implementation Guide. (Sự kiện kiểm thử liên thông đa vendor)

Vietnam context: OmiGroup's goal is to host the first Vietnam FHIR Connectathon in 2027, bringing together major HIS vendors (FPT, Viettel, VNPT, Misa, Ominext) to test the VN Core IG.

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: PACS and RIS systems in Vietnamese hospitals are built on DICOM. VN Core can reference a DICOM Study via the FHIR ImagingStudy Resource.

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.

Data Protection Impact Assessment — the process of evaluating privacy risks before deploying systems that process sensitive personal data. In Vietnam, a DPIA is mandatory under Form No. 10 of Decree 356/2025/NĐ-CP, especially for health data. (Đánh giá tác động bảo vệ dữ liệu)

Vietnam context: A hospital deploying a FHIR server connected to VNeID must complete and retain a DPIA on file; inspection authorities have the right to request it.

Data Protection Officer — a mandatory role under Decree 356/2025/NĐ-CP for organizations processing sensitive personal data, including health data. The DPO oversees compliance and serves as the point of contact for regulators and data subjects. (Cán bộ bảo vệ dữ liệu)

Vietnam context: Every Class I or higher hospital must appoint a DPO. The DPO signs off DPIAs and is the contact for the 72-hour breach notification under Form No. 08.

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 a deadline of December 31, 2026 for every healthcare facility to deploy an EMR. (Bệnh án điện tử)

Vietnam context: A Class I hospital's EMR must be capable of exporting a FHIR document Bundle to interoperate with the national EHR on VNeID, per the Ministry of Health's roadmap.

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 Resource on a 0–5 scale, followed by Normative. FMM 0 means a fresh draft, FMM 3 indicates implementation and testing experience, and FMM 5 reflects multiple production deployments. Patient, Observation, and Condition reached Normative status in R4. (FHIR Maturity Model)

Vietnam context: When selecting Resources for VN Core, prioritize those at FMM ≥ 3 to reduce the risk of breaking changes. Low-FMM Resources such as ResearchStudy should be used cautiously.

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: Most FHIR proofs of concept in Vietnam (Bach Mai Hospital, Vinmec, Hong Ngoc) start with HAPI FHIR thanks to its zero cost and rich documentation.

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. OmiGroup is currently working to establish HL7 Affiliate Vietnam.

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: The VN Core CodeSystem `vn-icd10-cs` contains the full Vietnamese ICD-10 release and is the required binding for `Condition.code` in the VNCoreCondition Profile.

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 Vietnam's national Implementation Guide, currently being built by OmiGroup at github.com/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: IHE MHD is the primary reference for FHIR-native document sharing. When designing a Vietnamese HIE, adopting IHE Profiles cuts design time and ensures international interoperability.

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: When a Vietnamese citizen travels or seeks care abroad, an IPS Bundle can be generated from the VNeID Personal Health Record to share with overseas clinicians.

The standard code set for laboratory tests, clinical observations, and document types, maintained by the Regenstrief Institute. LOINC is free of charge, recommended by FHIR for `Observation.code`, and the current release contains more than 95,000 codes. (Logical Observation Identifiers Names and Codes)

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 that exposes health documents over a FHIR REST API — the FHIR-native counterpart of XDS. MHD uses DocumentReference and DocumentManifest along with the Provide & Submit, Find Documents, and Retrieve Document transactions. (Mobile access to Health Documents)

Vietnam context: MHD is the recommended design for a Personal Health Record that needs to expose scanned medical records as PDF or JPEG to mobile applications.

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: In Vietnamese hospitals, HIS integration with biochemistry analyzers typically uses MLLP plus HL7 v2.5 ORU^R01 messages. MLLP connections must use TLS to comply with Law 116/2025/QH15 (the revised Cybersecurity Law).

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 publishes NamingSystems for nine identifier types: CCCD, CMND, BHXH, BHYT, healthcare facility code, practitioner license, passport, MRN, and birth certificate. Sample URI: `http://fhir.hl7.org.vn/core/sid/cccd`.

The highest status in the FHIR Resource lifecycle. When a Resource reaches Normative, HL7 commits not to change it in a way that breaks backward compatibility. In R4, Patient, Observation, Encounter, Practitioner, Bundle, OperationOutcome, ValueSet, and CodeSystem are Normative. (Đã chuẩn hoá — cam kết bất biến)

Vietnam context: Because Patient is Normative, VN Core can constrain it through a Profile without worrying that future FHIR versions (R5, R6) will break core fields.

The IETF authorization framework standard (RFC 6749). OAuth 2.0 is not authentication — it grants access to resources on behalf of a user. It is the foundation for SMART on FHIR and any authenticated FHIR API. (OAuth 2.0)

Vietnam context: Every FHIR server complying with Law 91/2025 should implement OAuth 2.0 with PKCE rather than Basic Auth, to support refresh tokens, scope restrictions, and proper audit logging under Decree 356/2025/NĐ-CP.

A FHIR Resource returned to clients in error, warning, or confirmation scenarios. It contains a list of `issue` entries with severity, code, and diagnostics. Conformant FHIR servers must use OperationOutcome for 4xx and 5xx errors and for validation results. (Kết quả thao tác)

Vietnam context: When a POST of a Patient lacks a CCCD in VN Core, the server returns `400 Bad Request` with an OperationOutcome.issue containing the code `required` and Vietnamese diagnostics.

Two IHE Profiles for identity management: PIX cross-references patient identifiers across domains (hospital, BHYT, VNeID), while PDQ queries demographic information by identifier. The FHIR-native equivalents are IHE PIXm and PDQm. (Patient Identifier Cross-reference / Patient Demographics Query)

Vietnam context: When integrating a hospital HIS with the VNeID national database, PIXm maps the internal MRN to the CCCD; PDQm then retrieves patient demographics from the Personal Health Record.

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`) is a Profile derived from FHIR Patient that tightens identifier to 1..* and attaches Extensions for ethnicity, BHYT, and ward.

A FHIR Resource that captures the chain of custody for another Resource: who created it, who modified it, when, with what software, and whether it was digitally signed. Provenance is the technical foundation for audit and non-repudiation. (Nguồn gốc dữ liệu)

Vietnam context: Under Decree 137/2024/NĐ-CP on electronic transactions, every electronic medical record must carry a digital signature. Provenance.signature stores the signature of the clinician who signed the record.

The two principal FHIR versions. R4 (4.0.1, published 2019) is the production baseline and contains 145 Resources combining Normative and STU. R5 (5.0.0, published March 2023) adds new Resources and matures many STU items. The VN Core IG currently targets R4 because most worldwide implementations are still on R4. (FHIR Release 4 / Release 5)

Vietnam context: The VN Core sushi-config sets `fhirVersion: 4.0.1`. Once R5 matures and international IGs reference it, Vietnam can publish a parallel R5 release of VN Core.

The core data unit in FHIR — every type of health data (Patient, Encounter, Observation, MedicationRequest, and so on) is its own Resource type. FHIR R4 has 145 Resource types. Each instance has a unique URL and supports GET, POST, PUT, and DELETE over REST. (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 slices `identifier` by `system`: a CCCD slice (1..1, MS), a BHYT slice (0..1), and an MRN slice (0..*). The result: every instance must have one CCCD, may have one BHYT, and may have many MRNs.

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) 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. FHIR Quantity requires UCUM to ensure unit compatibility across systems. (Unified Code for Units of Measure)

Vietnam context: A glucose Observation: `valueQuantity = { value: 5.5, unit: "mmol/L", system: "http://unitsofmeasure.org", code: "mmol/L" }`. Conversion to mg/dL is safe because UCUM defines it.

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: Under Circular 13/2025/TT-BYT, every electronic medical record must be linked to a CCCD or VNeID account — paving the way for clinical data to flow into the Personal Health Record on VNeID (reference architecture — pending official API spec).

An IHE Profile for cross-enterprise document exchange, built on ebXML and SOAP. An XDS Affinity Domain comprises a Document Source, Document Repository, Document Registry, and Document Consumer. The FHIR-native counterpart is IHE MHD. (Cross-Enterprise Document Sharing)

Vietnam context: Several European national HIEs (Denmark, Switzerland) started with XDS and later migrated to MHD. Vietnam may skip XDS entirely and adopt MHD/FHIR-native from the outset.

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 building a ConceptMap from the current XML to FHIR Claim/EOB for VN Core, the references are Decisions 130, 4750, and 3176 — not the original Decision 4210.