ReferenceReference
Public changelog
Verified Solia Direct platform and API releases from October 3, 2026 forward.
On this page
- Current state
- 2026-11-15 — Documentation reconciliation and Sandbox guide routing
- 2026-11-11 — Control Plane navigation and Service Partners presentation
- 2026-11-11 — Reference Network R2: recorded hosted Sandbox acceptance
- 2026-11-10 — Optional DTC: private preview, inherited branding and governed publication
- 2026-11-09 — Operational Overview and laboratory member access
- 2026-11-08 — Laboratory connection validation and profile-aware readiness
- 2026-11-08 — Catalog, Fulfillment and internal Sandbox testing
- 2026-11-07 — Native Sandbox dispatch authority and safety corrections
- 2026-10-27 — Developer artifact reproducibility and rollback safety
- 2026-10-26 — Laboratory interoperability safety (LIH-01) engineering source delivery — NOT Production
- 2026-10-25 — Laboratory Partner Services engineering source closeout — NOT Production
- 2026-10-25 — R1 Reference & Send-Out Testing engineering source delivery — NOT Production
- 2026-10-25 — CA-READY and ULC-CAT-01 engineering source delivery — not Production
- 2026-10-25 — Expanded laboratory integration testing — source delivery, not Production
- 2026-10-19 — Laboratory connectivity source delivered — connectors not certified, native runtime disabled
- 2026-10-03 — Laboratory onboarding, connectivity and Production readiness
- Future entries
Current state
The public changelog records verified platform and API releases from October 3, 2026 forward. Earlier development history is not reconstructed.
Limitation
Entries distinguish verified releases from explicitly labelled source delivery. Source-delivery records are not Production releases or vendor certification. Entries appear newest first and state affected surfaces, breaking changes and required action.
2026-11-15 — Documentation reconciliation and Sandbox guide routing
Reconciles November workflow guidance, current navigation, optional DTC preview and branding, Service Partners, invitations and release evidence. Public guides use universal laboratory examples and include six-step onboarding, evidence-based completion criteria and safe continuation while awaiting laboratory responses. Restores the Sandbox article on the documentation host while preserving application onboarding. Historical releases remain dated evidence; this documentation release does not enable clinical services or Production.
- Release: 2026.11.15-documentation-reconciliation
- Affected surfaces: Documentation
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-11-11 — Reference Network R2: recorded hosted Sandbox acceptance
Adds directional bilateral relationships, governed menus/mappings/private terms, canonical reference routing, custody/accession and correction lineage. The November 11 acceptance record documents a synthetic hosted two-laboratory workflow and isolation checks. Production reference execution remains off; synthetic acceptance is not a named laboratory certification or completed vendor POC. Endpoint and event counts remain unchanged; reference execution metadata is documented in the existing contract.
- Release: 2026.11.11-r2-reference-network-sandbox
- Affected surfaces: Control Plane, Partner API, Laboratory Integration, Documentation
- Breaking changes: None
- Action required: Review reference-route eligibility and execution metadata in the existing API contract. Production and laboratory-specific acceptance require separate evidence.
2026-11-10 — Optional DTC: private preview, inherited branding and governed publication
Merged source delivers a first-visit derived laboratory preview, optional saved customization, website-brand suggestions with explicit acceptance, preserved overrides, consumer eligibility explanations, Appearance/Test menu/Launch controls and revision-checked publication. The current full private preview is platform-owned and uses the same storefront composition. No automatic Program creation or public launch occurs on viewing. Native patient sessions and live checkout remain unavailable pending separate verified capabilities.
- Release: 2026.11.10-d2c-preview-branding-source
- Affected surfaces: Standard DTC, Control Plane, Documentation
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-11-09 — Operational Overview and laboratory member access
Merged source aligns owner/Admin operational projections, scoped metrics, attention navigation and unavailable-state handling. Laboratory staff member names can be edited and invitation account entry uses normal authentication for the intended email. Invitation requests do not prove inbox delivery or acceptance; Health Company membership is a separate flow.
- Release: 2026.11.09-overview-members-source
- Affected surfaces: Control Plane, Security, Documentation
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-11-08 — Laboratory connection validation and profile-aware readiness
Merged source refines Step 5 configuration/order/status/result progress, installation and transaction reuse, secure technical contribution, canonical acceptance and safe wait/resume/reconciliation. Step 6 pre-readiness and connection packages follow the selected profile. Source, installed authority, runtime bindings and external laboratory acceptance remain separate; HTTP success, internal tests or technical attestation do not complete Step 5 or authorize Production.
- Release: 2026.11.08-lux-s6ux-source
- Affected surfaces: Laboratory Integration, Control Plane, Security, Documentation
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-11-08 — Catalog, Fulfillment and internal Sandbox testing
Merged source refines shared file/manual catalog drafts, provenance and exact-code reimport, effective collection/service-area restrictions, explicit kit assignment, readback/recovery, and explicit internal test preparation/run with retained progress. Catalog drafts do not establish clinical equivalence; internal test success does not prove an external laboratory connection. No provider integration is activated by these UI and contract changes.
- Release: 2026.11.08-cux-fux-tux-source
- Affected surfaces: Control Plane, Laboratory Integration, Documentation
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-10-27 — Developer artifact reproducibility and rollback safety
Merged source corrects generated documentation artifact drift and preserves identifier state through collision-safe rollback. This engineering correction is not a migration installation, vendor acceptance or Production release.
- Release: 2026.10.27-docs-artifacts-rollback-source
- Affected surfaces: Documentation, Security
- Breaking changes: None
- Action required: No Partner API operation or webhook changes. Existing authorization and Production gates remain in force.
2026-10-26 — Laboratory interoperability safety (LIH-01) engineering source delivery — NOT Production
Source-only delivery, not an availability announcement. Adds issuer-qualified patient identifier matching with review and quarantine, capability-governed FHIR R4 Patient lifecycle, a documented flat REST payload contract, separation of transport receipt from laboratory application acknowledgement, no automatic resend after an uncertain send, authenticated and correlated callbacks, explicit preliminary/final/corrected result lineage, and governed native-code mapping without invented terminology. Database packages remain UNAPPLIED, native transports remain disabled and evidence is synthetic only; 14 of 40 original rules remain not run. No vendor interface is certified.
- Release: 2026.10.26-lih01-interoperability-safety-source
- Affected surfaces: Laboratory Integration, Security, Documentation
- Breaking changes: None
- Action required: None. No Partner API operation or event changes.
2026-10-25 — Laboratory Partner Services engineering source closeout — NOT Production
Source-only LPS delivery: laboratory-only four-tab workspace, versioned staged connection/assignment audit contracts, private operator-assisted packet and manual commercial evidence models, and read-only canonical compatibility. The database package remains UNAPPLIED and the service gate is off; all provider verification facts remain false. Disposable metadata persistence is not a complete approved Sandbox workflow, genuine hosted authentication, partner delivery or clinical execution. No commission calculation, invoices, payouts, deployment or publication is enabled.
- Release: 2026.10.25-lps01-engineering-source-closeout
- Affected surfaces: Control Plane, Laboratory Integration, Security, Documentation
- Breaking changes: None
- Action required: None. No Partner API operations or webhook changes; live Partner Services remains unavailable.
2026-10-25 — R1 Reference & Send-Out Testing engineering source delivery — NOT Production
Source-only delivery, not an availability announcement. Adds a Reference Testing destination to the laboratory Control Plane with seven sections that show "configuration pending" and disabled actions with reasons, plus bilateral relationship, Program binding, reviewed-mapping, price-privacy, referral-order, custody and FINAL/CORRECTED source contracts. Staged database packages remain unapplied, both reference gates are off, no native registry or clinical mapping authority exists, and a joined same-order sender-to-performer result chain remains PARTIAL. Not published until independently observed.
- Release: 2026.10.25-r1-reference-sendout-engineering-source
- Affected surfaces: Control Plane, Laboratory Integration, Documentation
- Breaking changes: None
- Action required: None. No Partner API endpoint or event changes; Reference Testing cannot be used yet.
2026-10-25 — CA-READY and ULC-CAT-01 engineering source delivery — not Production
Source-only engineering and documentation delivery, not an availability or vendor-certification announcement. All four ULC-CAT-01 source prompts supplement the CA-READY 72-slice record. Owner-supplied independent selected release-critical CI passed 1,632/1,632 tests in 96 files, zero failures/skips, with locked TypeScript and production build passing; Prompt4 synthetic acceptance passed 29/29 and separate real disposable PostgreSQL/PostgREST two-buyer acceptance passed 7/7, with integrated acceptance 24/24. This is not the entire historical broad suite. Candidate laboratory draft/wire/callback tests are NOT one joined canonical persisted transaction. Advanced rich intake remains draft-only, native installed authority is absent, clinical/vendor approvals remain open and Production promotion is paused. No external laboratory or vendor interface has been certified. These documentation revisions remain source until independently observed published.
Compendium and clinical review
Versioned intake/reimport, raw-header safety holds, immutable connector profiles and reviewed full-component equivalence contracts are documented; source Live status, names and biomarker overlap never authorize Production or clinical substitution.
Independent Programs and discovery
One laboratory installation remains separate from each buyer's credentials, Program and catalog/result/webhook scopes. Exact per-laboratory grants and public-safe network price rules do not create new ordering authority; reference/send-out remains disabled.
Evidence and operational handoff
Practical architecture, conformance, results/reconciliation, onboarding and troubleshooting guides distinguish source, loopback, disposable persisted and hosted verified evidence. U15 remains PARTIAL; U16/U17 PASS_ISOLATED, U18 PASS_CI for the supplied selected run and U19 PASS_SOURCE. Live Core, vendor, clinical and security approvals remain separate.
- Release: 2026.10.25-ulc-cat01-engineering-source-closeout
- Affected surfaces: Laboratory Integration, Partner API, Control Plane, Security, Documentation
- Breaking changes: None
- Action required: None for current partners; no breaking API changes. This source closeout does not deploy, enable Production or authorize vendor traffic.
2026-10-25 — Expanded laboratory integration testing — source delivery, not Production
Source-only engineering update, not an availability or vendor-certification announcement. Native REST, FHIR R4, HL7 v2/MLLP and SFTP integration components include an explicitly started MLLP inbound result listener and controlled SFTP poller; both are disabled for Production until separately authorized. A real HTTP Partner API test with disposable Core and PostgREST verifies two scoped synthetic buyer identities and a result ingested, clinically evaluated and released through canonical test authority. Release-critical isolated CI passed 1,455 automated tests. The complete same-order Partner API POST to LIS to Partner API result GET lifecycle and a fully installed, live managed Gateway/Edge authority remain unverified. No external laboratory or vendor interface has been certified.
Clinical transport
Inbound MLLP acknowledges only persisted canonical results or duplicates; SFTP archives only after confirmed commit and retains uncertain files for reconciliation.
Security and authorization
Independent HTTP tests enforce distinct buyer/Program grants, tenant isolation, revoked and expired key refusals and canonical result release.
Quality and handoff
The engineering source has an evidence-based 72-slice closeout, migration operator review package and technical-lead/laboratory handoff. CI results are not a Production or laboratory go-live authorization.
- Release: 2026.10.25-ca-ready-isolated-source-verification
- Affected surfaces: Laboratory Integration, Partner API, Control Plane, Security, Documentation
- Breaking changes: None
- Action required: None for current partners. Native LIS paths remain disabled and subject to laboratory and Core-owner approvals.
2026-10-19 — Laboratory connectivity source delivered — connectors not certified, native runtime disabled
Source delivered (October 4–19), not a Production release: native REST, FHIR R4, HL7 v2/MLLP and SFTP/file adapters, a standalone gateway and an outbound-only Edge agent are implemented and tested only against locally hosted synthetic servers; their runtime switches remain off and no installation is approved. Clinical safety in disabled native REST/FHIR source paths: uncertain post-send outcomes are delivery unknown and never automatically resent. The executable HTTPS/JSON worker retains classified retries, including a retryable refused sent-state write; this unresolved gap is not covered by the native guarantee; HL7 CA is commit-only and CE/CR are rejections; result status and corrections are versioned. Onboarding: Step 5 records the laboratory system as identified (not configured), supports immutable mapping drafts with independent review, and hands technical details to laboratory IT; Step 6 separates technical readiness from business activation and fails closed on stale reads. Security: IPv6-mapped SSRF classification, bounded response reads and gateway key-file custody were hardened. Documentation published at docs.soliadirect.com: release-status, LIS onboarding, onboarding roles/Step 5/Step 6, acknowledgement lifecycle and post-live Partner API pages; Production readiness no longer describes activation as self-serve. Subsequent source corrections require hosting propagation and a fresh publication check. Production promotion remains paused. No vendor or laboratory connector is certified; installation authority in Solia Core is pending.
Engineering delivery
Native REST/FHIR, HL7 v2/MLLP and SFTP/file source, gateway packaging and outbound-only Edge are locally tested with synthetic peers. Runtime switches remain off; installation authority and vendor certification are not supplied by those tests.
Founder and laboratory IT
The existing six-step journey distinguishes identified LIS, managed request, bounded dictionary preview, independent reviewer approval and technical readiness. None grants Production activation or starts commercial billing.
Partner API and notifications
Generated endpoint reference, single-version base URL composition and Postman resources follow the versioned contract. Subscription selection uses the nine canonical Partner events; Experience notifications remain a separate contract.
Clinical transport evidence
HL7 CA is commit acknowledgement, AA application acceptance; accession, specimen acceptance and clinical release remain separate. Native uncertain post-send outcomes suppress resend. HTTPS/JSON retains classified retries and a retryable refused sent-state write: source review does not certify this gap safe.
Technical documentation
Architecture, Core review-package ordering and rollback, protocols, role boundaries, incident reconciliation and first/second-site certification plans have source documentation. Private SQL/authority evidence stays outside public guides.
Release and publication
This is an October 19 source and technical-documentation update, not a shipped Production LIS connector. Full regression is not green; authenticated founder/IT acceptance, Core installation, hosted infrastructure, clinical/security approval and real vendor evidence remain pending. These final revisions are not verified published.
- Release: 2026.10.19-source-delivered-connectors-not-certified
- Affected surfaces: Laboratory Integration, Control Plane, Partner API, Security, Documentation
- Breaking changes: None
- Action required: None for HTTPS/JSON laboratories or Partner API integrations. Laboratories wanting a native connection must supply the inputs listed under Release status.
2026-10-03 — Laboratory onboarding, connectivity and Production readiness
Catalog: test creation and bulk import share one creation path that preserves biomarkers, price, fasting, preparation and consumer description, and every test receives a stable routing slug; nothing is published automatically. Fulfillment: tests inherit the laboratory's effective collection methods and service areas and can only narrow them, self-collection kits apply only when explicitly enabled, method changes save atomically and keep collection modes consistent, scheduling and time zone are shown only from recorded evidence, and Fulfillment Production readiness now takes part in the final launch and publication gate. Sandbox: synthetic Sandbox orders show coherent order, result and release states with truthful scheduling and transmission presentation. Laboratory connection: a simplified Connect your laboratory journey with a connection package and managed integration workflow; the Solia Test Laboratory remains the Sandbox proof path, HTTPS/JSON is the executable transport, and HL7 v2, FHIR and SFTP/file remain managed integration paths rather than self-service runtime transports. Production readiness: the final step covers plan, payment, Production connection, validation and activation; billing begins when the payment provider confirms the first invoice is paid, payment does not activate Production, and activation remains server-derived and fail-closed. Production API access still requires a scoped client, a Program grant, a scoped credential and a separately configured webhook. Status and documentation: the public status page now measures event delivery, order and result processing, and laboratory connectivity from real platform-wide signals, and this changelog begins.
- Release: 2026.10.03-platform-readiness
- Affected surfaces: Control Plane, Laboratory Integration, Partner API, Security, Documentation
- Breaking changes: None
- Action required: No action is required for existing Partner API integrations. Laboratories entering Production must complete the current Production readiness and validation requirements.
Future entries
Future entries will include:
- Release date.
- Affected surfaces.
- Additions.
- Breaking changes.
- Migration or action required.
- Related documentation.