Laboratory Partner ServicesGuide
Partner Services isolated conformance and Sandbox runbook
Disposable persistence, version and privacy assertions, fixed Sandbox refusal and future genuine acceptance.
On this page
Availability and evidence boundary — October 25, 2026
Limitation
Laboratory Partner Services is source-only, NOT operational in Sandbox and NOT available in Production. Its staged database package is UNAPPLIED, the service gate remains off and prospective providers are not connected or verified. No partner delivery, clinical execution, invoices, payments or certification are enabled.
The laboratory-only Control Plane presents four separate sections: Explore Services, My Connections, Program Configuration and Activity. Read failures are unavailable evidence, not zero activity or successful requests. Source contracts, disposable persistence, genuine hosted identity, partner acceptance and publication are independent evidence classes.
Run only disposable acceptance
Install the SHA-pinned staged package in a disposable PostgreSQL instance after its prerequisites and hash checks. Use loopback PostgREST with synthetic signed role identities; no live schema, vendor endpoint, real account, patient data or hosted credentials are permitted.
Exercise preflight → apply → postflight, and empty-table rollback/reapply. This tests package custody locally; it neither authorizes a live installation nor establishes genuine hosted authentication.
Joined metadata sequence
A production-labeled disposable fixture can record one laboratory’s DTC/cash-pay introduction, replay/conflict, operator evidence transitions, authorized account metadata, exact Program version assignment, private B2B attribution and suspension/revocation history. Every step must read back from the same connection/assignment/referral records.
Verify grantsOrdering=false throughout, Lab B read/write denial, role/environment/version refusal, restricted private ledger, and no duplicate events for unchanged revoked children. Production-labeled fixture means state-policy test only, not a real service or clinical transaction.
Sandbox hard stop
The frozen package explicitly refuses Sandbox external_handoff_evidenced, partner/account/technical approval and approved assignments. A Sandbox request may reach operator_review, then only appropriate closure/refusal. Do not edit constraints to make the test artificially green.
Therefore the requested fully approved Sandbox joined service workflow is PARTIAL. No real collection booking, provider requisition, kit shipment, accession or released result is included in LPS metadata acceptance.
Negative compatibility and finance cases
Test Tasso incompatible device/specimen, implicit self-kit refusal, mobile geography mismatch, Speedy Sticks planned draw sites, unknown DOT legal identity and missing Supera assembly/inventory/outbound/return proof. Courier evidence never toggles accession or resultRelease.
Test stale evidence, provider impersonation, another Program/version, unknown packet fields, expired business consent, no signer custody, unsigned terms, missing conversion, terms/legal same reviewer, private cross-laboratory finance scope and immutable historical snapshots.
Future genuine hosted and browser acceptance
After separately approved package installation and Sandbox policy review, use genuine laboratory A/B/IT/operator identities; sign-in, sign-out/relogin, expiry, direct-table denial and cross-environment tests must run through the actual server boundary. Desktop/mobile tabs, keyboard forms and stale-read behavior need authenticated browser verification.
A named partner and laboratory must independently attest business consent/account ownership, approved Program/test/method/geography and technical/clinical evidence. Separate Partner API or R1 tests do not certify this LPS flow. Publication and Production activation require their own explicit approval.