Conversations in ShifaTH
Keep messages and next steps connected to the request you sent to a Provider. How messages are seen depends on the communication flow.
A conversation belongs to one Provider relationship
Each submitted Provider-specific request has its own conversation. It connects you with that Provider’s request relationship; contacting several Hospitals creates separate conversations.
Communicate directly inside ShifaTH
In the core direct flow, you and the Provider see each other’s messages inside ShifaTH. Messages are not routinely pre-approved by ShifaTH staff before delivery. Authorized platform audit access can still apply.
When ShifaTH coordinates the communication
Where a coordinated flow is configured, messages from each side are visible to that side and authorized ShifaTH coordinators, rather than directly to the other side. Coordinators read both sides’ messages and write separate messages to the intended recipient. Those messages are clearly identified as coming from the platform.
Translation keeps the original available
Translation may help you read a message in your chosen language. It does not replace what the sender wrote, and you can return to the original. Generated translation can be imperfect; clarify important clinical meaning with the Provider.
Keep contact in the platform
ShifaTH’s request flow keeps communication in-platform. It does not provide private phone, email or messaging-app contact details to bypass that flow. Appointment confirmation does not release those details.