Patient Demographics Query for Mobile (PDQm)
3.1.0 - Trial-Implementation International flag

This page is part of the IHE Patient Demographics Query for Mobile (v3.1.0: Publication) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

OperationDefinition: PDQm $Match

Official URL: https://profiles.ihe.net/ITI/PDQm/OperationDefinition/PDQmMatch Version: 3.1.0
Draft as of 2024-12-02 Computable Name: Find_Patient_Matches_PDQm

This operation implements the Patient Demographics Match [ITI-119] transaction. It is fully compatible with the $match Operation on Patient. The only changes are to constrain the input parameters to use the PDQm Patient Profile for $match Input profile and to constring the output parameters to use the PDQm Patient Profile profile.

Generated Narrative: OperationDefinition PDQmMatch

URL: [base]/Patient/$match

Input parameters Profile:PDQm Match Input Parameters Profile

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INresource1..1Patient

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).

INonlyCertainMatches0..1boolean

If there are multiple potential matches, then the match SHOULD not return the results with this flag set to true. When false, the server MAY return multiple results with each result graded accordingly.

INcount0..1integer

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.

OUTreturn1..1Bundle (PDQm Match Output Bundle Profile)

A bundle contain 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).

Note: as this is the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource