Connect your Epic system in weeks, not quarters.
Two read-only paths feed one warehouse: Clarity extracts carry your billing and claims data, and a SMART on FHIR launch carries clinical context from inside Epic. Nothing writes back, and clinical and billing workflows stay untouched.
- Epic Clarity
- Read-only access to your Clarity reporting database or a scheduled export, no production write access.
- SMART on FHIR
- An OAuth 2.0 authorization-code launch, scoped to exactly what a session grants.
- FHIR R4 · US Core
- Resources validated against the same US Core profiles Epic’s own FHIR server publishes.
- Read-only, always
- Every path into Epic is read-only. 21st Care never writes back to the chart or the ledger.
Clarity carries the ledger. FHIR carries the chart.
Both are read-only. Both resolve to the same account spine, so a claim and the encounter behind it are never more than one join apart.
Epic Clarity
Billing & claimsClarity is Epic’s reporting database: charges, transactions, claims, and remits. We read it on a fixed schedule, from a reporting replica or a scheduled export your Epic analyst controls.
- Access
- Read-only reporting DB or export
- Cadence
- Scheduled, incremental
- Feeds
- Billing & revenue-cycle warehouse
- Charges, transactions, claims, and remits, table by table
- No changes to your production Clarity environment
- The same tables your existing BI team already reads
SMART on FHIR
Clinical contextA SMART on FHIR launch from inside Epic authorizes 21st Care to read the clinical resources that session grants: encounters, conditions, documents, and the authorizations that explain a denial.
- Access
- OAuth 2.0 authorization code
- Standard
- FHIR R4 · US Core
- Feeds
- Clinical context for the billing join
- Scoped to exactly what a launch grants, never broader
- No standing credential; access follows the session
- Joins to Clarity on the same account spine
From kickoff to your first trusted number.
A fixed, repeatable process. No custom data engineering, and no Epic build beyond what your team already maintains.
Kickoff & access
We sign a BAA and scope the extract: which Clarity tables and which FHIR resources your engagement needs. Your Epic analyst grants read-only access; nothing changes in production.
Extract & validate
Clarity data lands on a fixed schedule, and the SMART on FHIR launch is registered and tested end to end. Every figure is checked against your own reports before it reaches a dashboard.
Ask your data
Once the warehouse is live, your team asks questions in plain language and gets back charts and analysis, every number traceable to the Clarity table or FHIR resource it came from.
What a SMART on FHIR launch looks like.
The moment a user opens 21st Care from inside Epic, an OAuth 2.0 exchange runs in the background and hands 21st Care exactly the context that session grants.
Launch
A user opens 21st Care from a link inside Epic Hyperspace. Epic calls 21st Care’s launch URL with the FHIR server address (iss) and a one-time launch token (launch) that identifies the session.
Authorize
21st Care reads Epic’s SMART configuration and redirects the browser to Epic’s authorization server with its client ID, the requested scopes, and that same launch token.
Token exchange
Because the user is already signed into Epic, authorization completes without a second login. Epic redirects back with an authorization code, and 21st Care exchanges it for a short-lived, scope-limited access token.
Fetch & sync
21st Care calls Epic’s FHIR API with the access token, reads the resources the granted scope allows, and joins them to the same account spine as the Clarity extracts.
One user session, one OAuth 2.0 exchange, scoped to exactly what Epic grants.
Questions about the Epic integration
Yes. Any SMART on FHIR launch runs through Epic’s own app registration and security review, and your Epic team approves the exact scopes we request before anything goes live. Clarity access is separate: it’s granted directly by your Epic analyst and doesn’t require an app registration.
No. Every path into Epic, Clarity and SMART on FHIR, is read-only. Nothing in the chart, the ledger, or any Epic record changes because of 21st Care.
Most hospitals already grant Clarity read access to a reporting or business-intelligence team. We work with your Epic analyst to extend that same read-only access to 21st Care, or set up a scheduled export if a direct connection isn’t available.
It runs alongside the Clarity extract work, so it’s rarely the bottleneck. Timelines vary by health system; we scope the specific review your Epic team requires during kickoff.
Only the resources your engagement scopes, typically encounters, conditions, and the documents behind a denial. We request the narrowest scope that answers the questions you asked for, never a blanket read of the chart.
Connect your Epic system.
Bring your Epic analyst to a focused walkthrough. We’ll scope the Clarity tables and FHIR scopes your engagement needs, and show you the first numbers from your own data.