Scheduling API
Let people find open appointments across many providers, from one API that gathers each publisher's availability.
- FHIR R4
- SMART Scheduling Links
- FHIR Bulk Publish
GET/v1/scheduling/slotsLearn more about the Scheduling APIProducts
APIs for the healthcare ecosystem
Eight APIs you can use on their own or together: four workflow services and four building blocks. The haau3 platform API is in preview: it may change as we build, usually to add features or improve performance. Every API open to customers today is included in every plan. Free to start on the Developer plan. More services are planned.
Workflow services
Each answers a step in care: an open appointment, a medication list, what a plan covers, what a prescription will cost.
MedList API
Turn a patient's medication records, from however many sources, into one clean list with the evidence behind every entry.
Built with the Terminology API: the RxNorm codes MedList adds come from the same RxNorm release the Terminology API serves.
- FHIR R4
- US Core
- RxNorm
POST/v1/fhir/r4/$reconcile-medicationsLearn more about the MedList APIMedical Benefits API
Show what a Medicare Advantage or ACA Marketplace plan covers and what a member pays, from the plan files CMS publishes.
Built with the Provider Directory API: check whether the directory lists a provider in a Medicare Advantage plan's network.
- FHIR R4
- CARIN SBC profile (ballot)
- CMS plan files
GET/v1/fhir/r4/InsurancePlanLearn more about the Medical Benefits APIPharmacy Benefits API
Show what a prescription will cost before it is filled: cash prices at pharmacies near a ZIP code, or what a member pays under their own pharmacy coverage.
Not yet open to customers. Try it now in the Sandbox, where a test insurer, Example Health Plan, answers for synthetic members.
- FHIR R4
- CARIN Real-Time Pharmacy Benefit Check
POST/v1/fhir/r4/$process-messageLearn more about the Pharmacy Benefits API
Building blocks
The standards behind the services above, each useful on its own: who a provider is, what a code means, which form to ask, what a prescription's directions say.
Provider Directory API
Resolve an NPI to the practitioner behind it, find practitioners and networks in CMS's National Provider Directory, and find pharmacies in CMS's NPI Registry.
- FHIR R4
- CMS National Provider Directory
GET/v1/fhir/r4/PractitionerLearn more about the Provider Directory APITerminology API
Look up a code, expand a value set or validate a code against LOINC, RxNorm and ICD-10-CM, and get the standard FHIR answer back.
- FHIR R4
- FHIR Terminology Service
- LOINC
- RxNorm
- ICD-10-CM
BASE/v1/fhir/r4Learn more about the Terminology APIQuestionnaires API
Serve standard health questionnaires as FHIR, exactly as their source publishes them, and build a standard response in your own app.
Built with the Terminology API: the same LOINC support finds and reads LOINC's forms.
- FHIR R4
- SDC
- LOINC
GET/v1/fhir/r4/QuestionnaireLearn more about the Questionnaires APIStructured Sig API
Turn a prescription's free-text directions into a coded FHIR Dosage, with a review flag on anything a person should check.
Built with the Terminology API: the medication's dose form is read from the same RxNorm release the Terminology API serves.
- FHIR R4
- SNOMED CT
- NCI Thesaurus
- UCUM
- RxNorm
POST/v1/fhir/r4/$structure-dosageLearn more about the Structured Sig API
Medical Benefits and Pharmacy Benefits are the two halves of CMS's Real-Time Benefits use case. How Benefits fits together