...
Based on the high level workflow mentioned above, the list of transactional indicators are below:
...
- Count of ServiceRequests Created
...
- Count of ServiceRequests Claimed
...
- Count of ServiceRequests Completed
...
- Count of ServiceRequests Completed with Outcome of X
...
- Count of ServiceRequests Completed with Outcome of Y
...
- Average Time from Created to Claimed
...
- Average Time from Claimed to Completed
...
- Average Time from Created to Completed
The ultimate goal of these follow-ups is that the patient returns to care, so the most important indicator is probably "% of patients that have returned to care".
Key FHIR Resources
The essential resources for this workflow are as follows.
| Description | Structure Definition | Samples |
|---|---|---|
| Patient | Patient.StructureDefinition.json | patient_cht.fhir.json |
| ServiceRequest | ServiceRequest.StructureDefinition.json | service_request.fhir.json |
| Encounter | Encounter.StructureDefinition.json | encounter_cht.fhir.json |
Reference Architecture
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. Detailed technical information and instructions for the CoPs shared infrastructure can be found here.
...