Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Requesting System: Any system that wants a community based health worker to find and follow-up with a patient. The requesting system will often be an EMR like OpenMRS
  2. CHIS: A Community Health Information System is an information system that supports the routine and emergency health care of a patient population within community contexts in defined geographic areas.
  3. CHW: Community Health Workers are the central users of CHIS. CHWs conduct household visits and are responsible for the health of their community.
  4. SHR: Shared Health Record is a centralized data repository for storing patient’s shared health record.

...

Flows

...

Workflow Overview

From a very high level perspective, the workflow is designed around having the Requesting System determine which patients need to be followed-up with and a CHW trying to find the patient and recording the outcome of their attempt(s).  

  1. Requesting System → Determine patients needing follow-up
  2. Requesting System → Send list of patients
  3. CHIS → Notify
  4. CHW→ Find patient and record outcome
  5. CHW→ Sync results
  6. CHIS→  Update with outcome of follow-up


Image Modified

...



Data Flow

The flow is centered around the use of the FHIR "ServiceRequest" resource to initiate follow-ups in the community.

  1. Requesting system determines which patients need follow-up
  2. Requesting system creates a ServiceRequest for each patient and sends the ServiceRequest to HIE
  3. CHIS queries the HIE to determine if there are any patients to follow-up with
  4. Requesting system returns results of CHIS' query
  5. CHIS determines where or not to claim the service request
  6. CHIS "claims" the ServiceRequest to confirm that they will be following up with the patient
  7. CHIS tasks the appropriate CHW with finding and advising the patient
  8. CHIS records the results of the CHW's efforts
  9. CHIS updates the ServiceRequest
  10. Requesting system receives update
  11. Requesting system updates itself accordingly


Image Modified


Draft Indicators

...

  1. Count of ServiceRequests Created
  2. Count of ServiceRequests ClaimedCount of ServiceRequests Completed
  3. Count of ServiceRequests Completed with Outcome of X
  4. Count of ServiceRequests Completed with Outcome of Y
  5. Average Time from Created to Claimed
  6. Average Time from Claimed to Completed
  7. Average Time from Created to Completed

...

The proof of concept uses the Instant OpenHIE architecture interacting with multiple CHIS (CommCare, OpenSRP, and CHT).  

The current setup includes the following components.

  1. OpenHIM Admin Console
  2. OpenHIM
  3. HAPI FHIR
  4. CHIS

Detailed technical information about this infrastructure, including servers set up on 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


 



Data Flow Diagram (CHIS Processing Only)

The diagram below illustrates the dataflow between the SHR / FHIR Server and CHISs.

Image RemovedImage Added