Platform service providers can offer Particle’s nationwide interoperability API to their care organization clients.
Interoperability should be the default expectation for digital health tools. Electronic health record (EHR) platforms that meet modern standards for record sharing demonstrably reduce mortality rates, improve care outcomes, and address clinician burnout compared to other EHRs.
So, today we’re launching Particle for EHRs to ensure that any platform for healthcare providers can include interoperability as a feature. Particle for EHRs is a new product that lets electronic health record and platform service providers integrate Particle’s API results directly in their software, for any or all of their clients, with a single API integration.
Particle for EHRs is a new administration and management layer on top of the existing Particle platform. It allows EHRs and platform service providers who do not have direct treatment relationships with patients - but whose customers are treatment providers - to provide Particle’s full suite of solutions inside their platform for the first time.
EHRs need only send basic information about their customers - entity name, address and NPI - for Particle to structure that hierarchical information everywhere it needs to live on health information networks. EHRs can then make patient document requests, subscribe to ADT messages, and use all of Particle’s existing features on their clients’ behalf.
Yes, it’s the same great API we’re already using to improve clinical outcomes - but now we're able to open it up to a huge new set of users.
EHRs can market these new features any way they like. Treatment providers will think these are features of the EHR itself.
In case national interoperability networks weren’t enough, we also enable two comprehensive data sources - admission, discharge and transfer (ADT) feeds and medication adherence information - in the same API connection.
Interoperability: Particle’s API is all that EHRs need to make interoperability queries to the three major national interoperability networks + frameworks: Carequality, CommonWell, and eHealth Exchange. We handle accurate directory listings for each of their client’s locations (like a practice with offices in Florida and Wisconsin, for example). User creation, record location, and everything else that an EHR needs to activate a treatment provider is included.
ADT Feeds: This solution is a powerful way to prevent readmissions and monitor individual patients. ADT messages are nearly real-time notifications that are pushed to providers when their patient is admitted to an acute care setting. Clinicians who catch these messages in time can intervene accordingly. While the ADT scene is even more fragmented than interoperability, typically requiring time-consuming integrations with each participating provider, Particle for EHRs connects EHRs and their clients to ADT feeds for a stunning 10,000+ healthcare facilities.
Medication Adherence: Our data partner delivers comprehensive claims and retail point-of-sale data from most pharmacies. We can provide supplemental RX data like fill dates, prescriber names, and pharmacy locations. This helps care organizations monitor whether a patient is taking drugs as prescribed. With medication fill data, clinicians that rely on Particle for EHRs will get a more complete picture of patient care.
Network and HIE integration has historically been a piecemeal process for EHRs. It involves maintaining many complex integrations, as well as managing the organizational complexities that come with them. In practice, only the very largest EHRs serving the biggest hospital systems have been able to offer interoperability network integration to their customers.
Particle for EHRs opens network connectivity up to EHRs of any size through a single API integration, allowing EHRs to deliver workflows that are increasingly critical for their customers. Particle specializes in interoperability, and we think the solution we offer is far more robust than what any EHR vendor has currently hacked together.
As part of the re-architecture to build Particle for EHRs, we’ll soon support the addition of multiple Locations in our portal for all our customers. This means that a digital health provider that offers its services nationwide is no longer restricted to a single directory entry in the networks. We can add in every geography within which digital health providers offer their services, letting them respond to bi-directional queries accordingly.
If you’ve visited our developer portal over time, you’ve seen us continuing to add features large and small. Particle for EHRs gives our team more chances to make the portal look nicer, too.
Our talented team has put a lot of effort into this product. There’s so much more to share with EHR vendors and platform service providers.
I hosted a live demo webinar -- If you’ve made it this far, and would like to receive a copy or see a demo, message our team here!
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.
What is an API? The answer to what an API does seems pretty obvious, at first glance. However, what an API actually is can be sometimes misunderstood, so we've put together this high-level technical overview to help you better understand both what Particle's API is, and what our API does.