Product
Your data, through your own keys.
A REST API and a FHIR R4 endpoint, switched on by your administrator in Settings. Generate a key, choose the scopes, and read or write against the same record the product uses.
Off by default. An owner or administrator enables it in Settings → API access.
Where you turn it on
Settings → API access. Nobody has to open a ticket.
API access is disabled until an owner or administrator enables it, which keeps a live endpoint from existing on an account that never asked for one.
Read and write patients, appointments, notes, claims, and staff records.
Standards-based read access for health information exchange and partner systems.
Push events to your own systems on admission, discharge, signature, and remittance.
Off unless a qualifying consent covers the recipient. Enforced per request, not per key.
# request curl https://api.probitycare.com/fhir/r4/Patient/hp-0041982 \ -H "Authorization: Bearer pk_live_8f2a…" \ -H "Accept: application/fhir+json" # response { "resourceType": "Patient", "id": "hp-0041982", "active": true, "name": [{ "family": "Alvarez", "given": ["R."] }], "birthDate": "1991-04-17", "managingOrganization": { "reference": "Organization/harbor-point" }, "meta": { "security": [{ "code": "R", "display": "restricted" }] } }
What is exposed
FHIR R4 resources and the REST equivalents.
The FHIR endpoint is read-oriented and built for exchange. The REST API is what you use to build against your own account.
- Patient
- Encounter
- Condition
- Observation
- MedicationRequest
- AllergyIntolerance
- CarePlan
- Practitioner
- Organization
- Coverage
- Appointment
- DocumentReference
Each key carries explicit scopes. A reporting key that can only read appointments cannot write a claim.
API requests appear in the same immutable activity log as human access, with the key and the IP.
Protected records are excluded unless an active consent covers the recipient. A key cannot override that.
Published per-key limits with clear headers, so a bulk export does not degrade your clinicians' day.
Build against synthetic data before you point anything at a live tenant.
Take your full record set out in a usable format at any time, including on the way out.
Why it is a setting and not a sales conversation
Your records should not be something you have to negotiate access to.
Charging for API access is a way of charging you to leave. It is a toggle, it is included, and the documentation is public once your administrator turns it on.
Works with
It runs on the same record as the rest of the platform.
Clinical
Health record & eMAR
Diagnoses, medications, allergies, vitals, labs, and administration records on the same chart as the clinical note — so residential and detox programs stop keeping a second paper MAR.
Read more →Audit & compliance
Roles & permissions
A tech, a biller, a clinical director, and an owner should not see the same chart.
Read more →Audit & compliance
Activity log
An immutable record of who did what and when, across the whole tenant.
Read more →Get started
Start today, or take a look first.
Create an account in minutes. Or book a 30-minute walkthrough.