More than a blog, it’s Particle Health’s showcase.
Particle’s engineers explain how we take steps to munge, or standardize, data for the benefit of our users.
To find clinical data, you need a Record Locator Service (RLS), and it’s gotta be a good one!
Querying for a patient’s records looks easy to end users because of what our platform does behind the scenes.
Good data professionals consider the ethical obligations of working with sensitive data.
Particle VP of Engineering Dave Hauenstein spoke with PodRocket about what happens when companies start relying on teams instead of individuals, and how developers can build meaningful careers.
Particle uses OAuth 2.0 Authorization Framework to ensure secure access to medical data to our customers. Given that this framework is very complex, we've put together an overview that explores how it works by sharing examples of how we use this technology in our everyday lives.
Particle Health offers two distinct APIs: C-CDA and FHIR. They both offer the same level of unparalleled access to patient health data, but they differ significantly in how they offer access to that data. Let’s dig into Part 3 of our three part miniseries on APIs.
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.