This document is a work in progress. This dialog will be removed once the community agrees it is complete. |
This use case allows clinics to make requests to a CHIS to follow-up for various reasons. A common implementation might be for Lost to Follow-Up whereby the clinic generates a list of patients that have missed appointments and wants community based systems or health workers to find the patient and encourage them to attend their appointment or to understand why they cannot or will not.
See diagram below. From a high level, the steps can be summarized as:
→ Insert Diagram ←
Based on the high level workflow mentioned above, the list of transactional indicators are below:
# | Description | Notes |
---|---|---|
1 | Count of ServiceRequests Created | |
2 | Count of ServiceRequests Claimed | |
3 | Count of ServiceRequests Completed | |
4 | Count of ServiceRequests Completed with Outcome of X | |
5 | Count of ServiceRequests Completed with Outcome of Y |
The essential resources for this workflow are as follows
Description | Structure Definition | Samples |
---|---|---|
Patient | Patient.StructureDefinition.json | |
ServiceRequest | ServiceRequest.StructureDefinition.json | |
Encounter | Encounter.StructureDefinition.json |
The proof of concept uses the Instant OpenHIE architecture which utilizes a HAPI FHIR Server as a Shared Health Record component and OpenHIM for the Interoperability Layer.
The proof of