CH EPR FHIR (R4)
5.0.0-ballot-ci-build - ci-build
CH EPR FHIR (R4)
5.0.0-ballot-ci-build - ci-build
CH EPR FHIR (R4), published by eHealth Suisse. This guide is not an authorized publication; it is the continuous build for version 5.0.0-ballot-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/ehealthsuisse/ch-epr-fhir/ and changes regularly. See the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-epr-fhir/OperationDefinition/CHPDQmMatch | Version: 5.0.0-ballot-ci-build | |||
| Active as of 2024-12-18 | Computable Name: Find_Patient_Matches_PDQm | |||
Copyright/Legal: CC0-1.0 |
||||
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 CHPDQmMatch
URL: [base]/Patient/$match
Input parameters Profile:CH PDQm Match Input Parameters Profile
Output parameters Profile:CH PDQm Match Output Bundle Profile
| 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 | 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. | ||
| 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 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 |