260011-Attachment E-Functional and Technical Requirements.xlsx
XLSX spreadsheet 14 KB Posted
- Attached to
- Inmate Medical Wristbands
- Solicitation number
- 260011-RFP
- Issued by
- Arizona
About this file
This document is a Functional and Technical Requirements attachment for an Inmate Medical Wristbands solicitation issued by the Maricopa County Sheriff's Office (MCSO) in partnership with Correctional Health Services (CHS) in Arizona. The procurement seeks a qualified vendor to provide, implement, and support a secure electronic medical wristband monitoring system designed to track and monitor inmates on specific medical protocols such as CIWA (Clinical Institute Withdrawal Assessment) and COWS (Clinical Opiate Withdrawal Scale). The system must have capabilities including precise location tracking within 10-foot radius, unique device identification, multi-station alert monitoring, configurable medical alert thresholds, and the ability to capture and retain monitoring data.
The technical requirements specify a cloud-hosted solution that is not subscription-based, supports end-to-end device encryption, provides API integration, and can integrate with OKTA for single sign-on. The system must support reporting through SSRS or Power BI without additional licensing, include implementation support and training, and provide ongoing maintenance and system upgrades. Vendor bids must be submitted through BidNet Direct, with Maricopa County reserving the right to award the contract in full or in part to a single or multiple vendors. The medical wristbands must meet specific correctional environment standards, including being tamper-proof, not easily swallowed, safe, and having a minimum 24-hour battery life with low battery alerts.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| ATT C - REFERENCES.pdf | ||
| 260011-Exhibit 4-Draft Contract.docx | DOCX document | |
| BOS-ATT B Agreement Page.pdf | ||
| 260011-Solicitation.docx | DOCX document | |
| ATTACHMENT A - VENDOR INFORMATION.docx | DOCX document | |
| BidNet Direct Electronic Submission Instructions.pdf | ||
| 260011-Attachment D-Pricing Sheet.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment E
| Attachment E - Functional and Technical Requirements | ||||
| 260011-RFP Inmate Medical Wristbands | ||||
| Submitting Respondent: _________________________________________ | ||||
| Ref # | Agency | Requirement | Yes or No? (Y or N) | Respondent Notes |
| 1.00 | Functional Requirements | |||
| 1.01 | MCSO | The medical wristband system shall have the capability to define coverage areas within each facility that MCSO determines will be included for monitoring medical wristband alerts. | ||
| 1.02 | MCSO | Wristbands shall have the capability to monitor vitals while in a vehicle as well as identify which vehicle the inmate is in. | ||
| 1.03 | MCSO | The medical wristband system shall have the capability of knowing where an activated wristband is located within all the defined coverage areas within each facility to within a 10-foot radius, or vehicle. | ||
| 1.04 | ALL | All medical wristbands shall have a unique device identification number that will not be duplicated. | ||
| 1.05 | MCSO | The application or system used to monitor and track triggered alerts for the wristbands shall have the capability to be viewed at multiple stations by multiple MCSO users, and each station shall have the capability to select and assign the coverage areas (one or more as needed) they are responsible for monitoring. | ||
| 1.06 | CHS | The application or system used to monitor and track triggered alerts for the wristbands shall have the capability to view all alerts and acknowledgements as a read only for CHS users, and each station shall have the capability to select and assign the coverage areas (one or more as needed) they are responsible for monitoring. | ||
| 1.07 | CHS | Medical wristbands that are placed on inmates in CIWA or COWS shall have the capability to be configured based on a general standard, by gender and age, to define the minimum and maximum values for the variables that will trigger a “Medical Emergency” alert if exceeded. The variables required for monitoring are listed below. | ||
| 1.08 | CHS | The general standard variables shall be configurable so that the minimum and maximum values that trigger an alert can be specific to the inmate wearing the wristband. | ||
| 1.09 | MCSO | Medical wristbands that are placed on inmates shall have the capability to have the booking number (if capable) added and be included on any alerts or data captured and retained related to the specific wristband once it is assigned and attached to an inmate. | ||
| 1.10 | MCSO | Medical wristbands shall have the capability to send different types of alerts with a level of urgency associated with each type to assist with prioritization when triggered in any coverage area. | ||
| 1.11 | MCSO | Medical wristband alerts that are triggered shall be sent to an active alert message queue along with an audio prompt immediately, within 10 seconds of being triggered, to the application or system monitoring station assigned for the coverage area the wristband is located within. | ||
| 1.12 | MCSO | All defined alerts that are triggered and sent shall be displayed in an active alert message queue for the assigned monitoring station until it is acknowledged by a user with monitoring access, and once it is acknowledged the alert shall be moved out of the active queue and to an acknowledge alert message queue. | ||
| 1.13 | MCSO | The monitoring application or system shall allow users to acknowledge all alerts that have been created. Once an alert has been acknowledged, it will then move to a separate queue. | ||
| 1.14 | MCSO | The monitoring application or system shall allow monitoring users to select and acknowledge multiple “Network Down” messages to simplify acknowledgement of multiple messages in the event of a large network outage. | ||
| 1.15 | ALL | All alerts that are triggered shall capture and retain the date, time, and variables (one or more) that caused the trigger along with the minimum and maximum settings configured on the specific wristband. Additionally, it shall capture the unique wristband identification number and Booking # assigned. | ||
| 1.16 | MCSO | All alert acknowledgements that are made shall capture and retain the alert message it was related to, and the date, time, device identification number, and the username that acknowledged it. | ||
| 1.17 | MCSO | All defined alerts that are triggered and sent shall be retained in the medical wristband system until purged by the system administrator. | ||
| 1.18 | ALL | The medical wristband and system shall be able to capture and retain all variables being monitored at a minimum of every 60 seconds. Additionally, all variables captured shall include the variable being monitored, the variable value at the time it was taken, the date and time taken, the variable minimum and maximum in effect, the wristband device number, and the Booking # assigned to the device. All information must be retained until purged by the System Administrator. | ||
| 1.19 | ALL | The medical wristband shall be able to retain and report all captured variables being monitored if the network connection is lost and update the system once the network connection is reestablished. | ||
| 1.20 | ALL | The application or system shall provide the capability for defined users to query and generate reports for all data that is captured and retained and allow filtering of data based on the any of the data retained. | ||
| 1.21 | ALL | The application or system shall allow for the configuration of multiple user group access where each defined group would have the ability to view or update the data defined for the group. | ||
| 1.22 | MCSO | The medical wristband should be considered tamper proof, not easily swallowed, safe (not easily turned into a weapon), and approved for use in a correctional setting. | ||
| 1.23 | MCSO | The medical wristband shall have a minimum battery life of 24 hours with low battery alerts. Respondent to indicate the battery life of the medical wristband if it is longer than 24 hours. | ||
| 1.24 | MCSO | The medical wristband shall be able to detect and send an alert relating to an abnormal movement, such as an inmate being in a fight or having a sudden fall. The alert message that should be received shall be “Abnormal Movement”. | ||
| 2.00 | Technical Requirements | |||
| 2.01 | MCSO | The system shall provide the capability to manage user access and capability based on defined user roles where an individual may be assigned to one, or multiple roles. | ||
| 2.02 | MCSO | The system shall provide the capability to develop and manage reports based on defined user roles where an individual may be assigned to one, or multiple roles. | ||
| 2.03 | MCSO | The system shall not allow unlimited users simultaneous logins. | ||
| 2.04 | MCSO | The system shall not be based on a per user subscription. | ||
| 2.05 | MCSO | The system shall support the use of either SSRS or Power BI for reporting and be accessible to users without the need for additional licensing. | ||
| 2.06 | MCSO | The system shall provide an API with industry-standard, best practice security and architecture allowing for data to be consumed programmatically for business intelligence and/or future integration with other MCSO or CHS applications. | ||
| 2.07 | MCSO | The system shall provide application maintenance and support for resolving vulnerabilities and security risks as they are found and addressed and are to include documented release notes. | ||
| 2.08 | MCSO | The system shall provide the capability to schedule and perform backups of application and transaction related data and support the restoration of the information as needed. | ||
| 2.09 | MCSO | The system shall allow for data encryption capabilities for data that is at rest or in transit. | ||
| 2.10 | MCSO | The system shall support end to end device encryption. | ||
| 2.11 | MCSO | The system shall have a web application firewall to prevent automated creation of reports (BOTS) | ||
| 2.12 | MCSO | The system shall have the ability to define data for purging and support the scheduling of the purges to be performed. | ||
| 2.13 | MCSO | The contractor shall include implementation support and training | ||
| 2.14 | MCSO | The contractor shall provide maintenance including all updates and system upgrades | ||
| 2.15 | MCSO | The system shall have the ability to be integrated with OKTA for single user sign in. | ||
| 2.16 | MCSO | The system shall be a cloud hosted solution that is not subscription based. |
File details come from the government source that posted it. Updated .