Facesheet Transmission Errors

The following errors may be received when clicking the Send to Kipu RCM button on the patient facesheet. These errors appear at the top of the Information tab and indicate the patient details were not successfully sent to the RCM.

Error Message	Resolution
Patient's State (PID.11.4) is missing or invalid:	This error occurs when the state is missing from the patient's address. To resolve, edit the patient’s facesheet and update the patient's state under Patient Information then click Send to Kipu RCM.
ICD9 code \"305.5\" is invalid.	This occurs when an ICD-9 diagnosis code is sent instead of an ICD-10 diagnosis code. The diagnosis code should be updated on the patient’s facesheet to an ICD-10 code then click Send to Kipu RCM.
Cannot insert duplicate key row in object 'dbo.Patients' with unique index 'UIX_Patients_KipuID'. The duplicate key value is (xxxxxxx-xxx-xxxx-xxxx-xxxxxxxx).	Please contact Support for assistance in resolving this issue.
An Admitted/Prospective Patient with the name \"LastName, FirstName\" already exists	This error occurs when a patient with the same first name, last name, and date of birth already exists in the Kipu RCM. Because the patient already exists in the EMR and the RCM, please search the EMR or the RCM to locate the previously created patient record and use that existing record.
Cannot insert duplicate key row in object 'dbo.TreatmentEpisodes' with unique index 'UIX_TreatmentEpisodes_PracticeID_KipuID'. The duplicate key value is (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx, xxxx).	Please contact Support for assistance in resolving this issue.
Missing admit date.	The admit date or anticipated admit date is missing from the patient's facesheet. Ensure that either an admit date or anticipated admit date has been added for the patient. Once added, click Send to Kipu RCM.
The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.	Someone has entered a date that is very far in the past (ex: entering 0202 instead of 2002) This could be for the Admission Date or Date of Birth. To resolve, enter a valid date.  Note: If the Insurance Effective Date is invalid, please contact Support for assistance.
You do not have access to this record.	This error occurs when the API user added to the Kipu RCM Konnector doesn't have access to the RCM.  This can occur for two reasons: The password on the konnector is incorrect: In this instance, please reset the password for the API user in the RCM, then update the Password field in the Konnector.  The API user wasn't configured correctly in Avea: Please contact Support for assistance.
Cannot create a Treatment Episode for a patient without a specified Birthday	An admitted patient was sent to the RCM without a birthday. To resolve, update the patient’s facesheet with the date of birth and then click Send to Kipu RCM.
Object reference not set to an instance of an object.	Please contact Support for assistance in resolving this issue.
Another user has modified this record. Please try again.	This occurs when a user is editing a patient in RCM at the same time the ADT is being sent. To resolve, try clicking Send to Kipu RCM again.
Patient must be discharged from the previous Treatment Episode before creating a new episode	In the RCM, you cannot have two concurrent treatment episodes for a patient at the same practice at the same time. The patient needs to be discharged from the previous treatment episode before the new one can be created.
Invalid Authorization Header	This error occurs when the username and password on the RCM Konnector is invalid (meaning it doesn't match the RCM user details). To resolve, locate the RCM Konnector associated with the patient and re-enter the username and password.
Exception Error: undefined method 'parsed_response' for nil:NilClass.	The EMR was unable to connect to the RCM. Please contact Support for assistance in resolving this issue.