--- title: Error Scenarios and Conditions slug: shin-interconnect-fhir/guide/error-scenarios-and-conditions docTags: createdAt: 2026-06-10T15:22:56.021Z --- **Error Scenarios with Sample Message** | **Transaction(s)** | **Error Message** | **Scenario** | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | All | AuthenticationDataInvalid - Invalid Authentication Credentials | Certificate Subject or Issuer is not configured within Interconnect or was not sent with the transaction.
-Workbench tool logs incoming values to check for typos in configuration. | | All | AuthenticationDataMissing - Invalid authentication info in the header | Certificate Subject or Issuer is not configured within Interconnect or was not sent with the transaction.
-Workbench tool logs incoming values to check for typos in configuration. | | All | Message Id must be 255 characters or fewer | Maximum length exceeded. | | All | Organization Id XXXXXX not authorized for this transaction | The Organization ID from the subject of the transaction is not configured for this transaction in the Interconnect system. | | All | Receiver - Part \{urn\:ihe\:iti\:xcpd:2009}Body should be of type org.hl7.v3.PRPAIN201306UV02, not org.apache.cxf.binding.soap.SoapFault | Transaction sent to Interconnect was not syntactically valid. | | All | Responder Id missing from request URL | Message was sent to the Interconnect endpoint configured for communication between two QHINs. However, no responder info was included in the URL.
- Check the RCE directory to verify the correct URL for a specific QHIN.
- Interconnect Participants should use the Interconnect URL | | All | Surescripts Health Information Network has encountered an error processing the message.
Cannot invoke method getAt() on null object | Transaction sent to Interconnect was not syntactically valid. | | All | Unauthorized - Organization Id 1.2.3454 not authorized for this account | Interconnect account, portal, and Interconnect Auth configuration of the Organization ID from the incoming transaction does not authorize processing for this transaction. | | All | Unexpected Exception occurred please contact technical support
or
There was an unexpected error processing the message | Incoming message is not valid or there is an issue internal to the Surescripts Health Information Network system. Review transactions in Workbench tool to see details. If the problem persists, submit a support case. | | All | Unknown responder 'XXXXXX' specified in request URL | Attempt to send a message directly to a specific QHIN responder through Surescripts Health Information Network failed. Invalid URL / endpoint was used. | | All | Unmarshalling Error: … | Transaction sent to Interconnect was not syntactically valid | | All | Required organization id (IHE-ID) not included in SAML on incoming message | Interconnect requires the Home Community ID of the sender to be sent in the subject organization is for each incoming transaction. | | All | No routable entity configured with IHE-ID = organization id ‘n.n.nnn.nnnn’ | The subject organization id on the incoming transaction is not configured on a data provider in the Interconnect system. | | All | Portal ‘nnnn’ for IHE-ID ‘n.n.nnnn’ does not match portal ‘yyyy’ from RLS\_AUTH | The configuration of the organization id listed is not consistent. The data provider portal and the RLS\_AUTH table portal are not in the same account hierarchy. | | All | Exception occurred: InvalidSoapMessage element | An invalid SOAP message is submitted. | | All | 400: Bad Request
403: Forbidden
404: Not Found
406: Not Acceptable
500 - Internal server error
502 – Bad Gateway
certificate check=invalidvalue
HTTP error code: 500
Connection refused
Connection reset
Connection reset by peer
PortalId\:nnnnn with URL\:http\://xxxxx
Unsupported or unrecognized SSL message | Issues with connectivity configuration, certificates, and mutual TLS may occur during the receipt of messages sent by Surescripts Health Information Network to external endpoints. Review details of errors in Workbench tool and work with the endpoints’ contact, if needed, to correct. | | All | 401: Unauthorized | Certificate mapping rule missing on the receiving system. | | All | Could not parse message | The receiving system is not able to process the message as expected. Work with the endpoints’ contact to correct. | | All | Index was outside the bounds of the array | The receiving system is not able to process the message as expected. Work with the endpoints’ contact to correct. | | All | Unexpected EOF in prolog at \[row,col] | This error occurs when the Content-Length value that is specified in the HTTP header of the response does not match the actual length of the response. Work with the endpoints’ contact to correct. | | Patient Search Request | Birth date needs to be formatted CCYYMMDD | Invalid date of birth format. | | Patient Search Request | First name must be 255 or fewer characters | Maximum length exceeded. | | Patient Search Request | Last name must be 255 or fewer characters | Maximum length exceeded. | | Patient Search Request | Middle name must be 255 or fewer characters | Maximum length exceeded. | | Patient Search Request | Suffix must be 50 or few characters | Maximum length exceeded. | | Patient Search Request | Only M, F, UN administrative gender codes are accepted | Invalid gender code submitted. | | Patient Search Request | Address line 1 larger than accepted (120 maximum length) | Address line 1 too long. | | Patient Search Request | Address line 2 larger than accepted (120 maximum length) | Address line 2 too long. | | Patient Search Request | City larger than accepted (50 maximum length) | City too long. | | Patient Search Request | State larger than accepted (2 maximum length) | Invalid state code submitted. | | Patient Search Request | Only USA zip codes are accepted | Zip does not comply with US formats. | | Patient Search Request | Internal Service Error | Interconnect application has encountered an internal error. | | Document Retrieve | System wasn’t able to generate the document. | The document originating system was not able to provide the requested document. Work with the endpoints’ contact to correct and retry the request. | | Document Retrieve | Unable to retrieve requested document(s) | A failure occurred during the retrieval of the requested documents. Review details of errors in Workbench tool and work with the document originating system’s contact, if needed, to correct. |