Wasatch Behavioral Health
CMS API Developer Portal
APIs built under the CMS Interoperability Final Rules.
Patient Access API
SMART on FHIRFor consumer applications that a patient logs into and authorizes to see their own records, using SMART App Launch (authorization code + PKCE).
For Developers
Getting Started
Learn about the FHIR R4 API, supported profiles, and the SMART on FHIR authorization flow.
Read the DocsRegister an Application
Submit your application for review. Approved apps receive a
client_id for the SMART on FHIR authorization flow.
Supported Scopes
Browse the SMART v2 patient-context scopes supported by this API, including clinical, claims, and formulary resources.
View ScopesFor Patients
App Directory
Browse applications that have been approved to access the Patient Access API.
Browse AppsRegister a Patient
Set up patient portal access. Registration requires an in-person visit and a Microsoft EntraID account.
Get StartedProvider Access API
SMART Backend ServicesFor backend systems connecting on behalf of a provider organization — no end-user login. Access uses OAuth 2.0 client credentials and is scoped to patients attributed to the organization's NPI.
For Developers
Getting Started
Learn about the client credentials flow and how per-patient attribution is enforced.
Read the DocsRegister an Organization
Submit your provider organization's NPI for review. Approved organizations receive confidential-client credentials.
RegisterProvider Directory API
Public, No Auth RequiredPublic plan network directory data — organizations, practitioners, locations, and their network affiliations. No registration, authorization, or API key is required to read it.
For Developers
Getting Started
Learn how to query the directory — no registration or authorization step required.
Read the Docs