Laboratory EngineeringGuide
Nexus-shaped synthetic conformance walkthrough
Understand the actual candidate wire tests and the unresolved vendor acknowledgement and callback contract.
On this page
Synthetic candidate, not official vendor API
The isolated candidate uses bearer-authenticated POST /api/v1/order against a loopback HTTP peer. It is not an official Nexus API reference, approved staging interface or permission to contact Nexus. Real schema, native codes, credentials, provider fields and callback policy require Nexus IT confirmation. No nested vendor request template is endorsed here.
Request mapping checks
- The candidate orderNumber carries the kit barcode, not the canonical Solia order ID. The panelOrderCode carries the reviewed laboratory-native code.
- The real loopback peer inspects the actual bearer header and JSON produced by the shared declarative executor, with separate synthetic lab A/B configurations.
- Canonical order identity and specimen/accession correlation remain separate. A synthetic native code is not evidence of a real menu or approved mapping.
Transport and reconciliation
- A 201 response means transport SENT only; an unknown response field cannot become application ACK.
- A 409, timeout or ambiguous post-send outcome requires reconciliation under the original identity, without automatic resend or a replacement order.
- 401/403 credential refusals and invalid request/scope errors are test failures to diagnose, not permission to weaken validation.
- Obtain explicit vendor application acceptance/rejection evidence before declaring an order accepted. Unknown ACK stays unknown.
Receipt, rejection and results
Authenticated bounded synthetic callback transformations check exact kit/panel/specimen/accession correlation. Sample rejection is not whole-kit rejection; Boolean strings need an approved profile rule. An unverified identity/signature, replay or correlation drift refuses/quarantines the candidate input.
Important
Unknown Nexus FINAL/CORRECTED semantics produce PENDING_CLINICAL_REVIEW and remain unreleased. Translator events are pure transformations, not durable candidate Core ingest or clinical sign-off.
What 29 tests establish
The Prompt4 29-test suite joins draft intake/reimport/raw-header review to two independent loopback HTTP peers with a shared executor. It proves bounded candidate wire and translation/refusal behavior in isolation. It does not prove a single Nexus request/callback transaction persisted through canonical release.
A separate approved SYNTHETIC NON-NEXUS test uses disposable PostgreSQL/PostgREST: two buyers POST orders, canonical ACK and FINAL then CORRECTED are processed, staff-authorized release occurs and scoped Partner GET succeeds with cross-buyer denial. Its 7/7 proof must not be relabeled Nexus conformance.