Using the Direct Message Integration Error Log
Integration error logs are available to Client Admin at clients that have integrations that transfer data to par8o via the Direct protocol. Each line item indicates a message that reached par8o and whether it successfully created a referral.
If a referral was not created (integration error), an error reason will be noted. Only messages that reach the par8o HISP will display on this queue; if there is an error within the EMR interface, please work with your EMR vendor or IT department directly.
Using the Integration Error Log:
- Click Error Log.
- From the queue, you'll see details such as when the integration message was received and the par8o referral ID or error message. You can also use the filters on the left side of the screen to narrow the referrals in this view.
Example Error Messages (vary by integration)
| could not send Direct referral: Sending profile 1234567890 not in sending master group | The NPI listed on the order is not the client mastergroup. Please update par8o data via the normal method for client group (admin tool or files) to add the provider to par8o. |
| could not send Direct referral: Missing sending profile. npi: 1234567890 | The NPI listed on the order does not exist in par8o. Please update par8o data via the normal method for client group (admin tool or files) to add the provider to par8o. |
| Missing sending profile. npi: none specified | There was no NPI in the expected location within the integration message. |
| could not send Direct referral: Invalid Referral: Client referral identifier Referral XYZ-1234 already exists with client_referral_identifier XXXXXX | Updates were made to the order in the EMR; these updates should not re-create or update the par8o referral associated with the order. This is more of a notification than an error. |