Public documentation (Tier 1)Approved

Implementation and onboarding prerequisites

What a prospective customer must decide or provide before an OCRS deployment can go live, and which responsibilities sit with the customer versus OCRS.

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: Procurement teams, Provider organizations, State agencies, Counties
Evidence source: Implemented onboarding surfaces (organization/facility directory, bed configuration, user assignment, jurisdiction configuration, reporting schedule, reporting test centre)

Prerequisites

Prerequisites and where responsibility sits
Prerequisite	What is needed	Customer	OCRS
Organization and facility structure	The organizations to be created and the facilities each one owns.	Decides and supplies	Configures the directory
Facility identifiers	The OCRS Facility ID registered with the receiving jurisdiction, plus licence numbers where the jurisdiction requires them.	Supplies	Records and validates presence
Licensed capacity	Licensed bed count per facility.	Supplies	Records; validates submissions against it
Bed and room configuration	Rooms and bed labels for every physical bed.	Supplies	Loads, including by bulk import
Levels of care	Licensed reporting level of care per facility.	Supplies	Records; required on every extract row
User and role assignments	Which people hold which role, at which organization or facility.	Decides and supplies	Provisions and enforces
Reporting recipients	Who at the jurisdiction receives reports.	Decides and supplies	Configures per jurisdiction
Reporting schedule	Reporting frequency and the time zone it runs in.	Decides	Configures and operates the schedule
Jurisdiction configuration	The receiving jurisdiction and its required reporting fields.	Confirms	Configures; surfaces an unconfigured list as a defect
Data migration	Any historical census or facility data to be loaded, and in what format.	Supplies and validates accuracy	Loads facility and bed configuration
Training	Which staff need which role-based material.	Identifies staff	Provides published guides, documentation and courses
Testing / UAT	Confirming submissions validate and reports reach the intended recipients before go-live.	Performs and accepts	Provides the reporting test facility and verification output
Production activation	The point at which reporting to the jurisdiction becomes live.	Authorizes	Activates and records the activation

Prerequisites and where responsibility sits

Note: Licensed bed counts and bed configuration come first: census submissions are validated against them, so a facility cannot report correctly until they are right.

Commercial and contractual terms

OWNER INPUT REQUIRED — IMPLEMENTATION TIMELINE AND SERVICE COMMITMENTS

No implementation duration, staffing commitment, migration service level or acceptance window has been approved for publication. Those terms belong to the applicable customer agreement and are not asserted here.

All documentation Ask a technical or procurement question