MediRecords FHIR Implementation Guide
1.4.1 - release
The MediRecords FHIR API supports the following DiagnosticReport operations.
GET {API_URL}/v1/DiagnosticReport/{id}
This API interface enables the client to read a DiagnosticReport resource from MediRecords repository which is compliant with the supported MediRecords DiagnosticReport profiles.
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 DiagnosticReport resource.
| Hub Event | Application Trigger Event |
|---|---|
| diagnostic-report.created | Occurs whenever a new diagnostic results record is created |
| diagnostic-report.updated | Occurs whenever a diagnostic results record is updated |
Bundle <br>
DiagnosticReport(1)
Encounter (0..1)
Patient (1)
PractitionerRole (0..1)
Practitioner (0..3)
Organization (0..3)
| diagnostic-report.deleted | Occurs whenever a diagnostic results record is deleted |
Bundle
request (1)
url: DELETE DiagnosticReport/{id}