3. Prepare to respond to requests

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 so that you don’t need to build an infrastructure capable of supporting such a large volume. To do this, you must regularly push data to us so that we can maintain an accurate representation of your patient database and the applicable documents for each patient. You do this by maintaining your patient database and saving patient documents regularly. Check out more details below.

Step 1: Maintain your patient database

As you create and update patients in your system, you need to ensure that they stay current in our database. Use at least one patient identifier with the ID Type of the patient identification OID assigned to you in the wizard.

Create a new patient

For new patients, send us a PatientAdmin.NewPatient request to create that patient in our database.

Update an existing patient

If demographics or contact information changes for existing patients, send a PatientAdmin.PatientUpdate request to update our database.

Merge patients

To combine records for one patient, send a PatientAdmin.PatientMerge request. This request merges the patient records in our database and replaces the previous identifiers with the new one.

Step 2: Save patient documents

As you provide care for patients, send your summary documents to us so that we respond to document requests as well. We recommend using the ClinicalSummary.VisitPush request with all the available unique clinical information that you produce. 

Keep in mind the following requirements:

  • 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.
  • 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.
  • 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 VisitPush is quite lengthy, we include an abbreviated example below. Check out an unabbreviated example or view the Postman package.