Partner readiness
A working integration
is the starting point.
Tell us the service you provide and the exchange your customers need. We’ll define the supported capabilities and the evidence required to launch.
Share your organization, technical contact, vendor/platform, region, and intended workflow. Do not send patient records, credentials, or identity documents by email.
The path to production
- Verify the organization and workflow.
Confirm organizational ownership, technical and support contacts, region, vendor/site access, and the exact read/write destinations.
- Define the capability agreement.
Document resources, directions, pet mapping, consent, retention, commercial terms, and how access is withdrawn.
- Complete technical acceptance.
Prove authorization, exact delivery, correction/deletion, failure recovery, token rotation, and disconnect in the supported environment.
- Launch a limited pilot.
Enable only the approved application and capabilities. Confirm the source record and reviewed response at both real endpoints.
- Operate and expand.
Assign support ownership, monitor failures and sync lag, rehearse recovery, and certify additional capabilities individually.
Availability, stated plainly.
| Capability | Current availability |
|---|---|
| Synthetic source records and reviewed summaries | Runnable local developer preview |
| Native Connections foundation | Included in the recorded Build 44 release |
| Production partner onboarding / general OAuth | OAuth/PAR implemented and locally verified; production activation awaits acceptance |
| Real clinic, laboratory, insurer, pharmacy, retailer, or device adapters | Require vendor access, mapping, and adapter-specific certification |
| Registered webhooks / protected file exchange | Webhooks implemented and locally verified; protected files are a separate capability |