-
Notifications
You must be signed in to change notification settings - Fork 85
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
When all participants leave the call, the patient isn't removed from the waiting queue #98
Comments
yeah we discussed this but not sure for full implementation, notes from slack:
the solution probably will be browser specific as well. |
I'll attempt to summarize the problem: Something that might be worth looking into is server side notifications from twilio: They allow HTTP callbacks to our API to notify us of actions happening in the application. It seems possible that we could update the encounter based on this information. @SamirOmarov @OmarZubaidi what do you think of this? Any alternative solutions / feedback for this before we bring it to the ZapEHR team? |
FWIW it is definitely a long term goal of this service to have Zap listen to status callbacks and other webhooks and automatically document details in the Encounter. Your frontend would probably have to poll the state of the Encounter to glean details from that I guess. Not really ideal? |
Our FE already polls for the state of the Encounter |
Moving out of MVP due to high LOE |
See #95 AR point 3
The text was updated successfully, but these errors were encountered: