State & jurisdiction programs
A validated capacity record from every participating facility
Also a deployment level rather than an industry. A jurisdiction defines the reporting specification in OCRS; facilities cannot submit until their data satisfies it. Organization views aggregate for oversight and never create a second competing submission.
Best suited for: State / jurisdiction programs • County / regional authorities
Who this is for
- State agency program and data staff receiving occupancy information
- Jurisdiction administrators defining required reporting fields
- Technical and procurement evaluators assessing the reporting architecture
This use case replaces the previously published label: State Health Agencies.
Operational challenge
The operational problem
- Every facility reports differently
- Without an enforced specification, fields are missing, formats vary and the dataset needs manual repair.
- Late and missing submissions are discovered late
- Completeness is reconstructed after the fact instead of being visible during the period.
- Aggregates cannot be traced to a source
- A statewide figure is only as defensible as the submission history behind it.
- Competing submissions
- When an organization can report on behalf of a facility, two versions of the same census exist.
How OCRS fits the workflow
- 1.Jurisdiction configures the reporting specification
- 2.Facility submits; OCRS blocks the submission until the specification is satisfied
- 3.Organization views aggregate for oversight only
- 4.Jurisdiction receives validated records with full history and audit evidence
Capabilities that apply here
- Jurisdiction reporting specification
- Required fields and identifiers are configured per jurisdiction and enforced.
- Pre-submission validation
- Each violation names the field, the rule, the reason and where to correct it.
- Statewide roll-up
- Occupancy and capacity aggregated from validated facility submissions.
- Reporting history & audit evidence
- Append-only submission and audit records behind every figure.
- Exports
- Structured extract matching the published reporting data dictionary.
- Role-based access
- Facility, organization and jurisdiction scopes are separated.
OCRS carries occupancy and capacity information only — no client-level clinical record. Statewide licensing is quoted separately from per-facility plans.
Example workflow
Illustrative OCRS workflow
- 1A facility submits a census missing a required identifier
- 2OCRS blocks the submission and names the field and the correction location
- 3The corrected submission is validated and recorded
- 4The jurisdiction roll-up updates, with the submission retained in history
Illustrative only. Not based on a named customer, and no adoption figures, outcomes or endorsements are implied.
Operational need and regulatory position
Operational need
A jurisdiction needs comparable, complete and traceable capacity information rather than a repaired spreadsheet.
Regulatory / reporting requirement
OCRS enforces the specification a jurisdiction configures in the platform. It does not assert, interpret or create a statutory reporting mandate, and no jurisdiction relationship or endorsement is implied.
What implementation requires
- Reporting specification: required fields, identifiers and cadence
- Participating facility and organization structure
- Facility identifiers registered with the jurisdiction
- Recipient configuration and delivery expectations
- Jurisdiction user accounts and roles
- Testing before production activation
Customer and OCRS responsibilities, and the full prerequisite list, are documented in Implementation & onboarding.
Documentation for this use case
- Reporting architecture & data flow
- Reporting & validation rules
- Reporting data dictionary
- Security & privacy overview
What to do next
The demo is an on-demand recording you can watch immediately — no account and no meeting required.