⌘K

Laboratory EngineeringGuide

Integration troubleshooting & practical FAQ

Diagnose missing authority, rejected correlation, private pricing and unreleased results without unsafe workarounds.

On this page

Catalog and Program cases

  • Empty Program Catalog / no grant: verify current client, Program, laboratory and environment through the existing Program owner. Published network discovery does not fill an authorized catalog.
  • Missing native code / stale compendium revision: hold the row; reimport/review the exact version, never match by display name or reuse an older approval.
  • Wrong lab or environment / expired or revoked key: stop requests and restore correctly scoped authority. Never borrow another Program key.
  • Future capability / unpublished or private price: keep nonorderable/Quote required; obtain explicit publication and safe price visibility, not DTC price substitution.

Wire and callback cases

  • 409 / timeout / unknown ACK: reconcile under the original transmission identity, no automatic resend; confirm application acceptance with lab IT.
  • Rejected sample versus kit: inspect exact specimen/kit/panel/accession correlation. An individual rejection does not reject the whole kit.
  • Webhook signature failure / replay: verify current canonical signing contract, bounded timestamp and deduplication using the existing webhook guide; reject unverified input rather than turning verification off.
  • Vendor status unknown / FINAL or CORRECTED unapproved: keep PENDING_CLINICAL_REVIEW/unreleased. Synthetic status mapping is not vendor evidence.

Results and installation cases

  • Result not visible: verify it belongs to your current Program and has an authorized released revision. A received/critical/final-looking result alone is not released.
  • No native installation authority: remain at draft configuration/synthetic tests; do not start an Edge listener or invent a registry. Core owner approval is required.
  • Reference send-out requested: REFERENCE_NOT_ENABLED; compatibility metadata never executes a route.
  • Failed evidence refresh: unknown/not ready; obtain a fresh authorized read, do not show the last pass as current readiness.

Safe escalation record

  1. Capture only the authorized environment, bounded non-clinical identifiers, revision and observed refusal/unknown state. Never export keys, clinical free text or another tenant’s records.
  2. Use existing workspace support and laboratory owner destinations. Describe transport evidence separately from lab acceptance/release.
  3. Assign lab IT for vendor semantics, clinical reviewer for mapping/release, Core owner for installed authority and security/ops for custody/replay. Keep missing telemetry explicitly unknown.

Related resources