Athena Core Implementation Guide
4.2.0 - release
Athena Core Implementation Guide
4.2.0 - release
Athena Core Implementation Guide - Local Development build (v4.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://fhir.athena.io/OperationDefinition/ah-sync-external-patient | Version: 4.2.0 | |||
| Active as of 2025-04-17 | Computable Name: AthenahealthSyncExternalPatient | |||
The $sync-external operation is used to replicate Patient resources from an external source system into athenahealth’s Patient Directory. This allows these records to be linked to athenahealth’s master Person index where applicable and queried using the Patient/$match operation (subject to pre-established access control restrictions). Note that this operation is asynchronous. A 202 status response indicates that the input Patient resource(s) have passed initial validation and been queued for ingestion, but it may take some minutes before the records are available to search.
Generated Narrative: OperationDefinition ah-sync-external-patient
Information Source: athenacoreext
URL: [base]/Patient/$sync-external
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | patient | 1..* | Patient | Use this to provide an entire set of patient details from the user to save it in Athena Directory (e.g. POST a patient record to Patient/$sync-external). | ||
| IN | priorityFlag | 0..1 | boolean | If this parameter is set as (priorityFlag: true) then the patient resources would be added to the priority queue and these resources would ingested faster. If this parameter is set as (priorityFlag: false) or not specified in the input then the patient resources would be added to the non-priority queue and these resources would be ingested based on the current lag in the non-priority queue. |