Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Direct to patient #791

Closed
wants to merge 12 commits into from
Closed

Direct to patient #791

wants to merge 12 commits into from

Conversation

nsitaula
Copy link
Contributor

Could you please review direct-to-patient workflow documentation? which is in:
cht-docs-> content -> en -> apps -> examples

Copy link
Contributor

@mrjones-plip mrjones-plip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really good work here!

I went through and made some requests per our meeting with @abbyad along the lines of:

  • redo screenshots to be current
  • remove ghost background with light "rectangular snip" text
  • fix any images that are tables with text to be native markdown tables

content/en/apps/examples/direct-to-patient.md Outdated Show resolved Hide resolved

### Users and hierarchy example

{{< figure src="user_hierarchy.png" link="user_hierarchy.png" alt="Users and hierarchy example" title="" class="left col-9">}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use native HTML when ever possible instead of images. This will both improve legibility on mobile devices, but also make the content searchable.

Here's a start on how to make a table for this:

| Users | Location | Devices | Role |
|-------|----------|---------|------|
| **SUPER NURSE** | Admin Level | Laptop or desktop  | Users who log in at the Admin level have access to all sites in a Distric. They can access many  sites via the CHT WebApp.... |


Eligible male clients with access to phones are registered on CHT to enable them receive daily check-in texts to help track the condition of the clients for 13 days after the circumcision. After the registration, the VMMC clients receive a registration text message confirming that they have enrolled in the text messaging follow up intervention. It is also possible for two household members belonging to the same household to be registered on CHT to be receiving texts using the same phone number.
Clients registered on CHT receive preconfigured bidirectional daily follow up texts to check on their condition and clients respond to the check in texts by informing the Site Nurse whether they are experiencing any potential adverse effects. Clients who report potential adverse effects are followed up by facility Nurses and guided or referred to a health facility to be able to receive further care.
{{< figure src="automated_check_in.png" link="automated_check_in.png" alt="Patient automated check-in SMS workflows" title="" class="col-9">}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be a stretch, but let's see if we can use native HTML with images in a table. Mocking this up with something like this:

##### Patient automated check-in SMS workflows

| ![Enrollment](img.png) | ![SMS Check-in](img_1.png) | ![Referral](img_2.png) | ![Follow up](img_3.png) |
|-------|----------|---------|------|
| **1A** Enrollment form - Site nurse enrolls eligible VMMC clients in CHT using the enrollment form. | TK | TK  | TK|

I can get maybe close enough? Notice how hard to read the image based on is above it as compared to the native HTML one:

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, please use the correct patient icon (see here) or reach out to @n-orlowski for help. the patient icon used here is blurry.


{{% pageinfo %}}

This documentation provides a guide for designing and deploying direct-to-patient messaging workflows to support patient care using CHT. It can serve as a great way to learn how to integrate CHT’s with technologies like [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) and SMS aggregators to build direct-to-patient workflows.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor suggestions:

Suggested change
This documentation provides a guide for designing and deploying direct-to-patient messaging workflows to support patient care using CHT. It can serve as a great way to learn how to integrate CHT’s with technologies like [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) and SMS aggregators to build direct-to-patient workflows.
This documentation provides a guide for designing and deploying direct-to-patient messaging workflows to support patient care using the CHT. It can serve as an example for learning to integrate CHT apps with messaging apps, like [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/), and SMS aggregators to build direct-to-patient workflows.

Comment on lines 90 to 93
## Resources

- [RapidPro Messaging Gateway]({{< ref "apps/guides/messaging/gateways/rapidpro" >}})
- [Africa’s Talking SMS Aggregator]({{< ref "apps/guides/messaging/gateways/africas-talking" >}})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These should be added instead as related content at the top of the page.


## Frequently Asked Questions
##### 1. Is the patient charged for receiving or sending the SMS?
It is possible for health programs to acquire a zero rated short code service which is free for patients and household members to send and receive texts from the short code.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
It is possible for health programs to acquire a zero rated short code service which is free for patients and household members to send and receive texts from the short code.
It is possible for health programs to acquire a zero-rated short code service which is free for patients and household members to send and receive texts from the short code.

weight:
description: >
Reference for Direct-to-patient workflows with CHT and RapidPro
relatedContent: >
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add an alias for direct-to-client since these are used somewhat interchangeably, and we will want to include direct-to-client term in this page as well.

@garethbowen
Copy link
Member

@nsitaula Please make the requested changes and let's get this merged!

@nsitaula
Copy link
Contributor Author

@nsitaula Please make the requested changes and let's get this merged!

Hi @garethbowen, sorry for late response. @antonykhaemba is working with Caryl on other pending changes and approval for direct-to-patient documentation.

@mrjones-plip
Copy link
Contributor

@nsitaula - I think we can close this PR and not merge it as we did the work elsewhere, correct?

@nsitaula
Copy link
Contributor Author

nsitaula commented Apr 3, 2023

@mrjones-plip sorry for the confusion, we are still working on it and this is still not merged and is in progress. @antonykhaemba has been following up with the team for the documentation changes.

@garethbowen
Copy link
Member

@nsitaula Can we merge this now?

@antonykhaemba
Copy link
Member

@garethbowen, we are finalizing working on the documentation with @EvelynWaweru and @BeaWasunna-zz and we should be able to merge this in the next two weeks.

* Update direct-to-patient.md

* Add files via upload

* Delete content/en/apps/examples/direct-to-patient/CheckinPrototype.gif

* Delete content/en/apps/examples/direct-to-patient/CheckinWorkflow.png

* Delete content/en/apps/examples/direct-to-patient/VMMC_follow_up.png

* Delete content/en/apps/examples/direct-to-patient/activeCases.gif

* Delete content/en/apps/examples/direct-to-patient/aptReminderWorkflow.png

* Delete content/en/apps/examples/direct-to-patient/user_hierarchy.png

* Delete content/en/apps/examples/direct-to-patient/sharingTip.png

* Delete content/en/apps/examples/direct-to-patient/sharingTip.gif

* Delete content/en/apps/examples/direct-to-patient/automated_check_in.png

* Delete content/en/apps/examples/direct-to-patient/pneumococcal.png

* Delete content/en/apps/examples/direct-to-patient/taskDemo.png

* Delete content/en/apps/examples/direct-to-patient/technicalArchitecture.jpg

* Delete content/en/apps/examples/direct-to-patient/technicalArchitecture.png
Copy link
Member

@garethbowen garethbowen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent work! A few changes inline.

Also the text in the images is way too small to read.

Approving to unblock. Let's get this merged and iterate over improvements as we go!

The CHT also allows integration with health information systems (District Health Information Software 2) and facility-based electronic medical record systems such as OpenMRS.

## CHT SMS workflow technical overview
The SMS workflows in CHT can integrate with [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) flows to support two way interactive messaging between healthcare providers and household members. RapidPro is an open source tool that has the capability to support conversational messaging flows via SMS, Interactive Voice Response (IVR), Telegram, Facebook Messenger and WhatsApp. With the CHT-RapidPro integration, it is possible to design and configure SMS workflows in the two systems. Data is shared between CHT and Rapidpro via the APIs; and the information from the interactive texting is used to update clients details on CHT through CouchDB which can trigger tasks on CHT.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ref for internal links, eg:

Suggested change
The SMS workflows in CHT can integrate with [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) flows to support two way interactive messaging between healthcare providers and household members. RapidPro is an open source tool that has the capability to support conversational messaging flows via SMS, Interactive Voice Response (IVR), Telegram, Facebook Messenger and WhatsApp. With the CHT-RapidPro integration, it is possible to design and configure SMS workflows in the two systems. Data is shared between CHT and Rapidpro via the APIs; and the information from the interactive texting is used to update clients details on CHT through CouchDB which can trigger tasks on CHT.
The SMS workflows in CHT can integrate with [RapidPro]({{< ref "apps/features/integrations/rapidpro" >}}) flows to support two way interactive messaging between healthcare providers and household members. RapidPro is an open source tool that has the capability to support conversational messaging flows via SMS, Interactive Voice Response (IVR), Telegram, Facebook Messenger and WhatsApp. With the CHT-RapidPro integration, it is possible to design and configure SMS workflows in the two systems. Data is shared between CHT and Rapidpro via the APIs; and the information from the interactive texting is used to update clients details on CHT through CouchDB which can trigger tasks on CHT.


{{% pageinfo %}}

This documentation provides a guide for designing and deploying direct-to-client, two-way texting workflows to support patient care using the community health toolkit (CHT). Direct-to-client (D2C) messaging documentation, like that used for two-way texting (2wT) between clients and their clinicians or other healthcare workers, can serve as a great way for digital health implementers to learn how direct-to-client communication can be achieved through integrating app features within CHT with messaging technologies like [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) and SMS aggregators.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use ref for internal links:

Suggested change
This documentation provides a guide for designing and deploying direct-to-client, two-way texting workflows to support patient care using the community health toolkit (CHT). Direct-to-client (D2C) messaging documentation, like that used for two-way texting (2wT) between clients and their clinicians or other healthcare workers, can serve as a great way for digital health implementers to learn how direct-to-client communication can be achieved through integrating app features within CHT with messaging technologies like [RapidPro](https://docs.communityhealthtoolkit.org/apps/features/integrations/rapidpro/) and SMS aggregators.
This documentation provides a guide for designing and deploying direct-to-client, two-way texting workflows to support patient care using the community health toolkit (CHT). Direct-to-client (D2C) messaging documentation, like that used for two-way texting (2wT) between clients and their clinicians or other healthcare workers, can serve as a great way for digital health implementers to learn how direct-to-client communication can be achieved through integrating app features within CHT with messaging technologies like [RapidPro]({{< ref "apps/features/integrations/rapidpro" >}}) and SMS aggregators.

- Trainer of trainers slide deck
- Flip Books (updated to include WhatsApp)

##### Illustrative [Videos](https://drive.google.com/drive/folders/1AKsjdhJD3-3nXAqKTzakGAyZS9itnsk2?usp=sharing)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These videos are not publicly accessible. Either upload them to the Medic youtube channel or remove this section altogether.

@garethbowen
Copy link
Member

@nsitaula Can you please look at merging this?

Copy link

@EvelynWaweru EvelynWaweru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nsitaula I have reviewed the documentation, and approve release.

@nsitaula nsitaula requested review from mrjones-plip and removed request for antonykhaemba and mrjones-plip March 7, 2024 11:46
@nsitaula nsitaula assigned nsitaula and unassigned nsitaula Mar 7, 2024
@nsitaula
Copy link
Contributor Author

nsitaula commented Apr 26, 2024

closing this since we already have other branch and these changes are out of date. Most recent one is here.

@nsitaula nsitaula closed this Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants