Start testing today
Run realistic prior-authorization workflows on synthetic data today. No negotiated participation agreement is required for sandbox testing; standard test-environment registration and terms apply. Testing is how you start; it doesn’t obligate you to anything.
Two ways to test
No local infrastructure; self-service client registration; synthetic data only. Validate CRD/DTR/PAS construction against the available test routes.
- Register an API client (self-service)
- Discover authentication metadata
- Obtain a token
- Send CRD/DTR/PAS requests
- Verify the expected results
Prove deployment: run the gateway in your environment — keys generated and retained locally — connect the EHR or payer sandbox, and validate full EHR/payer → gateway → hub routing and conformance.
- Request developer access
- Register a provider client
- Run the evaluation bundle
- Connect the EHR sandbox
- Execute and verify
Many teams do both: cloud first to prove the requests, local second to prove the deployment.
Synthetic data only. Do not submit PHI, patient or member information, passwords, private keys, access tokens, or production secrets. All test routes are preview/synthetic environments — no production endpoints. Cloud sandbox registration is self-service; local developer-environment access is a moderated step and is not instant.
How production connection works — Get Connected → · Download the two-pager (PDF) →
Request construction · network routing · conformance against the pinned profiles · endpoint behavior on the test routes · readiness evidence for the production process.
Regulatory compliance · production authorization · production identity · operational readiness · participant status. Production participation requires executed agreements, organization-authorized production credentials, and completed capability and launch checks.
I'm a provider or health system
Keep your EHR. Connect through your FHIR server, your EHR’s native Da Vinci API, or a SMART on FHIR application — using a gateway you host or SHN hosts. Nothing deploys in your production environment to begin testing — most teams start in the cloud sandbox.
The richest data path — and it reduces dependence on the EHR vendor’s native timeline.
The workflow stays entirely in the EHR, where your clinicians already work.
From the EHR marketplace — the broadest interim path for certified-EHR providers, subject to supported SMART capabilities and marketplace policies.
All three paths terminate at the same standard gateway interface — using a gateway you host or SHN hosts.
I'm a payer
Keep your CMS-0057 implementation. The network adds the shared distribution route into it. Give SHN access to the synthetic-data test endpoint you’re building for CMS-0057, name one engineer, choose one workflow — and certify once: reachable by every provider on the network. Endpoint details are collected later over the secure channel, never by email or form.
payers@smarthealthnetwork.org → · Plan payer participation →
I'm an EHR, HIE, RCM, or integration partner
Run the same two pathways on behalf of your customers — multiple test clients, readiness evidence, and certification intake. Architecture, protocol, SDK, and reference code are public; test credentials require standard registration. Certification demonstrates capability for a specific job and qualifies your organization to compete for that work.
partners@smarthealthnetwork.org → · About the partner program →I'm a state
Bring payer and provider test participants, request the four-action state commitment package, and schedule a state working session — or host a satellite site at the October 14 national Connectathon.
1 — Join · 2 — Activate the Market · 3 — Connect State-Sponsored Health Plans · 4 — Accelerate Provider Adoption (optional — RHTP states)
I build patient-facing applications
Help design the patient layer. Join the Consumer App Design Group shaping the patient activity model, authorization pattern, and app trust framework. Current status: design collaboration; synthetic-data testing only.
partners@smarthealthnetwork.org →I'm a developer
Docs, sandbox, pinned versions, invariant tests — no NDA, no sales call. Create a free developer account and download the Local Test Kit — the standardized workflow running on your laptop, in minutes. A reference implementation for testing, not the deployment path.
Create a free developer account → download the Local Test KitNot the technical lead? Forward this page to your integration team and schedule a working session.