Athena Core Implementation Guide
2.33.0 - release
Athena Core Implementation Guide
2.33.0 - release
Athena Core Implementation Guide - Local Development build (v2.33.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.athena.io/OperationDefinition/ah-patient-match | Version: 2.33.0 | |||
| Active as of 2024-04-12 | Computable Name: AthenahealthPatientMatch | |||
An extension to the base Patient-match OperationDefinition adding two additional optional input parameters to further classify the specific Patient match criteria.
URL: [base]/Patient/$match
Parameters
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | resource | 1..1 | Resource | 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. | ||
| IN | x-useCase | 0..1 | string | The athenahealth Patient match use case (Scheduling | CareQuality | HDPE). | ||
| IN | x-targetSource | 0..* | uri | This can be used to specify target source from which patient records are retrieved | ||
| 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) |