This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/match-grade |
Version: | 4.2.0 |
Name: | MatchGrade |
Title: | MatchGrade |
Definition: | A Master Patient Index (MPI) assessment of whether a candidate patient record is a match or not. |
Committee: | FHIR Infrastructure Work Group |
OID: | 2.16.840.1.113883.4.642.3.970 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/match-grade
This expansion generated 31 Dec 2019
This value set contains 4 concepts
Expansion based on http://terminology.hl7.org/CodeSystem/match-grade version 4.2.0
All codes from system http://terminology.hl7.org/CodeSystem/match-grade
Code | Display | Definition |
certain | Certain Match | This record meets the matching criteria to be automatically considered as a full match. |
probable | Probable Match | This record is a close match, but not a certain match. Additional review (e.g. by a human) may be required before using this as a match. |
possible | Possible Match | This record may be a matching one. Additional review (e.g. by a human) SHOULD be performed before using this as a match. |
certainly-not | Certainly Not a Match | This record is known not to be a match. Note that usually non-matching records are not returned, but in some cases records previously or likely considered as a match may specifically be negated by the matching engine. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |