A 1health platform service

Ascension

Execute your BAA in-product, graduate to production, and activate the network ledger — cross-org patient matching unlocked, at no extra cost.

Ascension is the climb from sandbox to production — you execute your BAA against Treaty and rise into the network as a full party.

Turnkey ascension to production · BAA-covered in production

The graduation flow

Sandbox to production is a flow, not a negotiation.

The step that takes other platforms weeks of paperwork happens here in-product. Your integration doesn't change — your standing does.

Build in the sandbox

Register, get an isolated tenant and API key, and build against real platform behavior with synthetic data. Nothing you write here is thrown away.

Execute the BAA in-product

When you're ready for real data, the business associate agreement is presented, signed, and recorded inside the flow — a codified agreement through Treaty, not a PDF exchanged over email.

Graduate and activate

Your tenant is promoted to production and the network ledger switches on. Same code, same key model, new standing — you are now a party to the network.

The network ledger

Walls by default. Retractable by choice.

Every tenant is walled. Your patients, your records, your tenant — invisible to every other organization on the platform. Isolation is the default state, not a setting.
A wall retracts only by agreement. When two organizations choose to share, the ledger matches patients across the boundary — scoped to what the agreement between them allows, and nothing more.
Every crossing is recorded. Cross-org matches write to the audit ledger, so the answer to "who saw what, under which agreement" is a query, not an investigation.
$ ascension status
tenant: sandbox · ledger: off · walls: sealed
$ ascension graduate
BAA executed in-product  ·  recorded
tenant promoted to production
network ledger active  ·  walls sealed until you say otherwise
Why it's free

No toll at the door.

The network is the product. Every organization that graduates makes cross-org workflows — discharge handoffs, care transitions, readmission outreach — more useful for everyone already here.

So ascension carries no extra cost: you pay for what you build on the platform, not for becoming a party to it.

Composes with

One tile on the sidewalk.

Every platform service is built on the same canonical data model, so ascension's effects reach the rest of the platform by default.

Standing on it

The apps already walking on this tile.

Transitional Care Management — cross-org patient matching for 30-day episodes Discharge Carestreams — hospital-to-practice handoffs across tenant walls Readmission reduction — outreach that follows the patient across organizations
FAQ

Straight answers.

What does ascension mean on the 1health platform?

Ascension is the climb from sandbox to production. The agreements themselves are managed by the Treaty service; ascension is the flow where you execute your BAA in-product, graduate to production, and become a party to the network's shared agreements.

What is the network ledger?

The network ledger enables cross-organization patient matching. Every tenant is walled by default — nothing is shared. A wall retracts only when the organizations on both sides choose it, and only to the extent their agreements allow.

Why is ascension free?

Because the network is the product. Every organization that graduates makes cross-org workflows more useful for everyone already on the platform, so there's no toll at the door. You pay for what you build, not for joining.

Your sandbox is one flow away from the network.

Turnkey ascension to production. BAA-covered in production.