Integration GuidesGuide
Sandbox to Production
What carries forward, what stays environment-specific, and how Production is validated.
What carries forward
- Your integration code, request shapes and endpoint paths.
- Safe laboratory configuration continuity inside the paired workspaces, where the platform supports it.
- Your understanding of scenarios, errors and reconciliation.
What stays environment-specific
- API keys, webhook subscriptions and signing secrets.
- Program identifiers and grants — a Production Program is promoted and granted separately.
- Laboratory adapters, endpoints and credentials.
- Orders, customers, results, events and delivery history.
Production connection and validation
- Laboratory configures its Production adapter, endpoint and credential and passes the Production connection test and validation run.
- Commercial eligibility is satisfied separately; it never substitutes for technical evidence.
- When separately authorized release authority is available, the server re-derives every gate before activation. Production promotion is currently paused; finishing this checklist cannot bypass it.
- The laboratory promotes the Program, grants your client and issues a Production key with MFA step-up.
- Register a Production webhook separately. Any external order/result rehearsal requires explicit laboratory, clinical and security approval; metadata-only checks never submit a clinical order.
Important
Sandbox evidence never satisfies a Production gate.