Digital record retrieval enables your connection to the Carequality Interoperability Framework, a nationwide network of healthcare organizations comprising over 600K providers, 50K clinics, over 4,200 hospitals, and millions of patient records. Carequality facilitates the exchange of over 150M clinical summary documents every month between Carequality participants.
Instead of needing a business agreement with hundreds of individual organizations, you can use digital record retrieval to make one connection for access to records from any Carequality participant.
You don't have to use digital record retrieval to have Carequality as one of your connections through Redox. But with digital record retrieval, we serve as your Carequality implementer and responder.
You can choose to be your own implementer and responder to connect with Carequality, but it may take a significant amount of time to get started. So if you don't want to reinvent the wheel, use our experience to get started with Carequality in a matter of days instead of months.
But if you must, learn how to be your own responder.
As a Carequality participant, you can obtain information about a patient and their medical history, including clinical details like allergies, diagnoses, and medications, without connecting to each individual healthcare organization.
Explore our network or use the Carequality search to review a list of current Carequality participants.
Since sharing is caring, you're required to share your data in return with other Carequality participants. Carequality has two foundational requirements to ensure that a patient's entire clinical history is available nationwide to retrieve:
If your organization doesn't meet the exceptions mentioned above, you're required to respond to incoming requests with your unique clinical data.
The Framework supports the exchange of C-CDA documents, which is an industry-standard for exchanging patient and visit information.
The two primary types of supported documents are patient summaries and visit summaries. Patient summaries represent a current—or nearly current—snapshot of the patient’s chart while visit summaries contain a patient’s chart for a specific visit and are considered accurate as of the visit date.
The list below contains a summary of rules for returned data. Learn more details about HL7 standards.
null
if there is no relevant data or a participant doesn’t have the ability to include data):We're a certified Carequality implementer. Implementers are approved to help organizations like yours connect to Carequality. Basically, we serve as your on-ramp to the Framework. With us as your implementer, you can start exchanging data across the Framework in a matter of days rather than months.
As your implementer, we complete the following steps for you:
Being a Carequality participant can entail a high volume of incoming requests. These volumes are influenced by factors like your geographic location or the number of facilities within your organization.
Many Carequality participants automatically trigger outbound requests by running algorithms with radius-based searching around the patient’s address. So, rural areas may receive 10K–25K of these requests daily, whereas geographic areas with high population density—like the San Francisco Bay Area or New York metropolitan area—may see daily request volumes of up to 200K per location.
As your responder, we can shield you from this traffic and simplify your flow so that you only have to send new or updated information to us. We take care of the rest with the data you already have.
If you prefer to respond to incoming traffic yourself, you won't qualify for digital record retrieval pricing. Talk to a Redoxer to discuss options and pricing.
With digital record retrieval, you have a limit of 25K API calls per day and per location to the Framework. An API call is defined as sending a request via Redox that results in a response from the Framework—this includes searches for patients that don't return matches.
These query requests are included in your total allowable amount per day:
To locate a patient and retrieve their documents, you need two API requests at a minimum (PatientSearch.Query and ClinicalSummary.PatientQuery). This means that you can locate up to 12.5K patients per day at most with digital records retrieval—so long as you don’t use any other requests. Given this, you can calculate whether that limit is sufficient depending on whether a patient may exist at multiple healthcare organizations within your geography.
These query requests are excluded from your total allowable amount per day:
Success
state. Basic information
How-to
Troubleshooting