Lab Adapter Framework

Laboratory adapters connect vendor- or protocol-specific systems to canonical Solia orders, specimens, results and events. The canonical records stay independent from the transport, and an adapter never becomes a second order or result source.

Adapters declare versioned capabilities. Support is proven by the declared capability and current evidence, not inferred from a protocol label.

• Order capabilities may cover creation, update or cancellation where implemented.
• Lifecycle capabilities may cover acknowledgement, accession and specimen status.
• Result capabilities may cover final and corrected result return where implemented.
• An unknown, absent or unsupported capability fails closed and is never advertised as available.

• Adapter configuration, environment, validation state and health are evaluated together.
• Sandbox and Production adapters and credentials remain separate.
• Synthetic conformance proves contract behavior with test data; it is not Production validation and cannot satisfy a Production gate.
• A Production capability is used only when current Production configuration, validation and health evidence prove it.

• Solia HTTPS/JSON — executable self-service transport.
• HL7 v2 — managed integration path where applicable; a request does not by itself create a live adapter.
• FHIR — managed integration path where applicable; a request does not by itself create a live adapter.
• SFTP / file — managed integration path where applicable; a request does not by itself create a live adapter.
• Vendor or system-specific mapping — managed integration path where applicable; a request does not by itself create a live adapter.

Collection adapters and providers are separate from laboratory order/result adapters. A mobile collection provider is available only where that laboratory, offering, region and configured mode support it; no provider is universal.