January is coming. Start testing now.

You do not need to wait for a production agreement to find out how the connection works.

Bring one prior-authorization workflow. Test a request, a response and the status you need to follow it. Use the results to identify what can be reused and what still needs work.

One workflow is enough to begin

Health plans: name your CMS-0057 or interoperability technical lead. Arrange access to the test API and run a synthetic prior authorization. The first test does not require SHN software inside your production environment.

Providers: bring your EHR or workflow technical contact. Start through a supported EHR connection, your own integration or an existing workflow partner.

HIEs and technology partners: bring one service, customer connection or workflow that can help others participate faster.

States: bring the people doing the work — Medicaid, insurance, plans, providers and technology partners — into a shared readiness discussion. You do not have to wait until everyone can test.

Choose a test environment

Preview test environment (shn-preview.org): try supported requests and responses in the cloud without installing a local Gateway.

Local reference software: explore Gateway configuration and integration in an environment your team controls.

The developer resources contain the current access instructions, versions and examples.

Test together. Reuse the result.

Bring a test already on your implementation plan. Where the same test can meet the same requirement for more than one connection, agree how to reuse its result instead of repeating it.

Record what worked, the systems and versions involved, and the questions that remain. Share the relevant findings at a readiness session so another team can benefit.

Testing is the start, not another commitment barrier.

Testing uses synthetic data — fictitious patient information, not copied patient records. Production agreements, security reviews and operating arrangements can proceed alongside the testing work. Live use begins when the particular workflow and participating systems are ready.

Use only synthetic data. Do not send real patient information, passwords or production credentials.

Last updated: September 2026