ADT and Employee Integration Error Emails

This article contains commons ADT and Employee Integration error emails that are received by the development team and steps to resolve the issues described.

ADT Emails

Subject: <Community Name> - unable to process data. id=<id>
Body: Error Message: Adding <Resident> to account number <Account Number> of plan <Plan> starting on <Date> would result in double coverage. The customer has not been added to the account..
Please see application logs for more details.

• This indicates a conflict in the dates on plans getting assigned. Most of the time it is one of the following:
• Overlap in dates between admissions. Change the end date on the existing plan and run again.
• Overlap in logic for the plans. This is typically an unmapped plan already assigned to a resident being in conflict with what the system thinks they should have. In this case, the mapping should be updated or in some cases, the message can be ignored.

Subject: Error Processing integration-pcc
Body: Failed to process Event
PCCEvent [id=<id>, processed=E]
HttpStatus.400
Exception thrown during patient request.
{"errors":[{"id":"6ad80a19-2e7c-4710-8425-b7925b4da210","status":"400","code":"32","title":"Bad Request.","detail":"Error reading 'patientId', Failed to convert value 'Y' to required type 'int'."}]

null
Please see application logs for more details.

• This is an error on the PCC side. If it's persistent, investigate. Otherwise, feel free to ignore these as it's an issue with data on the PCC side.

Subject: Failed to process Event
Body: PCCEvent [id=3594150, processed=E]
Failed to create row for patient [19177232]. Leaving event [3594150] as unprocessed. Cause: unknown communityMapping for orgUuid: 71C06113-BFF5-4806-9900-327059C42BA9, facilityId: 81]
Please see application logs for more details.

• This for a new community that has not yet been mapped. This community needs to be added in pcc_integration_obj_owner.community_map.

Subject: <Community Name> - unable to process data. id=<id>
Body: Error Message: could not extract ResultSet.
Please see application logs for more details.

• This indicates bad set-up on the mappings for plans, charge accounts, or customer types. The bad sql should be identified and corrected.

Subject: <Community Name> - IOException
Body: Error Message: Server returned HTTP response code: 503 for URL: https://pcc.fullcountintegration.net:20443/integration-pcc/request/1910.
Please see application logs for more details.

• This indicates maintenance on the production servers. If the name is a remote community, this can be ignored.

Subject: Failed to process Event
Body: PCCEvent [id=<id>, processed=E]
Accessed unprocessed events have existed for over 15 minutes. All accessed unprocessed events will be marked as an error.
Please see application logs for more details.

• This indicates that we were backed up from processing records from PCC. This could be due to a large load of records or from issues on the PCC side.

Subject: Error Processing integration-matrixcare
Body: Failed to process Event
MatrixCareEvent [id=<id>, processed=E]
No community map found for facility ID: <facility id>
Please see application logs for more details.

• This for a new community that has not yet been mapped. This community needs to be added in matrixcare_integration_obj_owner.community_map.

Subject: Error Processing integration-matrixcare
Body: Failed to process Event
MatrixCareEvent [id=<id>, processed=E]
Invalid event data for event id: 23
Please see application logs for more details.

• This indicates we were not able to parse the HL7 message we received from MatrixCare. Investigate the event to find out why.

Subject: Error Processing integration-matrixcare
Body: PCCEvent [id=<id>, processed=E]
Accessed unprocessed events have existed for over 15 minutes. All accessed unprocessed events will be marked as an error.
Please see application logs for more details.

• This indicates that we were backed up from processing records from PCC. This could be due to a large load of records or from issues on the PCC side.

Employee Integration Emails

Subject: <Server Name> - unable to process file <File Name>.
Body: Error Message: Community unable to be found. Community id is <>. <Line from file>
Please see application logs for more details.

• This indicates bad data. The community should be reached out to to resolve the issue.

Subject: <Server Name>  - unable to process file <File Name>.
Error Message: For input string: <Value>.
Please see application logs for more details.

• This indicates bad file format. The community should be reached out to to resolve the issue.