BC Client Registry FHIR Implementation Guide
1.0.0 - Build CI
BC Client Registry FHIR Implementation Guide
1.0.0 - Build CI
BC Client Registry FHIR Implementation Guide - Local Development build (v1.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://hlth.gov.bc.ca/fhir/client/OperationDefinition/bc-patient-notification | Version: 1.0.0 | |||
| Draft as of 2024-06-07 | Computable Name: PatientNotification | |||
This operation is used notify a user that a patient’s record has changed.
Note
This specification is currently published as a Draft Standard on the ministry GitHub and is not intended for implementation. Feedback is welcome but readers should understand that there is more work to be done in testing the profiles and operations defined in this guide. For more information, please see the Future Plans page in this guide.
This is the Patient Notification operation, aka Distribution.
A Patient resource is required to notify that a patient record has changed. This interaction is similar to RevisePatient, but the Client Registry is acting as the client.
URL: [base]/Patient/$PatientNotification
Input parameters Profile:ReviseRequestBundle
Parameters
| Use | Name | Scope | Cardinality | Type | Binding | Documentation |
| IN | ReviseRequestBundle | 1..1 | Bundle | The request bundle. |
The response to a Patient Notification Operation is a HTTP status code 200 on success without a body..
| Cardinality | Resource Type | Comment |
|---|---|---|
| 1..1 | MetadataParametersIn | See profile. |
| 1..1 | ClientRegistryPatient | See profile. |
N/A
Besides the two mandatory name-value pairs, none.
N/A
The following example is actually the revise patient example as it is identical to the notification request. See Patient Notification request example.