...

Summary

This use case allows clinics other systems to make requests to a CHIS to follow-up for various reasonsany reason.  A common implementation might be for Lost to Follow-Up whereby the a clinic generates a list of patients that have missed appointments and wants community based systems to help find the patient and encourage them to attend their appointment or to understand why they cannot or will not. This might be achieved either by having a health worker physically go find the patient or by other communication protocols (SMS, for example). 

High Level Workflow

See diagram below.  From a high level, the steps can be summarized as:

1. Clinic based Requesting system system determines which patients to need follow-up with
2. Requesting system creates Clinic based 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 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. Clinic based Requesting system receives update
11. Requesting system updates itself accordingly

Image Added→ Insert Diagram ← 

Draft Indicators

Based on the high level workflow mentioned above, the list of transactional indicators are below:

...