New Zealand NHI IG
1.5.4 - Release
New Zealand NHI IG
1.5.4 - Release
New Zealand NHI IG - Local Development build (v1.5.4) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://nhi-ig.hip.digital.health.nz/OperationDefinition/Patient-match | Version: 1.5.4 | |||
| Draft as of 2023-06-12 | Computable Name: Match | |||
A Master Patient Index (MPI ) is a service used to manage patient identification in a context where multiple patient databases exist. Healthcare applications and middleware use the MPI to match patients between the databases, and to store new patient details as they are encountered. MPIs are highly specialized applications, often tailored extensively to the institution’s particular mix of patients. MPIs can also be run on a regional and national basis.
To ask an MPI to match a patient, clients use the "$match" operation, which accepts a patient resource which may be only partially complete. The data provided is interpreted as an MPI input and processed by an algorithm of some kind that uses the data to determine the most appropriate matches in the patient set. Note that different MPI matching algorithms have different required inputs. The generic $match operation does not specify any particular algorithm, nor a minimum set of information that must be provided when asking for an MPI match operation to be performed, but many implementations will have a set of minimum information, which may be declared in their definition of the $match operation by specifying a profile on the resource parameter, indicating which properties are required in the search. The patient resource submitted to the operation does not have to be complete, nor does it need to pass validation (i.e. mandatory fields don’t need to be populated), but it does have to be a valid instance, as it is used as the reference data to match against.
URL: [base]/Patient/$match
Parameters
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | resource | 1..1 | Patient | Use this to provide an entire set of patient details for the MPI to match against (e.g. POST a patient record to Patient/$match). | ||
| IN | onlyCertainMatches | 0..1 | boolean | When set to TRUE = Validate, When set to FALSE = NHI Search | ||
| IN | count | 0..1 | integer | The maximum number of records to return. If no value is provided, the server decides how many matches to return. Note that clients should be careful when using this, as it may prevent probable - and valid - matches from being returned | ||
| OUT | return | 1..1 | Bundle | A bundle containing a set of Patient records that represent possible matches, optionally it may also contain an OperationOutcome with further information about the search results (such as warnings or information messages, such as a count of records that were close but eliminated) If the operation was unsuccessful, then an OperationOutcome may be returned along with a BadRequest status Code (e.g. security issue, or insufficient properties in patient fragment - check against profile) | ||
| OUT | failure | 0..1 | OperationOutcome | Error response |
The response is a bundle containing a patient record (validate) or records (match). For match the records are ordered from most likely to least likely. If there are no patient matches an empty search set with no error will be returned. All patient records SHALL have a search score from 0 to 1, where 1 is the most certain match, along with "match-grade" that indicates the MPI's position on the match quality.