Error Scenarios and Conditions

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