Maintain your Redox repository

Who can use this how-to

  • Starter package customers using digital record retrieval
  • Existing customers using digital record retrieval

All Carequality participants—including those who join via Redox—are required to respond to any requests they receive from other Carequality participants. In some cases, you may receive up to 200K requests per day.

With Redox as your Carequality responder, we can respond to incoming patient requests on your behalf. But you must push your patient records and documents to your data on demand repository so that we can maintain an accurate representation of each of your patients.

For direct responders

If you are your own responder, you must build an infrastructure capable of supporting such a large volume of incoming requests. And, you must still maintain your own patient and document database so that can respond to incoming requests with the most accurate data.

Use curl for technical validation

You can copy the code examples we provide and send the test requests with curl (learn more about curl) instead of Postman. Keep in mind though that you need to remove the comments from the code examples (starting with //) and replace any variables (e.g., {{variable here}}) to use them. Also, note that some of the code examples are abbreviated, so be mindful of that if you're copying them for your own use.

Maintain your patient database

As you create and update patients in your system, you need to ensure that they stay current in your data on demand repository.

  1. For new patients, send a PatientAdmin.NewPatient request with the new patient's details to your data on demand repository. You must use at least one patient identifier with the ID Type of the patient OID assigned to you in the wizard.
  2. If demographics or contact information changes for existing patients, send a PatientAdmin.PatientUpdate request with the updated details to your data on demand repository.
  3. To combine duplicate records for one patient, send a PatientAdmin.PatientMerge request to merge the patient records in your data on demand repository and replace the previous identifiers with the new one.

Save patient documents

  1. After providing care for a patient, save the patient summary documents to your data on demand repository so that we can respond to requests for documents. We recommend using the ClinicalSummary.VisitPush request with all the available unique clinical information that you produce. Keep in mind the following requirements:
    1. The Header.Document.ID must be globally unique across Carequality as either a GUID or an internally unique ID prefixed with your organizational OID. Our examples use the OID prefix.
    2. The Header.Document.Type and Header.Document.TypeCode should be a LOINC code. In most cases, you should use the code for a Continuity of Care Document (i.e., 34133-9). When sending a document related to a single patient visit, you should use the code for Progress Notes (i.e., 11506-3) for outpatient/ambulatory visits, or discharge summary (i.e., 18842-5) for inpatient/hospital visits.
    3. At least one of the patient’s identifiers should include an ID Type of the patient identification OID matching the same value used in the PatientAdmin messages.

Since ClinicalSummary.VisitPush is lengthy, we include an abbreviated example below. Check out an unabbreviated example or view the Postman package.

Next steps