Failed Prescription Errors
Message type not supported by sender
This failure message means that Surescripts has marked the provider's SPI inactive
due to lack of use. Re-registering the provider with Surescripts will resolve the issue.
Attempting to update the location does not own this prescriber
This failure means that the provider switched away from NewCrop and NewCrop no
longer owns this SPI. If the provider needs to still use NewCrop, registering the
provider for a service level of New only, meaning the provider can transmit new Rxs out but no longer receive renewal requests, and generating a new SPI/LOC will resolve the issue.
Failure Internal error. Contact pharmacy by other means
This failure means that the pharmacy is having connectivity issues.
Failure Portal is not configured to send message version 6.1
This failure means that an account has been moved over to 20170701 and the provider
was not re-registered with Surescripts to be in the correct portal. Re-registering the
provider with Surescripts will resolve the issue.
Failure Error: The 'Header' element is not declared or The 'Body' element is not declared.
This failure means that the match with Surescripts was being attempted at the same time that the Rx was being sent. The result is the header was not added to the XML in the background when sending it over to the pharmacy. Resending the Rx normally will resolve this issue.
Failure Ex: VR: Error The 'PayerID' element is not declared
This failure means that the payerID had not yet been populated from Surescripts Benefit and History at the time the Rx was sent. Resending the Rx normally will resolve this issue.
Failure Partner rejected transaction with an error
You will see this failure with Rxs sent to CVS. This failure means that a 2nd duplicated Rx was sent and failed. The 1st one was received without any issues.
Failure Error: The operation has timed out
This failure means there are connectivity issues with the pharmacy. Resending the Rx will usually resolve this. If it does not, NewCrop will have to open a ticket with Surescripts for them to research further.
Failure Error: The underlying connection was closed: An unexpected error occurred on a receive
This failure means there are connectivity issues with the pharmacy. Resending the Rx will usually resolve this. If it does not, NewCrop will have to open a ticket with Surescripts for them to research further.
Failure Unexpected Exception occurred while processing the request
This error means there are connectivity issues with the pharmacy. Resending the Rx will usually resolve this. If it does not, NewCrop will have to open a ticket with Surescripts for them to research further.
Failure Transaction is a duplicate
This failure means that a 2nd duplicated Rx was sent and failed. The 1st one was received without any issues.
Failure Duplicate Prescription, original message has been processed
This failure means that a 2nd duplicated Rx was sent and failed. The 1st one was received without any issues.
Failure Not authorized to send Controlled Substance
This failure means the provider did not re-registered with Surescripts once EPCS was completed. Re-registering the provider with Surescripts will resolve the issue.