Public documentation (Tier 1)Approved
Integrations and interoperability status
An honest status list for every OCRS interoperability capability: what is available in production today, what is configured, and what is only planned.
- Document version
- 1.0
- Last updated
- 2026-09-08
- Document owner
- OWNER INPUT REQUIRED — DOCUMENT GOVERNANCE
- Applies to
- OCRS 2.4.0 (multi-tenant hosted edition)
- Status
- Approved
- Audience
- Technical evaluators, Health systems, State agencies, Procurement teams
- Evidence source
- src/lib/reporting/deliver.server.ts · src/lib/obcc/state-csv.ts · src/lib/facility-import.ts
Status definitions
- Production available — implemented, in use and supported today.
- Supported / configured — implemented, enabled per deployment as part of configuration.
- Pilot / beta — implemented but not yet generally available.
- Planned — not implemented. A planned capability is never described as operational.
Capability status
| Capability | Status | Notes |
|---|---|---|
| Fixed-schema CSV reporting extract | Production available | Versioned schema 2.0.0, one row per physical bed, generated for the receiving jurisdiction. |
| Spreadsheet and PDF report artifacts | Production available | Human-review outputs generated from the same accepted records. |
| Scheduled report generation and delivery to configured recipients | Production available | Recurring runs on the jurisdiction's configured schedule and time zone, with per-attempt delivery logging and idempotent cycles. |
| Recipient configuration per jurisdiction | Supported / configured | Recipient lists are resolved from configuration at send time; a removed recipient stops receiving reports immediately. |
| Bulk facility import | Supported / configured | Used during implementation to load an organization's facility and bed configuration. |
| Public read API for capacity data | Planned | Not implemented. No public API endpoint is available to customers today. |
| HL7 v2 interfaces | Planned | Not implemented. No HL7 interface exists in the product. |
| FHIR resources / FHIR API | Planned | Not implemented. No FHIR endpoint or resource mapping exists in the product. |
| Single sign-on federation (SAML / OIDC to a customer directory) | Planned | Not implemented for customer directories today. |
| Statewide system-to-system interface beyond the reporting extract | Planned | Not implemented. Statewide reporting is delivered through the extract and report path above. |
Note: Nothing in the Planned rows is offered, priced or scheduled by this document. A capability moves out of Planned only after it is implemented, verified and approved — and then it is recorded in the release notes.
Version history
This document covers a change-managed subject, so every substantive change is versioned with its effective date and the audience it affects.
| Version | Effective date | What changed | Affected audience |
|---|---|---|---|
| 1.0 | 2026-09-08 | First published integration status list. | Technical evaluators, procurement |