MediRecords FHIR Implementation Guide
1.4.2 - release
The MediRecords FHIR API supports the following Practitioner operations.
GET {API_URL}/v1/Consent/{id}
This API interface enables the client to read a Consent resource from MediRecords repository which is compliant with this MediRecords Consent profile.
| Request Parameters | |
|---|---|
| id | The logical id of the Consent resource |
In an error situation, server SHALL return OperationOutcome detailing the error with the appropriate HTTP Error code as follows.
| Status | Text |
|---|---|
| 200 | OK |
| 400 | Bad Request |
| 401 | Unauthorized |
| 403 | Forbidden |
| 404 | Not Found |
| 500 | Internal Server Error |
The following table provides the FHIR Webhook event types generated for the Patient resource.
| Hub Event | Application Trigger Event | |
|---|---|---|
| consent.created | Occurs whenever a new consent record is created | Example |
| consent.updated | Occurs whenever a consent record is updated |
Bundle
Consent (1)
Patient (1)
DocumentReference (0..*)
Organization (0..*)
Practitioner (0..*)