New Feature - API v1 and FHIR
Back around 2020, I wrote about version 1.0 of the UnaCasePro API. A lot has changed since then, so we went back to the drawing board and built a brand new one. While we were at it, we built a second API that speaks FHIR. Both are live in production right now.
Why should you care? Because your data shouldn't be stuck in one system. Your director wants a dashboard. Your epidemiologist wants the numbers in the data warehouse. Somebody down the hall wants to hook into a health information exchange. Too often that means someone exporting spreadsheets and re-keying records by hand. Nobody got into public health to do that.
The API
This one is a read-only REST API that returns JSON. It covers what you'd expect: clients, cases, referrals, care plans (needs, goals and outcomes), contacts, notes, time entries, programs and dynamic forms. Yes, that includes PHQ-9 and GAD-7 scores.
We already built a Power BI dashboard on top of it, and that's exactly the kind of thing it's made for. Your own reports, pulling straight from UnaCasePro, without waiting on anybody.
The FHIR API
If you haven't run into FHIR yet, you will. It's the standard healthcare systems use to share data with each other. Our FHIR API is R4 (4.0.1) and supports read and search on Patient, Practitioner, Organization, EpisodeOfCare, Encounter, Condition, Observation, CarePlan, Goal and DocumentReference.
A few of those are worth calling out. Condition covers diagnoses and social determinants of health (SDOH) needs, which is a big deal for case management. Observation carries vital signs. DocumentReference only returns signed notes, so drafts stay where they belong.
Each agency's FHIR endpoint also publishes a CapabilityStatement. That's FHIR-speak for "here's what I support," so the system on the other end doesn't have to guess.
Security
Both APIs use OAuth 2.0. Every system that connects gets its own credential, and you decide exactly what each one can see, right down to individual FHIR resource types. Want to lock a credential to your county's IP addresses? You can. Every call is rate limited and logged, and the logs don't contain PHI.
Both APIs are also turned off by default. Nothing gets shared until your agency says so.
Want in?
We turn on API access one agency at a time. If you want to connect UnaCasePro to Power BI, your data warehouse or another system, reach out and we'll walk you through setup and the API docs.
So what would you connect it to first? I'm curious. Drop me a line and tell me.