Build on the Smart Health Network.
Smart Health Network is shared, neutral infrastructure for real-time health administration — one connection that reaches every authorized participant. Connect once, and reach every payer, provider, and patient on the network instead of building and maintaining a separate integration for each. We’re opening sandbox access to early participants, using synthetic data.
Why build here
Healthcare’s administrative transactions — prior authorization, eligibility, claims status — run on a tangle of point-to-point integrations, each with its own credentials, endpoints, and quirks. Smart Health Network replaces that with a single, standards-based connection to a neutral hub. The network handles identity, authorization, and a tamper-evident audit trail, so you can focus on your product instead of rebuilding plumbing for every counterparty.
- Connect once, reach everyone. One integration reaches every authorized participant on the network.
- Standards-based. Built on the FHIR and X12 standards your systems already speak.
- Neutral and governed. No payer or provider owns the network; the rules are public and the same for everyone.
- Patient-visible by design. Every request is recorded where the patient can see it.
What you can build
- Provider tools that submit prior authorizations from inside the clinical workflow, with documentation attached.
- Payer integrations that receive structured requests and return decisions in real time.
- Patient-facing experiences that show authorization status and a record of who accessed a person’s information.
- Coverage and eligibility checks, claims-status lookups, and the related administrative workflows that run alongside care.
Built on open standards
The network composes with the standards your systems already run:
- HL7 FHIR R4 with US Core
- Da Vinci CRD / DTR / PAS for the prior-authorization workflow
- X12 eligibility and claims-status transactions
Existing CMS-0057 and Da Vinci work is what makes you ready to connect. The network adds reach, not rework.
Two ways to integrate
Connect a gateway at your own edge, or implement the published protocol directly. Either way, onboarding is self-service and standards-based: register, prove control of your own keys, and you’re live on the network — no lengthy per-counterparty integration project.
Full integration guides, the SDK, the reference implementation, and the sandbox environment are shared with participants on access approval.
Who’s connecting
Payers, providers and health systems, EHR and health-IT vendors, and digital health developers — anyone preparing for the federal 2027 prior-authorization requirements and looking to do it once, on shared infrastructure, rather than one integration at a time.
What you can do in the sandbox
Run real prior-authorization workflows against synthetic data: submit a request with documentation attached, route it to a payer, return a decision, and see the patient-visible audit record — end to end, through the shared hub.