Centralized Bed Registry Platform

The vendor is required to provide centralized bed registry platform to enhance the efficiency and effectiveness of behavioral health services for department service recipients by implementing an innovative and reliable system.
- No computer hardware or other equipment, and no network or computer installation services (such as cabling or physical installation of equipment) will be purchased under any contract resulting.
- The city will purchase such equipment and services separately, through its normal procurement process.
- The priority levels of care to include in the systems are:
•    programs assist participants whose needs are less intense but still require clinical or recovery house assistance.
•    Programs assist participants who may need a 24- hour clinically managed supportive treatment environment to initiate or continue a recovery process that has failed to progress
•    Programs are appropriate for participants who require medically managed high intensity inpatient treatment, but who do not need the full resources of an acute care general hospital or daily physician interaction.
•    Programs are for participants experiencing severe signs and symptoms of intoxication—or signs and symptoms that are unexplained given known substance use—and requires 24-hour integrated medical services and support that are only available in an acute care setting. 
•    People in this level of care may need daily physician interaction or 24-hour oversight.
- Centralized bed registry functions, the platform must include the following functionality specific to crisis response centers (CRCs):
•    A crisis response center diverts management system allowing CRCs to submit divert status updates without requiring a phone call to a centralized authority
•    The platform must allow CRCs to manually request divert through a secure login or automatically trigger divert recommendations based on live data feed thresholds.
•    The system must allow both manual entry and application programming interface -based updates of key operational metrics:
•    The divert request interface must allow CRC staff to select a divert status level, aligned.
- Technical specifications
•    Browser compatibility: the platform must work seamlessly on major web browsers such as chrome, Firefox, safari, and edge.
•    Web-based needs: include semantic hypertext markup language (html) mark-up to ensure accessibility for screen-reader users and images with descriptive alt tags. 
•    It requires responsive styling for seamless access across devices, from desktops to mobile and tablets.
•    Scalability: the system must support dozens of users initially and scale with growing demands without performance degradation. 
•    The initial anticipated number of users will be up to 150, scaling to 200+ over within 3-5 years.
•    User authentication: should support single sign-on (SSO) with active directory (A.D.) or industry standard identity and access management (IDAM) platforms and must support multi-factor authentication (MFA) and role-based access control (RBAC) to ensure secure access.
•    Data import and export: The platform must support the import and export of data in common formats such as comma-separated values (csv), JavaScript object notation (json), and extensible markup language (xml).
•    Interoperability – ability to integrate with other platforms.
•    The system will need to capture individual level data and be able to integrate electronic health records (EHR’S).  
•    Security standards data encryption: all data, both in transit and at rest, must be encrypted TLS 1.2 or higher. 
•    Demonstrated experience integrating the platform into existing systems (e.g., electronic health records [her]).  
•    If bed-based providers already have a system, the ability to integrate that system into the centralized bed registry to prevent duplication in reporting.
•    Customization: provide customization options for different user roles and preferences. 
•    Possible customization for fields related to specific provider data such as bed types (following scales or scoring systems specified above), capabilities, etc. and the ability to sort and filter said data. 
•    Possible customization of referral management which may give the ability to send more than one referral at a time.
•    Data storage and backup storage: ensure adequate data storage capabilities to handle current and future data needs.

- Contract Period/Term: 1 year
- Optional/Mandatory Pre-Proposal Meeting Date: September 5, 2025
- Questions/Inquires Deadline: August 27, 2025