Integration Events Overview
Integration messages can fail for a variety of reasons. We suggest having your internal IT department review the error message and the referral payloads to help determine the issue before involving Novari Health Support. When contacting Novari Health, please include the referral ID and related payload information.
Integration events are part of the referral history to flag to the user that a failure occurred. When an integration message has failed the referral History tab will show a red exclamation mark on the history tab to inform the user of the failure.
Select the History tab to see the failure highlighted in red (as shown above).
The failure provides the following information:
Creation Date: The date/time the integration event occurred
Reference Number: eReferral reference ID number of the referral
Event type: what type of message was sent
Source->Destination: System that initiated the integration event and the system the integration message was sent to
Function Name: The specific function the error occurred on
Error Message: Failure Message (to expand the error message click the )
To the right of the Integration Events section is the Integration Events Reviewed action button. When clicked it will clear the event(s) and removes the exclamation mark from the History tab and the action button will disappear, but the failures remain in red. If you have any dashboard buckets configured to pull back referrals with failures this will remove them from the bucket
EVENT TYPES
Type | Meaning | Applicable Interface |
---|---|---|
notify-update-location | Notify other system of change in referral location | Ocean |
notify-update-status | Notify system of status change on referral | Ocean |
notify-add-appointment | Notify system of appointment being booked | Ocean, EPIC, Cerner, Meditech |
notify-update-appointment | Notify system of update to an existing appointment | Ocean, EPIC, Cerner, Meditech |
notify-update-appointment-noshow | Notify system of appointment no show | EPIC, Cerner, Meditech |
notify-update-appointment-info | Appointment | Ocean, EPIC, Cerner, Meditech |
com.novarihealth.mirm.senddicomrequest | Send DICOM request to PACS system | DICOM for Medical Imaging |
com.novarihealth.mirm.updaterequisitionstatus | Update Requisition status in Novari | Cerner, Meditech |
com.novarihealth.mirm.completeappointment | Complete appointment in Novari | Cerner, Meditech |
com.novarihealth.mirm.addappointment | Add appointment to requisition in Novari | Cerner, Meditech |
com.novarihealth.mirm.sendappointmentnotification | Appointment Notification triggered based on appointment added via integration | Cerner, Meditech |
add-service-request | Referral sent from Novari to | Epic, Cerner, Meditech |
FUNCTION NAME
Type | Meaning | Applicable Interface | Note |
---|---|---|---|
OutboundFhirMessageOrchestrator | Generic function that processes sending messages out to another system | EPIC, Cerner, Meditech | Outbound from Novari to another system |
UpdateTrackedAppointment | Function that handles updating of appointments | EPIC, Cerner, Meditech | Inbound from another system to Novari |
UpdateRequisition | Handles updating the status of the requisition in Novari | EPIC, Cerner, Meditech | Inbound from another system to Novari |
AddTrackedAppointment | Adds the appointment in Novari | EPIC, Cerner, Meditech | Inbound from another system to Novari |
SendDicomFhirPayloadActivity | Makes the DICOM request to the PACS system | DICOM for Medical Imaging | Outbound from Novari to another system |
CompleteTrackedAppointment | Completed the appointment in Novari | EPIC, Cerner, Meditech | Inbound from another system to Novari |
FhirBundleHandlerOrchestrator_SendAppointmentNotificationActivity | Sends out appointment notification | EPIC, Cerner, Meditech | Inbound from another system to Novari |