Monitoring

• Integrations → Activity & logs for integration and delivery outcomes, scoped to the selected environment.
• Overview for canonical deployment state and anything needing attention.
• The event stream for reconciliation from an API integration (internal system or external partner).
• The public status site reports platform-wide read-only availability checks and scheduled-worker evidence, plus published incidents. A healthy probe or recent worker run is not proof that a particular order, result, webhook or laboratory transmission completed successfully. Unavailable or unmeasured signals are labelled explicitly; workspace-specific integration health remains in Integrations and Overview.

Start in the correct workspace and Sandbox or Production environment. Overview and connection health summarize the canonical evidence available to that scope; Activity and logs provide the corresponding integration/delivery outcomes. A Sandbox success is not included as a Production acceptance fact.

• Read the observed timestamp, error and next action rather than assuming a remembered healthy state is current.
• Missing, failed or refreshing reads mean unavailable or incomplete, not healthy. Refresh once, inspect the safe failure and escalate if current state still cannot be read.
• A successful availability/contract check does not prove a particular clinical transaction reached the laboratory or was released.

Accessioned means the LIS assigned or confirmed an authorized accession linked to the original order/specimen. Only supported correlated application evidence establishes acceptance or rejection. Released means the canonical authorized release completed; receiving a result is not release.

• Queued means work is recorded for delivery; it does not mean an outbound request completed.
• Transport receipt records the transport outcome. HL7 CA is commit acknowledgement; only AA is application acceptance. CE/CR and application rejection require their own handling.
• Application acceptance, accession and specimen acceptance remain separate evidence. Result receipt is not final clinical release; final/correction versions and quarantined outcomes require canonical disposition.
• Preserve the original correlation when a delivery is unknown. Disabled native paths suppress uncertain automatic resends; executable HTTPS/JSON still has a classified-retry safety gap, so there is no universal non-resend guarantee.

Use Overview attention and order exceptions to locate canonical blockers such as missing mappings or specimen/result problems. Backlog and delivery status must be read from the current scoped records; an attention item is not proof that an automated alert was sent or that an incident is already assigned.

• Open the affected order, connection or delivery and capture safe identifiers, environment and observed time.
• Route mapping/clinical exceptions to the laboratory reviewer, endpoint/authentication failures to authorized laboratory IT and delivery reconciliation to the integration operator.
• Do not clear an exception by changing display text. Resolution must be recorded through the supported canonical workflow and read back before claiming recovery.
• Role-gated acknowledge, resolve, reprocess, retry or release controls exist only where canonical policy permits. For expired/revoked credentials or endpoint refusal, use supported authorized containment; disabled native suspension is not an established operational service. Preserve the journal and reconcile ambiguous orders before any resend.

Webhooks → Delivery logs describes event delivery attempts in the selected environment. Confirm endpoint, event/delivery identifier, response outcome and any recorded retry/disposition before taking an authorized action. A receiver's successful HTTP response does not prove downstream clinical work completed.

Verify the signature against the exact raw bytes and timestamp before processing. Use durable atomic event deduplication with processing outcome recorded together; signature freshness alone is not replay prevention. Reconcile with authorized order/result/event reads after delayed or duplicate delivery rather than creating a replacement order.

• A gateway readiness probe proves a service is running, not an external LIS is certified or accepting orders.
• A saved adapter or credential flag is not an authenticated Production API smoke test.
• Two Programs in one tenant do not prove reuse of one independently approved LIS installation.

The public status site measures platform probes and recorded worker evidence, not laboratory-specific delivery latency, clinical acceptance or vendor certification. No automatic backlog/clinical alert, on-call assignment or successful reconciliation is implied unless that outcome is actually recorded.

For an unresolved read or ambiguous send, preserve safe request references and journal metadata, stop risky follow-up through supported operator controls and escalate to the owner. Do not share clinical payloads or credentials, rotate keys speculatively, resend an uncertain order or activate a disabled native worker.