About FHIR Messaging

overview about FHIR Messaging

This is published as part of general awareness/guidance and is not intended for production use, content is still in draft phase, please have a look at Sehhati roadmap to understand at which phase you can start using the API's!!

Sehhati API platform is built on RESTful API based FHIR messaging standard with version 4.0.1 (R4)

Integration flow

Sehhati will execute callouts for hospitals to find available slots and send appointment request for booking particular slots

Sehhati will use FHIR messaging standard as a communication protocol for enhanced message delivery: https://www.hl7.org/fhir/messaging.html

1. if hospital system is not available Sehhati will execute the below to insure message delivery

   1. Message will be either queued or discarded, find slot message will be discarded and patient will be notified with proper message indicating that target hospital is un reachable.

   2. Confirm slot will be queued with 10 minutes and retried 3 times within the 3 minutes, if no response is received message will be discarded and patient will be notified

2. Hospital can choose to either use pull mechanism or push mechanism , this configuration will be maintained at Sehhati :

   1. if hospital is configured for pull mode , all messages will be queued with proper timeout settings, hospital will execute poll-message request to get different messages that are waiting for processing.

   2. if hospital is configured for push mode , all messages will be tried as push in real time and if external system is not able to process those messages , messages will be retried until message is