Connect without starting over.

You already have systems, workflows and partners. The first step is to identify how those can connect to the shared network — not replace them.

Start with one prior authorization

Bring a technical owner and one workflow. Use the Preview test environment to send a synthetic request, receive a response and follow its progress. You do not need a production agreement to begin.

For a health plan, the initial test does not require SHN software inside its production environment. For providers and partners, the starting point may be an existing EHR capability, your own interface or a tested workflow partner.

How will your system connect?

Your EHR, payer platform or workflow partner supplies the source information and receives the updates. The Gateway is the software that connects that system to SHN, applies required checks and protects the messages.

Choose a supported integration with the people who know the source system. Existing systems can stay in place, including on-premises systems where a supported connection is available.

Who will run the Gateway?

Your team can run it. You can select a qualified independent operator. Or you can purchase Managed Gateway from SHN.

Managed Gateway covers the deployment, maintenance, monitoring, support and recovery SHN agrees to provide. SHN is responsible for that service. All three operating choices retain the same applicable network rights.

What can be reused?

Carry forward working components, valid identity and security evidence, and relevant test results. Identify what remains specific to the new organization rather than repeating the entire process.

Agree who leads the implementation and who handles source integration, Gateway operation and the healthcare workflow. That makes the next question easier to direct to the right team.

What will it cost?

Designated Open Access exchange carries no SHN participation, network-access, transaction or required Gateway-software-license fee. Optional services are separate purchases and never a condition of included exchange. The included use cases are listed on the Open Access page; required status and records are included.

Integration, infrastructure and selected operating or software services may have separate costs. Review what is supplied before committing to the work.

Joining and implementation are separate

Becoming a Participant happens through the published Network Participation Agreement: application, SHN approval and countersignature, and acceptance of your Transaction Schedule scope. Operator choice, path qualification and production activation follow. No installation, operator appointment, roster entry or sandbox registration creates Participant status by itself. Review the Rules & Participation package →

From the first test to live use

Use the test to find the remaining work. Complete the security, permissions, integration, support and participation arrangements for the actual connection before sending live patient information.

Keep what works. Connect what is missing. Reuse the result.

Get Connected | October 2026 guide — Start with a test. Review the actual participation and service terms before live use or purchase.