diff --git a/content/en/apps/examples/direct-to-client.md b/content/en/apps/examples/direct-to-client.md
index f5b96e621..42051903a 100644
--- a/content/en/apps/examples/direct-to-client.md
+++ b/content/en/apps/examples/direct-to-client.md
@@ -10,6 +10,15 @@ relatedContent: >
apps/reference/tasks
---
+
+
+
+
{{% pageinfo %}}
This documentation provides a guide for designing and deploying direct-to-client (D2C), two-way texting (2wT) workflows to support client follow-up care using the community health toolkit (CHT). 2wT is a mobile text messaging system built on open-source, CHT tools to engage clients in their health care; to facilitate prompt client - healthcare provider interactions; to provide low-cost telehealth; and, to improve health care outcomes through the early identification of, and referral for, potential complications.
@@ -26,14 +35,13 @@ Recipients of health care in sub-Saharan Africa face significant barriers in ac
The CHT offers general guidance on how SMS workflows can be built on CHT. CHT SMS based workflows can be configured to support D2C / 2wT between health care providers and clients. The D2C / 2wT workflows can be designed to support:
-
-
Regular client check-ins to help keep track of the client's condition
-
Sending of client follow up appointment reminders with confirmation requests
-
Sharing of information and educational health messages with the clients
-
Client tracing and client review tasks can be assigned to specific healthcare workers. Escalated workflows can result in tasks in CHT apps for CHWs, clerks or nurses, depending on need
-
Two-way conversation messaging between healthcare providers and clients
-
2wT-based telehealth, providing a lower cost format for clinical triaging, reassurance or referral to in-person care via SMS
-
+ * **Regular client check-ins** to help keep track of the client's condition
+ * Sending of **client follow up appointment reminders** with confirmation requests
+ * Sharing of **information and educational health messages** with the clients
+ * **Client tracing and client review tasks** can be assigned to specific healthcare workers. Escalated workflows can result in tasks in CHT apps for CHWs, clerks or nurses, depending on need
+ * **Two-way conversation messaging** between healthcare providers and clients
+ * **2wT-based telehealth**, providing a lower cost format for clinical triaging, reassurance or referral to in-person care via SMS
+
Furthermore, CHT allows integration with other health information systems including District Health Information Software 2 (DHIS2) and facility-based electronic medical record systems such as OpenMRS.
@@ -51,7 +59,7 @@ The CHT-RapidPro integration enables App builders to build complex conversationa
Clients are enrolled directly using the CHT D2C, 2wT app using a phone, tablet or computer. Clients need only simple phones and do not need to download an app. The resulting client data is then stored and managed using CouchDB and a PostgreSQL database system. Through the CHT application programming interface (API), client messages are sent to Rapidpro, and RapidPro pushes summary data back to the CHT to update client responses and status. On the client interface these can be automated messages or interactive free text with healthcare providers. An SMS text message aggregator service and a short code channel linked to RapidPro streamlines the incoming and outgoing SMS text messages; while the CHT generates the appropriate tasks (help clinicians triage, refer, track, and trace clients)and reports (keep track of completed actions and monitor clients) as represented in figure 1.
-{{< figure src="Figure1SystemArchitecture.jpg" link="Figure1SystemArchitecture.jpg" alt="Direct Messaging technical architecture" title="" caption="Figure 1: System architecture of direct-to-client (D2C), two-way texting (2wT) for voluntary medical male circumcision (VMMC) postoperative care. API: application programming interface; CHT: Community Health Toolkit." class="left col-10">}}
+{{< figure src="Figure1SystemArchitecture.jpg" link="Figure1SystemArchitecture.jpg" alt="Direct Messaging technical architecture" title="" caption="**Figure 1:** System architecture of direct-to-client (D2C), two-way texting (2wT) for voluntary medical male circumcision (VMMC) postoperative care. API: application programming interface; CHT: Community Health Toolkit." class="left col-10">}}
The CHT core framework has inbuilt [privacy/security features](https://docs.communityhealthtoolkit.org/apps/guides/privacy/) including two- factor authentication, role based authorization, data security, and a range of protected data access endpoints. The system can be configured to manage [user roles and permissions](https://docs.communityhealthtoolkit.org/apps/concepts/users/) for access of CHT applications. Responsible data practices is enforced through the [Privacy and Data Protection Policy](https://docs.communityhealthtoolkit.org/apps/guides/privacy/policy/).
@@ -70,13 +78,13 @@ The University of Washington, Department of Global Health’s International Trai
|Site nurse|Health facility or outreach site|Smartphone|Users are routine MC nurses at health facilities or outreach sites who enroll D2C clients and interact with clients enrolled at their site via the CHT D2C messaging app. In higher volume facilities, data clerks may also be involved in data entry of client enrolment details.|
|VMMC Clients|Community / household level|Smartphone / feature phone|VMMC clients with access to mobile devices and who have consented to participate in and have been enrolled into the D2C, 2wT app. They will receive daily check in messages and can communicate with their health care providers via text.|
-Figure 2: User types and hierarchy
-
### Workflows
-Current workflow for VMMC client enrollment, screening and VMMC procedures (without messaging) are as described in figure 3 below.
-
-{{< figure src="Figure3Workflows.png" link="Figure3Workflows.png" alt="Users and hierarchy example" title="" caption="Figure 3: Voluntary male circumcision workflow before direct-to-client messaging was introduced" class="col-9">}}
+Current workflow for voluntary medical male circumcision client enrollment, screening and procedures, before direct-to-client messaging was introduced:
+| {{< figure src="Figure3_1.png" >}} | {{< figure src="Figure3_2.png" >}} | {{< figure src="Figure3_3.png">}} | {{< figure src="Figure3_1.png" >}} | {{< figure src="Figure3_4.png" >}} |
+|--|--|--|--|--|
+| **1.** Enrolment - Static/Outreach Site visit | **2.** HIV Testing, screening & counseling | **3.** Procedure | **4.** Static/Outreach Site visit | **5.** Follow up visit |
+| Nurse enrols clients | Client tested for HIV, screened for wounds, any form of bleeding, and any other medical issues. Counselling provided as needed.| If client's HIV status doesn't pose risks, procedure is done. Post-operative counseling offered | Register after surgery | On Day 2 and Day 7 after surgery |
#### 1. Automated check-in workflow to support client care
@@ -86,14 +94,28 @@ After the registration, the VMMC clients registered on the VMMC app receive prec
An adverse event (AE) is any complication or problem that may happen during or after a surgery, including a VMMC surgery. AEs may be mild, moderate or severe. All moderate and severe AEs should be reviewed by a clinician. Moderate and severe AEs after VMMC are rare, but occur about 2% of the time. . Identifying AEs swiftly and managing them properly is a sign of a quality surgical program, including VMMC programs.
+Direct to client messaging for voluntary male circumcision clients without AE:
+
+|{{< figure src="Figure4_1.png" >}} | {{< figure src="Figure4_2.png" >}} | {{< figure src="Figure4_3.png">}}|
+|--|--|--|
+| **Enrolment** | **Automated, daily check-in SMS** | **{{No Action}}** |
+| **1a** Static/Outreach Site visit Data Clerk/Site Nurse enrolls eligible clients into the D2C program using the enrollment form|**2** System sends automated daily SMS to client to see how they are doing. |**3** SMS response AE absent |
+|**1b** Registration and SMS confirmation Client gets a confirmation of enrollment Via SMS|**2a** Client SMS response with potential AE present | Continue automated daily check-in SMS until day 13 |
+||**2b** Client SMS response AE absent | |
-{{< figure src="Figure4PatientAutomated.png" link="Figure4PatientAutomated.png" alt="Patient automated check-in SMS workflows" title="" caption="Figure 4: Direct to client messaging for voluntary male circumcision clients without adverse effects" class="col-9">}}
#### 2. Triaging to care workflow for clients with potential complications
-Clients with potential AEs (those who respond with 1 or a free text indicating concerns) are followed up by nurses and given care via the D2C, 2wT intervention. Clients may be followed up via SMS / call. Nurses provide education and reassurance, or refer in cases where they need to go to a health facility for in-person review if an emergency was suspected (Figure 5). The clients could request a call back to speak with the nurse during routine clinic hours; the nurse could also initiate calls to follow up with clients when desired.
+Clients with potential AEs (those who respond with 1 or a free text indicating concerns) are followed up by nurses and given care via the D2C, 2wT intervention. Clients may be followed up via SMS / call. Nurses provide education and reassurance, or refer in cases where they need to go to a health facility for in-person review if an emergency was suspected. The clients could request a call back to speak with the nurse during routine clinic hours; the nurse could also initiate calls to follow up with clients when desired.
+
+Direct-to-client messaging for voluntary male circumcision clients without AEs:
-{{< figure src="Figure5Triage.png" link="Figure5Triage.png" alt="" title="" caption="Figure 5: Direct-to-client messaging for voluntary male circumcision clients without adverse effects" class="col-9">}}
+|{{< figure src="Figure4_1.png" >}} | {{< figure src="Figure4_2.png" >}} | {{< figure src="Figure5Triage3.png">}} | {{< figure src="Figure5Triage4.png">}}|
+|--|--|--|--|
+| **Enrolment** | **Automated, daily check-in SMS** | **Referral for care task** | **Client review visit** |
+|**1a** Static/Outreach Site visit. Data Clerk/Site Nurse enrolls eligible VMMC clients into the D2C, 2wT program using the enrollment form |**2** Check in SMS of Wellbeing. System sends automated daily SMS to client to see how they are doing.|**3** 2wT/HUB Nurse triages patient, provides guidance.2wT/HUB Nurse triages patient, provides guidance.2wT/HUB Nurse triages patient, provides guidance.|**4** When the client comes to the health facility after a referral, the clinicians (nurses or clinical associates) at site level use the Client in-person visit form to complete the details of the review|
+|**1b** Registration and SMS confirmation. Client gets a confirmation of enrollment Via SMS|**2a** Client SMS response with potential AE present|**3a** If nurse and client satisfied, no further response.|If client just comes into the clinic, the site Nurse completes the Client in-person visit form to complete the details of the review|
+||**2b** Client SMS response AE absent|**3b** If nurse thinks client may have AE referral for care task is cleared by completing the Referral for Care form, calling site nurse to alert of referral. and the client is informed via call or message||
#### 3. Escalated workflow to generate tasks when clients do not respond
@@ -101,17 +123,40 @@ If the client has not responded to any of the daily check in-messages by day 3,
A VMMC client who responds with a potential complication triggers a Client review: Potential complication task for the 2WT nurse. They then report and fill in whether the client was reviewed by a clinician. If the client has been reviewed by a clinician, they record the details of the review, time, place and adverse events identified. If the client has not been reviewed by a clinician, the 2WT nurse will try and trace them by SMS, phone call or a home visit; and report the tracing outcomes as shown in figure 6 below.
+Direct-to-client messaging for voluntary male circumcision clients without adverse effects:
-{{< figure src="Figure6Escalted.png" link="Figure6Escalted.png" alt="" title="" caption="Figure 6: Direct-to-client messaging for voluntary male circumcision clients without adverse effects" class="col-9">}}
+|{{< figure src="Figure4_1.png" >}} | {{< figure src="Figure4_2.png" >}} | {{< figure src="Figure5Triage3.png">}} | {{< figure src="Figure5Triage4.png">}} |
+|--|--|--|--|
+| **Enrolment** | **Automated, daily check-in SMS** | **Tracing follow up task** | **Client review visit** |
+|**1a** Static/Outreach Site visit Data Clerk/Site Nurse enrols eligible VMMC clients into the D2C, 2wT program using the enrolment form |**2** Check in SMS of Wellbeing System sends automated daily SMS to client to see how they are doing.|**3a** No client response by day 3= additional check-in SMS at noon |**4** When the client comes to the health facility after a referral, the clinicians (nurses or clinical associates) at site level use the Client in-person visit form to complete the details of the review|
+**1b** Registration and SMS confirmation Client gets a confirmation of enrollment Via SMS|**2a** Client SMS response with potential AE present |**3b** No client response by day 4. Trace Client task is generated 2wT/HUB Nurse initiates the tracing activity. - Client traced and no concern; no action - Client traced & AE referral follow up task - Client reviewed complete review form - No response at all Notes in tracing report|If client just comes into the clinic, the site Nurse completes the Client in-person visit form to complete the details of the review|
+||**2b** Client SMS response AE absent |**3c** 2wT/HUB Nurse triages patient, provides guidance. If nurse and client satisfied, no further response. If nurse thinks client may have AE referral for care task is cleared by completing the Referral for Care form, calling site nurse to alert of referral, and the client is informed via call or message | |
#### 4. Clients can share requests by messaging health care providers.
Clients registered in the intervention can also initiate the bidirectional messaging with a 2WT Nurse by messaging a central phone number or a short code. Clients can report any concern, ask a question about wound healing, or request for help from health care providers via SMS. For this workflow, the logic can be preconfigured to support health triage and clinical referrals. Using the messaging functionality on CHT, health care providers based at the facility can view, manage and respond to incoming texts from VMMC clients.
## Evidence of Impact
-In collaboration with researchers at the University of Washington, we assessed the effectiveness of the 2wT intervention through randomized controlled trials in Zimbabwe and South Africa. The foundational [randomized control trial in Zimbabwe in 2018](https://trialsjournal.biomedcentral.com/articles/10.1186/s13063-019-3470-9), demonstrated that post-surgical client follow up via SMS was as safe as follow up care at the clinic, and that the transition to SMS-based follow-up option enabled an 85% reduction in unnecessary clinic visits. Similar findings were reported in [South Africa](https://www.jmir.org/2023/1/e42111/). This approach to messaging with clients was more efficient and [cheaper](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0239915) than standard care, thereby lowering costs. Both clients and clinicians both found the approach to be [highly usable](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0233234) and [acceptable for post-operative care](https://journals.sagepub.com/doi/full/10.1177/20552076231194924) and further [usability studies](https://formative.jmir.org/2023/1/e44122) found that it was preferred by clients and providers alike (see figure 7). We are also expanding our application of D2C, 2wT for antiretroviral therapy (ART) clients in Malawi, aiming to have similarly [positive impact on engagement in ART and retention in HIV care](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0278806).
+In collaboration with researchers at the University of Washington, we assessed the effectiveness of the 2wT intervention through randomized controlled trials in Zimbabwe and South Africa. The foundational [randomized control trial in Zimbabwe in 2018](https://trialsjournal.biomedcentral.com/articles/10.1186/s13063-019-3470-9), demonstrated that post-surgical client follow up via SMS was as safe as follow up care at the clinic, and that the transition to SMS-based follow-up option enabled an 85% reduction in unnecessary clinic visits. Similar findings were reported in [South Africa](https://www.jmir.org/2023/1/e42111/). This approach to messaging with clients was more efficient and [cheaper](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0239915) than standard care, thereby lowering costs. Both clients and clinicians both found the approach to be [highly usable](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0233234) and [acceptable for post-operative care](https://journals.sagepub.com/doi/full/10.1177/20552076231194924) and further [usability studies](https://formative.jmir.org/2023/1/e44122) found that it was preferred by clients and providers alike (see "Benefits" below). We are also expanding our application of D2C, 2wT for antiretroviral therapy (ART) clients in Malawi, aiming to have similarly [positive impact on engagement in ART and retention in HIV care](https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0278806).
+
+### Benefits
+
+#### For Clients
+
+* Reduced cost of follow-up
+* Comfort and ease of usability of 2WT
+* Real-time clinical support in your pocket
+* Rapid support in case of suspected AE
+
+#### Of Participation
+
+* Increase demand/interest from men who would opt for MMC but not for the follow-up visits
+* Early identification of AE's
+* Ability to scale based on organizational needs
+* Less clinical time spend on unnecessary followup-visits
+* Publications
+* Great focus/time on incoming clients for MMC
-{{< figure src="Figure7EvidenceOfImpact.png" link="Figure7EvidenceOfImpact.png" alt="" title="" caption="Figure 7: Evidence supported benefits of direct-to-client messaging for voluntary male circumcision clients" class="col-9">}}
## More scenarios where direct-to-client messaging can be used to support client care
@@ -146,8 +191,8 @@ VMMC code can be accessed using the following link [D2C messaging app for post-o
- 2wT is scale up, reaching over 45,000 in [Zimbabwe](https://journals.plos.org/digitalhealth/article?id=10.1371/journal.pdig.0000066)
-Related pages - [UW website](https://sites.uw.edu/twowaytexting/), [I-tech/Aurum page](https://globalhealth.washington.edu/news/2020/07/02/expanding-two-way-texting-reduce-follow-appointments-male-circumcision-patients)
+**Related pages** - [UW website](https://sites.uw.edu/twowaytexting/), [I-tech/Aurum page](https://globalhealth.washington.edu/news/2020/07/02/expanding-two-way-texting-reduce-follow-appointments-male-circumcision-patients)
{{< figure src="Figure8Collab.png" link="Figure8Collab.png" alt="" title="" class="col-9">}}
-Funding: 2wT Zimbabwe was supported by the Fogarty International Center of the National Institutes of Health under Award Number R21TW010583, PI Feldacker. 2wT South Africa is supported by National Institute of Nursing Research of the National Institutes of Health (NIH) under award number 5R01NR019229, PIs Feldacker and Setswe. The content is solely the responsibility of the collaborators and authors and does not necessarily represent the official views of the National Institutes of Health.
+**Funding:** 2wT Zimbabwe was supported by the Fogarty International Center of the National Institutes of Health under Award Number R21TW010583, PI Feldacker. 2wT South Africa is supported by National Institute of Nursing Research of the National Institutes of Health (NIH) under award number 5R01NR019229, PIs Feldacker and Setswe. The content is solely the responsibility of the collaborators and authors and does not necessarily represent the official views of the National Institutes of Health.
diff --git a/content/en/apps/examples/direct-to-client/Figure3Workflows.png b/content/en/apps/examples/direct-to-client/Figure3Workflows.png
deleted file mode 100644
index a53607192..000000000
Binary files a/content/en/apps/examples/direct-to-client/Figure3Workflows.png and /dev/null differ
diff --git a/content/en/apps/examples/direct-to-client/Figure3_1.png b/content/en/apps/examples/direct-to-client/Figure3_1.png
new file mode 100644
index 000000000..019e3681a
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure3_1.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure3_2.png b/content/en/apps/examples/direct-to-client/Figure3_2.png
new file mode 100644
index 000000000..602c0f4a0
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure3_2.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure3_3.png b/content/en/apps/examples/direct-to-client/Figure3_3.png
new file mode 100644
index 000000000..aedcc3ead
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure3_3.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure3_4.png b/content/en/apps/examples/direct-to-client/Figure3_4.png
new file mode 100644
index 000000000..3805049fc
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure3_4.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure4PatientAutomated.png b/content/en/apps/examples/direct-to-client/Figure4PatientAutomated.png
deleted file mode 100644
index 822c74682..000000000
Binary files a/content/en/apps/examples/direct-to-client/Figure4PatientAutomated.png and /dev/null differ
diff --git a/content/en/apps/examples/direct-to-client/Figure4_1.png b/content/en/apps/examples/direct-to-client/Figure4_1.png
new file mode 100644
index 000000000..e658a57e2
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure4_1.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure4_2.png b/content/en/apps/examples/direct-to-client/Figure4_2.png
new file mode 100644
index 000000000..d02d67b50
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure4_2.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure4_3.png b/content/en/apps/examples/direct-to-client/Figure4_3.png
new file mode 100644
index 000000000..452324fc7
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure4_3.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure5Triage2.png b/content/en/apps/examples/direct-to-client/Figure5Triage2.png
new file mode 100644
index 000000000..86ac1618c
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure5Triage2.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure5Triage3.png b/content/en/apps/examples/direct-to-client/Figure5Triage3.png
new file mode 100644
index 000000000..0aa12fe2b
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure5Triage3.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure5Triage4.png b/content/en/apps/examples/direct-to-client/Figure5Triage4.png
new file mode 100644
index 000000000..9ca1b3cc5
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure5Triage4.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6Escalted.png b/content/en/apps/examples/direct-to-client/Figure6Escalted.png
deleted file mode 100644
index 21ef324f5..000000000
Binary files a/content/en/apps/examples/direct-to-client/Figure6Escalted.png and /dev/null differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6_1.png b/content/en/apps/examples/direct-to-client/Figure6_1.png
new file mode 100644
index 000000000..c958d1b6c
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure6_1.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6_2.png b/content/en/apps/examples/direct-to-client/Figure6_2.png
new file mode 100644
index 000000000..97ea54070
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure6_2.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6_3.png b/content/en/apps/examples/direct-to-client/Figure6_3.png
new file mode 100644
index 000000000..25e4aa763
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure6_3.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6_4.png b/content/en/apps/examples/direct-to-client/Figure6_4.png
new file mode 100644
index 000000000..96a05624f
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure6_4.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure6_5.png b/content/en/apps/examples/direct-to-client/Figure6_5.png
new file mode 100644
index 000000000..1e43a4e0c
Binary files /dev/null and b/content/en/apps/examples/direct-to-client/Figure6_5.png differ
diff --git a/content/en/apps/examples/direct-to-client/Figure7EvidenceOfImpact.png b/content/en/apps/examples/direct-to-client/Figure7EvidenceOfImpact.png
deleted file mode 100644
index 38d97d91f..000000000
Binary files a/content/en/apps/examples/direct-to-client/Figure7EvidenceOfImpact.png and /dev/null differ
diff --git a/content/en/apps/examples/direct-to-client/main.inkscape.svg b/content/en/apps/examples/direct-to-client/main.inkscape.svg
new file mode 100644
index 000000000..6c8678f75
--- /dev/null
+++ b/content/en/apps/examples/direct-to-client/main.inkscape.svg
@@ -0,0 +1,224 @@
+
+
+
+