Skip to main content

Capability status

Applies to: this documentation snapshot, updated 23 October 2026. UI reference: frontend feat/849-light-rebrand at 3a99cf9. Backend evidence was last reviewed on 21 October 2026; this is not a new backend acceptance test or a release certification.

Use this page as the shared source for availability statements. GA, Beta and Roadmap combine the Connect capability matrix (last verified 3 May 2026), owner statements recorded on 21 October 2026, and the standards availability updates in PR #7, merged into this documentation branch at 820eb59. Those upstream updates supersede the older matrix labels for HL7 message types, X12 transactions, DICOM DIMSE, FHIR structural validation and IHE profiles. Owner-confirmed records the product owner's later availability statement; it does not imply a new end-to-end test. A draft design header alone does not establish whether a deployed feature is supported.

CapabilityStatus used in these docsBasis and boundary
Connect standaloneGACapability matrix
Connect hub modeGA, owner-confirmedOwner statement recorded 21 October supersedes the older matrix's Beta label for hub mode
Connect spoke modeBeta in the retained matrix; current release availability unverifiedThe recorded owner statement addresses hub mode only. Confirm spoke-mode availability for your deployment before relying on it
Multi-site joins, exactly-once delivery and federated learningAvailable, owner-confirmedOwner statement recorded in the Mesh evidence; older repository design/hardening records have not been reconciled. Confirm the supported deployment and operating conditions with your administrator before use
Cross-spoke failover, local spoke queue, hub/spoke mTLSRoadmap in the retained matrixNot covered by the later owner statement

See Connect for processor limitations and Run on Mesh for configuration and operational controls. Availability of a mode does not establish availability of every optional feature.

Connect and interoperability availability​

StatusCapabilities
GAHL7 v2 parsing, ADT A01/A03/A08, ORU^R01, ORA^R41; TCP/MLLP listener and client; C-CDA parsing; X12 837; DICOM file parsing, DICOMweb and DICOM C-STORE, C-FIND, C-MOVE and C-ECHO (DIMSE); other HL7 message types (ORM, SIU, VXU, BAR, pharmacy); X12 835, 270/271, 276/277, 278, 834 and 820; FHIR transform with JavaScript; FHIR structural validation and R4 Touchstone certification; IHE XDS.b and MHD; IHE PIXm, PDQm, ATNA and PCD; standalone and hub modes; per-organization read and write enforcement
BetaSpoke mode (retained matrix; current release availability unverified); FHIR Bundle ingestion (pass-through, no validation); per-key message ordering (off by default); MQTT; network topology view
RoadmapMutual TLS between hub and spoke; 4-role RBAC; per-organization encryption at rest; cross-spoke failover; visual drag-and-drop channel builder; Hydra Stream (not deployable)

For the complete protocol breakdown, see Other standards around FHIR. X12 GA refers to parsing and workflow nodes; transport still uses an agreed file or API route, not a dedicated X12 Connect connector.

Workflow nodes (node maturity field)​

The catalog has 198 nodes in 18 categories. Of these, 7 declare production (for example empi, soap-generate, clinical-timeline), 26 declare beta (for example anonymize, voice-call, sql-connector, the rlm-* nodes) and 2 declare simulated: drug-check and terminology-mapper return demo data and are never for clinical use. The other 163 declare no maturity.

Implementation records and design status​

AreaStatus in its source
Run on Mesh across sitesSee the owner-confirmed capabilities and verification boundary above; do not infer pilot status from the older design header alone
Federated executionRetained design is Draft v3 (mesh-federated-execution-and-learning.md); the owner statement covers the specific Mesh capabilities above, not a blanket release status for this design
Federated learningOwner-confirmed available; the retained Draft v3 design is an older engineering record
Environments and promotionDesign header says DRAFT v2, with an implementation record in its section 9. In the Builder, the Deploy menu only sets a status and exports JSON or YAML; the application also has an Environments page under Tiet · Hub → Platform with tabs Environments, Routes, Agents & workflows, Trusted sources, Approvals and Retention. See Environments and promotion
Agent access governance (credential placeholders and permission-change proposals)Draft v1, "nothing here is implemented"
Harness resilience for agent graphsDraft v1 header
Tiet · ConsultRelease availability is unverified; no owner statement is recorded. The retained design is Draft for design review, which establishes neither a Pilot nor a GA release. See Tiet · Consult

Something unclear? Send documentation feedback by email.