Refer to these questions for help with Redox Access™ and integrating with Carequality.
- Explore Redox connections. Find out what other organizations you could partner with via Redox.
- Explore the Carequality directory. See who's already participating in the Carequality Interoperability Framework.
- Set up Redox Access. Get started using Access.
Yes, one easy-to-use Redox configuration can connect you to Carequality, as well as your other connections.
So you can use the same Redox APIs to search for patients and clinical documents either from individual connections or nationwide networks like Carequality or DirectTrust. Talk to a Redoxer if you have questions about how to do that.
Check out the specs for our Redox APIs to find out the requirements and supported data for each:
Commonwell and eHealth Exchange are two of the nation’s largest centralized health information exchanges. Both are certified Carequality implementers with thousands of live sites, meaning that many of their sites can be queried via the Carequality Framework.
Short answer: No, Carequality doesn't support push notifications.
Longer answer: No, Carequality doesn't support push notifications (same with Commonwell). But you may want push traffic since it's great for use cases like provider-to-provider messaging, event notification, diagnostic test ordering, and referrals. In general, push notifications are great when you want updates about patient data without having to query for it every time.
If your unique workflow includes any of the use cases for push scenarios, we can help you send and receive push notifications from another nationwide network, DirectTrust, instead. Talk to a Redoxer to learn more.
As your responder, we use the data you push to Access to respond to Carequality queries. But we isolate the data you push to improve the robustness, integrity, and consistency of our test system. The downside is that you won't be able to find the patients you add to Carequality.
If you really do need to find your own patients or documents, you can search your data on demand repository using these queries:
- PatientSearch.Query
- ClinicalSummary.DocumentQuery
- ClinicalSummary.DocumentGet
Just make sure you switch the Carequality destination.ID to the data on demand repository.ID instead. When you search data on demand, your IDs match exactly what you sent. But keep in mind that the record ID isn't the same one that appears in Carequality.
To guarantee uniqueness, Carequality assigns new IDs to all patient and document records they receive. So when you push a patient with ID 1234 or a document with ID 5678, you won't be able to search Carequality with those same IDs.
To find the Carequality-assigned IDs, you must perform a patient search with demographics to Redox Access. Then, find the patient's related documents. With the Carequality ID, you can retrieve data from other Carequality participants that may be for the same patient.
If you receive a successful response without any results, it typically means that there were no matching patients found. You may want to search with a smaller set of demographics or verify that the patient’s information is correct.
Yes, but only if you have the specific patient ID and matching OID that the organization uses to represent a patient OID type.
For example, if you use a medical record number (MRN), you must have the OID that the organization uses to represent MRNs. However, you typically won't know these OIDs since organizations often have a specific identifier for Carequality responses.
We recommend starting with a demographics search, even if you do already have an identifier.
When you use the PatientSearch.LocationQuery, our record locator service runs the search for you. However, it may take awhile to return all the results because record locator service sends the query to each connection individually. You can check the status of your search by looking for the Meta.Extensions.task-status.string value, which will either be Active or Success.
Status | Definition | Results |
|---|---|---|
Active | The process is asynchronously collecting locations. | The Patients array populates with any partial results as they become available. |
Success | The process has been completed and all possible locations were found. | Any available results have been returned. If the Patients array is empty, it means no patients were found. |
The response waits up to 10 seconds to reach a Success state. If unable to reach Success in that time, the response stays Active. You can retry the exact query repeatedly until it reaches a Success state.
To review the results of your search again, you can provide the value returned in Meta.Extensions.task-id.string on later queries.
If you run a new search with the same patient demographics within a 24-hour period, you'll see the same results. Record locator service doesn't trigger a new search unless you have new or modified patient demographics.
Redox Access's record locator service searches for patients within a 100-mile radius of the sender organization (as defined in Meta.Extensions.sender-organization-id). Record locator service also searches within a 100-mile radius of the patient's ZIP code, if provided. This means there could be a radius larger than 100 miles if those two ZIP codes aren't the same.
This is one of the multiple ways we locate matching patients based on the search criteria. The search logic is subject to change without notice if we identify ways to improve the matching rate.
You can use any of the fields in the ClinicalSummary.DocumentQuery to specify a date range or the types of documents to return. Using any of those fields should limit the number of documents in the response. We recommend using the Visit.StartDate to pull documents after a given date of service.
Review the supported fields for this query. Just keep in mind that some Carequality participants may not support all of these fields.
We offer the XML response since some organizations have pre-built capabilities to render XML C-CDA documents. There are also many available open source CDA renderers that can be useful in viewing the XML document.
If you're interested, check out these options for an open source C-CDA renderer:
Yes, you can respond to queries from Carequality participants yourself, but you won't qualify for Redox Access. Learn how to be your own responder.
We store all requests to and from Carequality per our standard data retention policy. Learn more about our data retention policy.
To be a little more specific, we store all of the data you push to your data on demand repository for the life of your contract. We store it so that we can adequately respond to your incoming Carequality queries.
You must push data (via ClinicalSummary.VisitPush) to your data on demand repository for every patient treatment. You don’t have to push data immediately after every treatment, though. For example, you're welcome to push a daily batch to us instead.
You must also push all patient demographic updates to us so that we can keep your patient demographics current. Remember, we're responding to incoming Carequality queries for you. Having all your updated data lets us accurately respond when someone asks whether a patient has been seen at your location.
Carequality requires that you respond to queries about patients you've seen, but they don’t specify a definite period for historical information. We recommend that you begin pushing data once you register your organization in production and build your historical data from that point forward.
If you want to send historical data, you may not qualify for Redox Access. Talk to a Redoxer to discuss your needs.
FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.