Our recent Health Information Networks white paper has shed light on these critical, complex databases. Want to skip ahead to the good parts?
Our recent Health Information Networks white paper has shed light on these critical, complex databases. It’s an accurate snapshot of healthcare data sources right now.
It’s also 50 pages long. Want to skip ahead to the good parts?
Even if you’ve seen our findings, check out this summary and some fun facts about the national networks you might have missed.
In 2023: State of US Healthcare’s National Network Data Exchanges, we explain what these networks are, and how digital health companies can use them today.
Since Particle has truly industry-leading connectivity to these healthcare data sources, we can surface unique insights about them.
In part 1, we discuss the three major health information networks, the recent data that HINs have, and the basic mechanics of why HINs are working well. If you really want to know the technical details, our engineers shared those too.
In part 2, we share our research on HIN performance on a state-by-state basis. Check our numbers if you want - we just told you all about Particle’s workings right there in the open.
In part 3, we discuss why API solutions are the preferred choice for HIN connectivity. For most companies, the only realistic way to get HIN connectivity is to use features like Record Locator Services that companies like Particle provide.
In part 4, we present examples of how participants (maybe like you!) are actually using this HIN data.
Then in part 5, we preview expected technical changes to healthcare data networks, including TEFCA and QHINs.
We’ve conclusively proven that Health Information Networks enable participants across the healthcare industry to reliably share patient records today.
We have to be restrained in a white paper, so maybe you missed this part. But Individual Access is coming. That means you’ll be able to sync your medical records onto apps and services of your choice, without going through a connected doctor or hospital. Everyone from fitness apps to insurers should get ready for phenomenal change. (page 42)
Over 95% of patients that we find data on have medication lists, problem lists, lab results, encounter info, and more. This helps clinicians inform care decisions. Consider how we find data for 90% of patients on these networks, and you'll see why care organizations have worked so hard to set up these networks in the first place. (page 28)
If you do the math, Particle accounts for a not-too-shabby portion of their documents exchanged. (page 8)
Few people believe this, but we looked it up, and that’s what their website says.
Medical…care? This word cloud of the 100 most common endpoint descriptions (effectively, names of care sites) paints a broad picture of networks, except for one dialysis provider in the lower right corner that stands out by properly labeling their endpoints.
While each of the major networks connects to care organizations in Wisconsin, this is one state where Health Information Networks really seem to diverge. Wisconsin is the home of a major Carequality booster, which could account for network disparities there. (page 23)
7. There's a Good Way to Meet the Treatment Purpose of Use
You have to generate net new treatment data to comply with this important aspect of joining the networks. For now, if you want to be on national networks, think about how you can give data back too. (page 15)
If you have any more questions about interoperability and Health Information Networks, don't hesitate to contact us. We’re happy to share the news about the State of US Healthcare's National Networks.
We're sharing our internal measurements on the current performance - and future status - of the Health Information Networks that hold America's patient data.
We know what APIs are, and what they do. So why choose an API as a product? APIs have become largely ubiquitous in the tech landscape, and for good reason. While there are alternatives, it's important to understand why we don’t choose them. Check out Part 2 of our three part miniseries on APIs.