Reporting architecture and data flow
The authoritative Facility → OCRS → State/Jurisdiction reporting model, the role of organization aggregation, and a procurement-level data-flow diagram.
- 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, State agencies, Counties, Procurement teams
- Evidence source
- src/lib/reporting/* (submission, validation, extract, delivery) · src/lib/obcc/state-csv.ts
The authoritative model
OCRS operates one reporting path: Facility → OCRS → State/Jurisdiction. Facility-level information is the authoritative source of facility census reporting. Everything an organization or a jurisdiction sees is an aggregation of those facility records, computed for management and oversight — never a second, competing submission.
- Facility — authoritative source of its own licensed beds and census submissions.
- Organization / provider — aggregates its own facilities for management and oversight; cannot submit a census on a facility's behalf as a separate report.
- Jurisdiction / state recipient — aggregates authorized reporting information across participating facilities for oversight.
Note: Because aggregation is a read of facility records rather than a submission, an organization rollup and a state rollup can never disagree with the facility record they are computed from.
Public data-flow diagram
1 · Facility
Licensed bed configuration and the census for a reporting date, entered by an assigned facility user.
2 · OCRS validation & processing
Required identifiers, bed states, capacity constraints and dates are checked against the receiving jurisdiction's specification before anything is accepted.
3 · Reporting record
An accepted submission becomes an append-only reporting record; the extract for a reporting period is generated from those records and locked.
4 · Authorized jurisdiction recipient
The extract and report are delivered to the recipients configured for that jurisdiction; every delivery attempt and outcome is logged.
Alongside this path: organization oversight reads the same facility records; reporting history retains every submission; audit records retain who did what and when. This diagram describes information movement and system boundaries only — infrastructure topology, hostnames, keys and authorization policy implementation are deliberately not published here.
Tenant boundary
Every record belongs to exactly one organization, and every read and write is constrained to the signed-in user's organization and facility assignments in the database layer rather than in the interface. The detailed authorization policy implementation is a controlled document (see Technical & procurement resources) because publishing it would add nothing an evaluator needs and would enlarge the attack surface.