Appendix A: Common errors

The Carequality Interoperability Framework has disparate, varied errors. Below, we describe common errors and the steps you can take below.

If you need extra support to resolve any Carequality issues, contact our Help Desk.

You may receive an error that states:

No subscriptions. Meta.Destinations needs to contain a destination from existing subscription. 

This means that the endpoint you specified to receive the request is invalid. The ID for the receiving endpoint should be in the Meta.Destinations array of your request. The ID differs based on the environment and the type of request.

If you receive this error, refer to the table below to make sure that you entered the correct ID.

You may receive an error that states:

This means that we we couldn't find the organization specified in your request. This can happen if:

• The organization was deactivated,
• The directory you're using is outdated, or
• The organization is a Query Initiator only.

The last possibility may be the case for organizations like EMS vendors or specialty pharmacies.

1. Refresh your copy of the directory to make sure it's the most current.
2. Query the organization directly to see if the entry is still active.

If you find a match via PatientSearch then try the ClinicalSummary.PatientQuery, you may receive an error that states:

This occurs when the organization doesn't have any documents available for the patient. In these cases, it's possible that patient consent is missing or that the patient is registered but hasn't had a visit yet, so there isn't any clinical data available.

If you expect documents but aren't getting any, contact our Help Desk so that we can reach out to the relevant implementers and Carequality participants.

You may receive an error that states:

This may occur as different systems undergo maintenance or small outages.

Given that these connectivity errors are typically temporary, we recommend retrying the request. If you see persistent problems with an organization, contact our Help Desk.

You may see any of these certificate errors:

Unable to verify the first certificate

or

Unable to get local issuer certificate

This means that the organization you're requesting data from incorrectly installed its certificate and security is compromised.

You may also see:

Self signed certificate in certificate chain

This means that the organization you're requesting data from installed the wrong certificate.

Connectivity with the Carequality Interoperability Framework depends on mutual TLS authentication to ensure security. The certificates issued by Carequality need to be refreshed and reinstalled periodically.

If you see any certificate errors, contact our Help Desk so that we can reach out to the relevant implementers and Carequality participants.

If you're responding to incoming requests, you can return granular errors by responding with the following format:

{
"body": {
    "XDSErrors": [
	{
	    "code": "XDSUnknownPatientId",
	    "message": "Patient Not Found."
	}
     ]
  }
}

In the body.XDSErrors.code field, you can return any of the following errors :

• XDSRepositoryOutOfResources
• XDSRepositoryBusy
• XDSRepositoryError
• XDSUnknownPatientId

In the body.XDSErrors.message field, you can include any additional information you want to relay back to the sender about the error.