Operator onboarding & go-live inputs

Use the existing six-step laboratory journey, not a second onboarding system. Preparation, mapping drafts, synthetic Sandbox evidence and documentation do not publish a laboratory, start billing or authorize real interface traffic. Native installed authority is absent and promotion remains paused.

• Founder/operator: laboratory organization identity, authorized business owner, selected channels, sanctioned test scope and commercial agreement.
• Lab IT/Nexus IT: sanitized compendium and interface documentation, native codes/panel composition/specimens, method/performer identity, approved endpoint ownership and authentication lifecycle.
• Lab IT + security/ops: secret custody reference (never value in docs), TLS/certificate/IP allowlist, callback authentication/signature/rotation, ACK/rejection semantics and replay/idempotency/timeout reconciliation.
• Clinical reviewer: current component/LOINC/UCUM/role/specimen/method mapping, constrained alternative justification, completeness/correction/critical/provider/release policy and witnessed sign-off.
• Core owner: canonical installed laboratory/environment authority, reviewed version storage and approval of any required persistence change. This public guide grants no SQL execution permission.
• Shamil: source/test evidence boundaries, independent lab profile reuse, approved acceptance plan, unresolved issue ownership and exact release artifacts.
• Commercial/launch owner: separately verified business/payment/subscription evidence and deliberate Production authorization; payment alone does not make the lab live.

1. Collect dictionary/interface inputs and confirm owner authority; missing code/specimen/vendor policy is a stop.
2. Review immutable mappings/profile versions; rich unsupported fields stay draft. No cross-lab scope or wholesale price exposure.
3. Run authorized synthetic test evidence in the intended environment. Separate wire, disposable persisted and genuine hosted evidence.
4. Obtain installation, clinical, security and vendor approvals independently. No approved live native registry means NO-GO.
5. Re-read current technical and commercial gates; respect platform-paused promotion. Do not infer eligibility from a remembered pass.
6. Authorize real traffic and publication only through existing canonical launch controls and explicit laboratory action after all required approvals.

Before any separately approved future rollout, record current source/config revision, authority scope, owner and operator-approved rollback. Stop dispatch on uncertainty, preserve pending evidence and reconcile without resend. Pausing retains configuration; rollback of code is not permission to erase clinical history or release results.