What Dependencies Does Message Assist Rely on?
The following lists focus on the messaging functionality of Message Assist. Addtional endpoints are brought in as Smart Assist dependencies.
Authentication
Message Assist authenticates with a user's electronic medical record using Praia Identity Service
Private Epic APIs
Message Assist uses follow following private Epic APIs:
| Endpoint |
Usage |
| get-medical-advice-recipients |
Understand what providers and pools an authenticated user can message and providers information about the health system's supported attachment types and file size limitations |
| send-message (2013) |
This API can be used to send messages to providers' inboxes, however use of a Custom Send Message API is recomended over this endpoint. |
FHIR APIs
| Endpoint |
Usage |
| api/FHIR/STU3/Practitioner |
(non-critical path) allow translation of users' medical advice recipient information to an NPI that can be used tocde fetch provider images, specialy, date of last appointment, etc to provide additional context to the user on who they are selcecting to message |
Additional APIs
| Service Provider |
Endpoint |
Usage |
| Kyruus |
pm/v8/phs/providers |
(non-critical path) Fetch providers' image to enhance user's messaging experience |
Custom Send Message API Development
| Service Provider |
Endpoint |
Usage |
| Implemented with Customer |
send-message |
Offer a superior send message experience over the existing epic send-message api. Read more about the Custom Send Message API |