Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/The answer is it depends
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

The answer is “it depends.”

Source: Redox•November 16, 2026 at 11:07 PM

The answer is “it depends.”

Most integration requests start with a destination: connect us to this EHR. The right pathway depends on what happens once the data arrives. Kalyn Gigot, SVP of Customer Success, breaks down national networks, Direct messaging, TEFCA Individual Access Services, and direct connections, and covers…

This post was written by Kalyn Gigot, SVP of Customer Success at Redox.

A guide through the pathways available to access healthcare data.

When organizations reach out to Redox to inquire about our capabilities, nearly every note opens with a destination. Connect us to this EHR. Give us one API for all of them.

The useful part comes later. Here are some of the requests we’ve fielded over the last couple of months. One team needs the date of a patient’s last mammogram. One practice wants a signed progress note to land in a skilled nursing facility’s chart, with nothing coming back. A founder wants patients to pull their own records into an app. A lab needs orders out and results in. Even though the notes start the same way, the details reveal real differences that inform the best solution option.

I’ve spent the last 10 years guiding Redox customers through finding the right answer for them to these exact questions, and others just like them. There is a general set of pathways, and each pathway has trade-offs like speed, control, data readiness, and who has to say yes. Here’s my take on how the options stack up, with one caution. Every data situation is different, so use this to ask better questions, not to skip them.

At the end of the day, the goal is the same: getting the data you need, where you need it, in a form you can actually use.

Note that this blog post assumes a level of familiarity with healthcare, interop, and national networks related terms (e.g. BAA, TEFCA, write-back). Check out Redox’s on-demand resources if you want more familiarity with the vocabulary.

Networks are broad and fast, but you get what the sender gives you

National Networks like Carequality and TEFCA let you pull records from a vast network without signing a BAA with each provider, and teams are often live in days to weeks. The trade-off is control. You query, and you get back whatever the network has. The format is variable, it might be C-CDA, ADT, or FHIR, in whatever condition it was stored. Completeness varies, and there is no write-back.

Before you can access the network, you have to provide justification. This ensures that only authorized personnel and systems can view PHI, and that requests are for a valid clinical or business need.

This is called Purpose of Use (POU). “Treatment” is the most dependable purpose, defined as direct care provided by doctors, specialists, and nurses. Other Purposes, such as Payment and Operations, are less dependable because responders may not be required to answer. You’ll have to prove answers to questions like, Who is the authorized clinician? Does the workflow qualify as treatment, such as retrieving records before an appointment or following an ADT feed for care coordination? And once you have the data, how does it inform care?

Assuming you can prove Treatment as a POU, using Networks is a great option for getting a broad swath of data, quickly. Be prepared for the data returned to require a lot of work before it is ready to use, and expect that it may not be complete.

Direct Secure Messaging reaches a named clinician fast, but nobody promises it was read

Direct Secure Messaging (DirectTrust and 360X, not those DMs) is similar to a National Network in that you can access a vast network without BAAs and VPNs, and often get it up and running in days to weeks. But that’s where the similarities end.

It is a push mechanism, a directed send to a named clinician. Even better, the data format is variable. It is well-suited for referrals and transitions of care. We often recommend Direct Secure Messaging to satisfy CMS ACCESS model requirements to push a care plan to another provider.

However, you have to treat it as transport. The document lands in an EHR inbox, not a discrete field, and nobody can promise it was read (similar to email). 360X can close the referral loop, but only if the receiving EHR instance has turned it on. And remember, fax is still out there!

Direct Secure Messaging is a great option to reach a lot of providers, directly and quickly, especially when the payload or format is variable. Be prepared for a lot of radio silence though.

Patient consent skips the provider, but it needs a patient who says yes

TEFCA Individual Access Services (IAS) lets a patient verify their identity once, through a partner like CLEAR or ID.me, and request their own records across participating Networks. Consent comes from the patient, data returns structured as FHIR R4 or CCD, and responders are required to answer without charging. No BAAs, no VPNs, no integrations, no POU.

For a consumer app with a patient relationship, that is a real unlock.

As the saying goes, if something sounds too good to be true, it probably is. There are trade-offs here as well. Patient consent isn’t as easy as it sounds. If your product has no patient touchpoint, there may be no practical way to collect that yes. Data return is structured and answers are required, but completeness, quality, and readiness for use are the same as any other data coming from National Networks, so be prepared to do some serious cleanup work and expect additional chart chasing. And again, no write-back.

Only direct connections write to the chart, but each one is its own build

Direct connections (an integration between you and a specific system or organization) require a direct BAA and a build at each site. They are the most flexible on purpose of use and format (e.g. FHIR, HL7v2, flat files, bulk, X12, CDA), and the only pathway that supports both push and pull, including discrete write-back.

As anyone in interop will tell you, if you’ve integrated with one instance of an EHR, you’ve integrated with one instance of an EHR. Meaning that, for most teams, this work is not reusable. If you are integrating with a health system, it depends on provider IT teams, what each EHR can do, and your team’s experience in building integrations. It can take many weeks to months to stand up one integration. And then you have to monitor and maintain it – but that’s for a different blog post. (oh look!, we just happened to write about it here)

Write-back is the sleeper requirement. In the notes we get from inbound prospect requests, it often appears as the final bullet, something like, “file a PDF to the patient’s chart.” If your workflow ends in the chart, this is your only pathway option.

It is also where teams hit the wall because, if you do it yourself, it means one site, and one integration, at a time. One start-up founder told me about being so excited when his team finally got their first hospital connected, then learning that every other hospital needed its own build. That is why reusable connections and expertise matter. Redox has over 12,000 reusable connections, and a deep bench of experts who have been doing this work for many years. So the work becomes customizing the last 10 to 20 percent instead of starting from scratch, and you have folks ready to guide you every step of the way.

Start with what happens when the data arrives, not where it comes from

Back to those inbound inquiries. The people who wrote in asked for a destination, but that’s not the only question. We also need to consider where the data has to end up, who has to agree, and how much work your team will need to do to make the data usable. Speed and control pull in opposite directions, and often the answer is a mix. It depends on your team, your business needs, and the trade-offs you can live with.

That mix is the norm, not the exception. Most teams end up needing more than one pathway: a network pull for history, Direct Secure Messaging for a referral, one or more direct connections to write back to the chart. I referenced CMS ACCESS earlier, and that’s a great example use case. Participating entities need to connect with a network for patient history, Direct Trust for patient referrals, and CMS to submit results/outcomes and receive payment.

So do this before your next planning meeting. Write your use case in one sentence: who needs what data, from where, and what happens once it arrives. Then send it to Redox this week. We work across every one of these pathways every day. We’ll tell you plainly which ones fit, which don’t, and where the traps are. And, we will be with you every step of the way to help you get the data you need, where you need it, in a form you can actually use.

← All articles

What this article says

More in HealthTech & MedTech

All →
Purification Archives
Thermo Fisher Scientific

Purification Archives

Chromatography Archives
Thermo Fisher Scientific

Chromatography Archives

Analytical Chemistry Archives
Thermo Fisher Scientific

Analytical Chemistry Archives

Elation Health Joins OpenAI’s Healthcare Plugin Ecosystem to Extend Primary Care Relationships Beyond Clinical Walls
Elation Health

Elation Health Joins OpenAI’s Healthcare Plugin Ecosystem to Extend Primary Care Relationships Beyond Clinical Walls

GE HealthCare expands global collaborations to help define the future of photon-counting CT with Photonova? Spectra
Ge Healthcare

GE HealthCare expands global collaborations to help define the future of photon-counting CT with Photonova? Spectra

Medtronic to acquire Contego Medical, expanding access to next-generation carotid therapies
Medtronic

Medtronic to acquire Contego Medical, expanding access to next-generation carotid therapies

More from Redox

Every healthcare data integration costs you twice
Redox

Every healthcare data integration costs you twice

What Redox is releasing: October – December 2026
Redox

What Redox is releasing: October – December 2026

Two years of partnership scaling sepsis care nationwide
Redox

Two years of partnership scaling sepsis care nationwide

Activation gets the headlines. Infrastructure does the work. Here’s what that looks like in practice.
Redox

Activation gets the headlines. Infrastructure does the work. Here’s what that looks like in practice.

Redox Joins CMS Health Tech Ecosystem as an Aligned Network
Redox

Redox Joins CMS Health Tech Ecosystem as an Aligned Network

Agents in production: what actually changed and where we go next
Redox

Agents in production: what actually changed and where we go next