SD24-00022_Exhibit_A-3_System_Requirements.Final.xlsx
XLSX spreadsheet 138 KB Posted
- Attached to
- SD24-00022 Nurse Call Light System Replacement
- Solicitation number
- 0000034219
- Issued by
- Los Angeles County, California
About this file
This is a System Requirements workbook for RFQ SD24-00022 from the California Correctional Health Care Services (CCHCS) detailing technical specifications for a Nurse Call System (NCS). The requirements document outlines comprehensive specifications across multiple categories including General System Requirements, Hardware, Software, Data Networking, and Training requirements for implementing and maintaining a UL 1069-compliant nurse call system throughout CCHCS facilities. The system must support nurse-patient communications, emergency notifications, dome lights, integration with electronic health records, and extensive reporting capabilities.
The technical requirements emphasize the need for integration with CCHCS' Active Directory, HL7 compatibility with the Electronic Health Records System, support for at least 18 concurrent patient calls, and ability to interface with multiple wireless communication systems. The vendor must provide 24/7 technical support, regular firmware/software updates, and training for various user groups. The implementation team must include certified technicians with confined space training, an engagement manager with 5+ years of project management experience, and nursing program subject matter experts. While pricing details are not included in this requirements document, vendors must possess either a California C-7/C-10 Electrical Contractor License or B-General Building Contractor License with qualified subcontractors.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFQ_SD24-00022_Nurse_Call_Light_System.Final.docx | DOCX document |
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
Instructions
RFQ SD24-00022
EXHIBIT A-3 - Nurse Call System Requirements Workbook Instructions This Excel Workbook consists of 4 spreadsheets including: Instructions, spreadsheets each containing a group of requirements associated to a specific Category (Technical/System, Training and Experience Requirements), and Requirements Glossary.
DO NOT change any of the data or the formatting on the spreadsheets.
In order for an Offer to be considered and accepted:
• Contractor must complete the requirement responses on each of the # separate requirement spreadsheets.
• Contractor must certify that their Offer “Can Meet” each Mandatory requirement; otherwise the Offer may be deemed non-responsive.
• Contractor must certify that their Offer “Can Meet” or “Cannot Meet” or specify response where specified for all Desirable requirements.
| Spreadsheet Legend | ||
| Column | Title | Column Description |
| A | Unique ID | A unique alpha-numeric identifier that references each individual requirement by the section. |
| B | Requirement Type | General System Requirements, Hardware, Software, Data Networking, Training. |
| C | Category | Identifies a component of the Requirement Type. |
| D | Mandatory/Desirable | CCHCS defined priorities as Mandatory (Must Have) or Highly Desirable (Should Have) |
| E | Requirement Description | Complete description of the requirement with detail sufficient to enable an Contractor to respond. |
| F | Contractor Certification | Contractor is required to certify if their Offer “Can Meet” or “Cannot Meet”, or select option where specified, for each requirement. |
G Experience Summary/ Resume Reference This column is only on the NCS Experience Requirements tab.
For the Company requirements, if the response is other than "Cannot Meet", reference the Experience Summary Number where the requirement is satisfied.
For Implementation Team Personnel, please specify the Name of the Candidate and reference the page/location on the resume where the requirement is satisfied.
&"-,Bold"&14CCHCS RFO EXHIBIT A-1 HRA Detailed Requirements Workbook
System Requirements
| Unique ID | Requirement Type | Category | Mandatory/ Desirable | Requirement Description |
| Contractor Certification |
("Can Meet" or "Cannot Meet" the Requirement or select an option where specified)
| 1.00 | GENERAL SYSTEM REQUIREMENTS | |||
| 1.01 | General System Requirements | Communication | Mandatory | Provide for nurse and patient communications from patient rooms, tub, showers as per as-built plans. |
| 1.03 | General System Requirements | Communication | Mandatory | Provide a two-way audio path from the bed station to the nurse station or wireless device, in response to a call or initiating a call. |
| 1.04 | General System Requirements | Communication | Mandatory | Provide an external indicator light over each patient room entrance, which can indicate: |
-a nurse or staff member is inside that room -a patient button has been pressed -a staff emergency button has been pressed
| 1.06 | General System Requirements | Communication | Mandatory | Provide uninterrupted high quality, full duplex audio communication between patient/staff stations and nurse station console handset. | |
| 1.07 | General System Requirements | Communication | Mandatory | Support a mimimum of 18 concurrent patient calls to facilitate workflows and call escalations to various nursing staff and/or groups. | |
| 1.12 | General System Requirements | General | Desirable | Maintenance contracts must be available from a factory-authorized distributor for a minimum of 5 years, after the warranty has expired. | |
| 1.13 | General System Requirements | Vendor Support | Mandatory | Provide a toll free technical support number that is available 24 hours per day, 7 days per week. | |
| 1.14 | General System Requirements | Vendor Support | Desirable | Proactively provide NCS firmware/software/security updates for the life of the system. | a) Cannot provide these updates |
b) Can provide at additional cost
c) Can provide at no cost
| 1.15 | General System Requirements | Vendor Support | Desirable | Proactively monitor, detect and resolve system issues remotely. |
| 2.00 | HARDWARE | |||
| 2.01 | Hardware | Dome lights | Mandatory | Provide long-life (approximately 50,000 hours) RGB LED lamps |
| 2.02 | Hardware | Dome lights | Mandatory | Provide a minimum of 18 dome color options with configurable flash rates, customizable by call type. |
| 2.04 | Hardware | Dome lights | Mandatory | Normal and emergency calls distinguished by different visual signals. |
| 2.06 | Hardware | Dome lights | Mandatory | Wall or ceiling mountable. |
| 2.07 | Hardware | Dome lights | Mandatory | Translucent lens sections provide maximum visibility under high ambient lighting conditions. |
| 2.09 | Hardware | Dome lights | Mandatory | Power-up test sequence to verify proper LED illumination. |
| 2.10 | Hardware | Faceplates - New Construction | Mandatory | Faceplates must be a single gang 12 gauge stainless steel face plate. Engrave nomenclature per the drawings, backfill with black paint |
| 2.11 | Hardware | Faceplates - New Construction | Mandatory | Ability to adapt to 1, 2, or 3-gang back-box using adapter ring. |
| 2.12 | Hardware | Faceplates - New Construction | Mandatory | Ability to be flush mounted directly to the back-box. |
| 2.13 | Hardware | Faceplates - As Built | Mandatory | Faceplates must be customized to fit existing NEMA outlet boxes with flush mount ligature proof covers and engraved nomenclature per the as-built plans, backfilled with black paint. |
| 2.14 | Hardware | General | Mandatory | Continuous error/failure detection of attached end-point devices, and reporting of device location. |
| 2.15 | Hardware | General | Mandatory | Report multiple connected devices and physical locations. |
| 2.16 | Hardware | General | Mandatory | NCS hardware shall consist of, at a minimum: |
a- nurse station consoles b- nurse duty stations c- nurse staff stations d- audible/visual annunciators e- nurse call network controllers f- network switches, power supplies g- Uninterruptable Power Supplies (UPS) for battery backup h- patient bed stations i- workflow devices j- patient room entry stations k- duty stations, corridor dome lights l- call cords, push buttons m- emergency push button stations n- emergency call stations o- emergency call reset key switches p- care boards q- equipment interface stations
| 2.17 | Hardware | General | Mandatory | Hot-swappable end-point nursing unit components that can be replaced without a complete controller reboot. | |
| 2.18 | Hardware | General | Desirable | Nurse Call System manufactured in the USA. | Select one or more of the following that apply: |
a) All NCS hardware is manufactured in the USA
b) All NCS software and firmware is manufactured in the USA
c) All hardware, software and firmware come from one manufacturer
| 2.21 | Hardware | Nurse Station Console | Mandatory | Ability to establish a two-way audio path between the patient room station and the Nurse Call Station. |
| 2.23 | Hardware | Nurse Station Console | Mandatory | Touchscreen with integrated handset with GUI controls. |
| 2.25 | Hardware | Nurse Station Console | Mandatory | Configurable control panel with permanently designated task buttons for frequently performed duties. |
| 2.26 | Hardware | Nurse Station Console | Mandatory | Ability to adjust time settings and volume levels for automatic Quiet Mode. |
| 2.27 | Hardware | Nurse Station Console | Mandatory | Full duplex, high quality, two-way voice communication with adjustable volume. |
| 2.28 | Hardware | Nurse Station Console | Mandatory | Enable password protection for authorized access. |
| 2.29 | Hardware | Nurse Station Console | Mandatory | Cancellation of Emergency and Code calls only at the originating device. |
| 2.30 | Hardware | Nurse Station Console | Mandatory | Ability to cancel Routine calls: |
a- from the device where the call originated b- from any nurse console system assigned to receive the call and c- at a designated remote locator station.
| 2.34 | Hardware | Nurse Station Console | Mandatory | Two way HL7 communication between CCHCS’ Electronic Health Records System. |
| 2.35 | Hardware | Nurse Station Console | Mandatory | Annunciation of Routine, Priority, and Emergency calls throughout the Nurse Call System. |
| 2.37 | Hardware | Nurse Station Console | Mandatory | Supports external additional display. |
| 2.41 | Hardware | Patient Room Devices - General | Mandatory | All wall mount stations inside patient areas shall be flush mounted using anti-ligature, tamper-resistant cover plates that can only be removed with a CDCR approved specialty tool. |
| 2.42 | Hardware | Patient Room Devices - General | Mandatory | All flush mount station buttons shall use a sealed keypad to facilitate the use of disinfectant cleaners. |
| 2.43 | Hardware | Patient Room Devices - General | Mandatory | All calls must be cancellable at the initiating device. |
| 2.44 | Hardware | Patient Room Devices - General | Mandatory | Touchscreen with integrated handset and full, duplex communication. |
For example, cannot include:
- VOX (Voice Operated Switching) circuitry or push-to-talk audio.
- VOX systems that incorporate microphones in pillow speakers to simulate true duplex audio.
| 2.45 | Hardware | Patient Room Devices - General | Mandatory | Touchscreen control for direct room and bed selection without requiring numeric entry. |
| 2.46 | Hardware | Patient Room Devices - General | Mandatory | Configurable control panel with permanently designated task buttons shall be provided for frequently performed duties. |
| 2.47 | Hardware | Patient Room Devices - General | Mandatory | Full duplex, high quality, two-way voice communication with adjustable volume. |
| 2.48 | Hardware | Patient Room Devices - General | Mandatory | Enable password protection for authorized access. |
| 2.49 | Hardware | Patient Room Devices - General | Mandatory | Cancellation of Emergency and Code calls only at the originating device. |
| 2.50 | Hardware | Patient Room Devices - General | Mandatory | Cancellation of Routine calls from the device where the call originated, from any nurse console system assigned to receive the call, or at a designated remote locator station. |
| 2.55 | Hardware | Patient Room Devices - Patient Station | Mandatory | Standard configuration of Routine, Cancel, and Staff Emergency buttons. |
| 2.56 | Hardware | Patient Room Devices - Patient Station | Mandatory | Backlit keypad. |
| 2.57 | Hardware | Patient Room Devices - Patient Station | Mandatory | Internal Mylar cone speaker or equivalent. |
| 2.60 | Hardware | Patient Room Devices - Patient Station | Mandatory | Compatibility with both VoIP and analog systems. |
| 2.63 | Hardware | Patient Room Devices - Patient Station | Mandatory | Configurable alert types. |
| 2.68 | Hardware | Patient Room Devices - Patient Station | Mandatory | Ability to accept requests from nurse station console. |
| 2.69 | Hardware | Patient Room Devices - Patient Station | Mandatory | Continuous (24/7) network supervision. |
| 2.70 | Hardware | Patient Room Devices - Patient Station | Mandatory | Keypad allows use of cleaning solutions. |
| 2.71 | Hardware | Patient Room Devices - Patient Station | Mandatory | Cancel button shall cancel any call on station. |
| 2.72 | Hardware | Patient Room Devices - Patient Station | Mandatory | Ability to service or replace station without removing system power or powering down the associated controller. |
| 2.79 | Hardware | Patient Room Devices - Patient Station | Desirable | Cleaning mode to prevent accidental call placement. |
| 2.81 | Hardware | Patient Room Devices - Shower and Tub Buttons | Mandatory | Large color-coded labels for placement of calls. |
| 2.82 | Hardware | Patient Room Devices - Shower and Tub Buttons | Mandatory | Ability to display a visible call assurance LED when call is placed. |
| 2.83 | Hardware | Patient Room Devices - Shower and Tub Buttons | Mandatory | Large color-coded CANCEL AT SHOWER label for cancellation of calls. |
| 2.84 | Hardware | Patient Room Devices - Shower and Tub Buttons | Mandatory | Water-resistance. |
| 3.00 | SOFTWARE | |||
| 3.01 | Software | Communication | Mandatory | The NCS and its components shall be capable of reporting device failure to any designated nurse station console, email, or wireless device. |
| 3.02 | Software | Communication | Mandatory | Ability to utilize remote diagnostics to locate the source of device failures. |
| 3.03 | Software | Communication | Mandatory | Support two-way signaling, audio communication, and text messaging between console systems and mobile devices. |
| 3.06 | Software | Configuration | Mandatory | CCHCS-configurable to meet the requirements of CCHCS’ care facility types (i.e. Correctional Treatment Center, Acute Psychiatric Program, and Intermediate Care Facility, etc.). |
| 3.07 | Software | Configuration | Mandatory | System diagnostics, configuration, and programming changes shall be capable of being executed remotely via a CDCR/CCHCS approved VPN connection. |
| 3.08 | Software | Configuration | Mandatory | Ability to configure all call types with assignable priorities, unique verbiage, unique audible tones, and colors at nurse station consoles, annunciators, and duty stations. |
| 3.09 | Software | Configuration | Mandatory | Include user-configurable software for nurse console system computers. |
| 3.11 | Software | Configuration | Mandatory | Include remotely programmable/configurable station functions that can be modified by factory-certified technicians to meet CDCR/CCHCS’ preferred functionality. |
| 3.12 | Software | Configuration | Mandatory | Program the system to remotely cancel calls, per CDCR/CCHCS Operating Procedure (OP). |
| 3.14 | Software | Configuration | Mandatory | On a per patient basis, program and configure, with assignable priorities/lights/flash rates, call types including: |
a - Routine b - Priority c- Staff Emergency d- Code Blue
3.15 Software Configuration Mandatory Ability to route/escalate specific call requests to appropriate level of staff from console system.
| 3.16 | Software | Configuration | Mandatory | Report patient calls to any nurse station console configured on the Nurse Call System. |
| 3.17 | Software | General | Mandatory | System must be kept within one version of latest stable production version. |
| 3.18 | Software | General | Desirable | Provide capability for backward compatibility to prior generations of manufacturer’s Nurse Call Systems without requiring network adaptors, interface modules, or translation equipment. |
| 3.19 | Software | General | Mandatory | Provide capability to support a GUI for each functional module of the software including, at a minimum: |
a- staff assignments bed assignments b- call/event handling c- request handling d- messaging e- equipment management f- historical event reporting.
| 3.20 | Software | General | Mandatory | Capability to manually admit, discharge, and/or transfer patients in the event the EHRS interface is not used, off-line, or is incorrect. Information manually entered at a touchscreen station will reside in the Nurse Call System and shall not be passed through the HL7 interface to the EHRS. |
| 3.21 | Software | General | Mandatory | Ability to make staff assignments and display patient information. |
| 3.22 | Software | General | Mandatory | Information can be exchanged between nurse call stations. |
| 3.23 | Software | Nurse Rounding | Desirable | Provide means for CCHCS Nursing staff to document, in real time, patient observation (e.g. patient sitting, sleeping, laughing, etc.), while outside the patient’s room. |
| 3.24 | Software | Nurse Rounding | Desirable | Ability to track and document when and who visits a patient’s room for observation. |
| 3.25 | Software | Nurse Rounding | Desirable | Ability to report on frequency of, and timing of, nursing staff visits to a patient’s room, within the last 24 hour period, or any period of selected timeframe. |
| 3.26 | Software | Nurse Rounding | Desirable | Ability to generate reports/metrics on patient observations. |
| 3.27 | Software | Nurse Station Console | Mandatory | Ability for user to swing (move) an individual room or any group of rooms located anywhere within the facility. |
| 3.28 | Software | Nurse Station Console | Mandatory | Twenty-four-hour time display and automatic synchronization, including option for daylight savings time changes, configured to facility standard network time source. |
| 3.29 | Software | Nurse Station Console | Mandatory | Call list, active call list, service request, and staff location display in either graphical floor map or list format. |
| 3.30 | Software | Nurse Station Console | Mandatory | Display all active calls in an interactive, graphical floor map mode to include all calling rooms for the covered area. |
| 3.31 | Software | Nurse Station Console | Mandatory | Call display shall be arranged to first display the highest priority call, followed by additional calls in order of priority level and order of placement time. |
| 3.32 | Software | Nurse Station Console | Mandatory | Ability to view additional calls in waiting. |
| 3.33 | Software | Reporting - Enterprise | Mandatory | Reports can pull data from any or all facilities. |
| 3.34 | Software | Reporting - Enterprise | Mandatory | Enterprise reporting must have the ability to show metrics for any or all facilities. |
| 3.35 | Software | Reporting - Local | Mandatory | Ability to run reports based on any information captured. For example: Events, Staff, Badge, Patient, Bed, Area Call Response Times, Call Details, Data Distribution, Staff Summary, Reason, Patient Timeline and Shift. |
| 3.36 | Software | Reporting - Local | Mandatory | All reports and delivery options must be customizable. |
| 3.37 | Software | Reporting - Local | Mandatory | All reports can be exported to Excel for more detailed analysis |
| 3.38 | Software | Reporting - Local | Mandatory | Reporting solutions must be allow for comparison of results, track trends, and identify potential areas of patient-care concerns. |
| 3.39 | Software | Reporting - Local | Mandatory | Information can be displayed as a live dashboard or as a customized report configured to meet specific user specifications. |
| 3.40 | Software | Reporting - Local | Mandatory | Multiple reports can be configured, saved, and delivered to a user's inbox at pre-determined times. |
| 3.41 | Software | Reporting - Local | Mandatory | There is no limit to the number of users or the number of customizable reports. |
| 3.42 | Software | Reporting - Local | Mandatory | Reports can be configured through the application and viewed on any device that can run a web browser. |
| 3.43 | Software | Security | Mandatory | All system applications shall be HIPAA compliant and shall allow for patient name aliases and alternative display methods. |
| 3.44 | Software | Security | Mandatory | Include password protection option for critical and noncritical levels of system setup, allowing access to authorized personnel only. |
| 4.00 | DATA NETWORKING | |||
| 4.01 | Data Networking | Active Directory | Mandatory | Use authentication mechanisms such as Active Directory Federated Services 2019, (ADFS)/Security Assertion Markup Language (SAML) integration options, or Azure AD for Software as a Service (SaaS) integration. |
| 4.02 | Data Networking | Active Directory | Mandatory | Align the user’s Single Sign On (SSO) with their Role Based Permissions, within the application. |
| 4.03 | Data Networking | Active Directory | Mandatory | SSO configurations must be SAML 2.0 or Kerberos-based. |
| 4.04 | Data Networking | Active Directory | Mandatory | ADFS or SAML authentication implementation must have the ability to setup a claims provider trust, have auto updating of the certificate connecting the ADFS/SAML trust, and not be required to point to a single domain controller. |
| 4.05 | Data Networking | Active Directory | Desirable | CCHCS/CDCR prefer the solution’s RBAC controls integrate with the CCHCS Active Directory Groups. |
| 4.06 | Data Networking | Communication | Mandatory | System must not require or rely on a CDCR/CCHCS furnished PBX for functionality to comply with UL 1069. |
| 4.07 | Data Networking | Configuration | Mandatory | Capable of supporting a VLAN configuration to separate activity on the nurse call network from other facility LAN traffic. NCS can span multiple subnets on a facility’s LAN. |
| 4.08 | Data Networking | Data Center | Mandatory | Capable of running on CDCR/CCHCS provided servers for enterprise functionality common to all facility nursing units. |
| 4.09 | Data Networking | Hardware | Mandatory | CDCR/CCHCS will provide no more than one LAN port for HL7 integration to the entire network. |
| 4.10 | Data Networking | Hardware | Mandatory | The NCS network shall be scalable to support facilities of any size as a contiguous, interconnected system. Multiple buildings and intra-building connections may be linked together utilizing TCP/IP data networking. |
| 4.11 | Data Networking | Hardware | Mandatory | The NCS contractor shall not use CDCR/CCHCS supplied networking equipment for NCS UL 1069 listed operations. |
| 4.12 | Data Networking | Hardware | Mandatory | All vendor-provided NCS data networking components must comply with UL 1069. |
| 4.13 | Data Networking | Hardware | Mandatory | All vendor-provided NCS data networking components must be of similar manufaturer and make up one homogenous interoperable network, unless approved by CDCR/CCHCS. |
| 4.14 | Data Networking | Hardware | Mandatory | All NCS equipment shall use plug-in connectors, and all switches, console stations, and controllers shall use standard RJ-45 modular connections. All cables must be labeled at termination points. |
| 4.15 | Data Networking | Infrastructure | Mandatory | NCS wiring in new installations shall comply with CDCR/CCHCS department standards (currently plenum rated CAT-6). |
| 4.16 | Data Networking | Infrastructure | Mandatory | Multi-conductor cable for non-Ethernet functions is acceptable if specified by manufacturer, and/or is present in existing infrastructure. |
| 4.17 | Data Networking | Infrastructure | Mandatory | Nurse-patient communications network wiring shall not be run in the same conduit with Class 1 AC power distribution. |
| 4.18 | Data Networking | Infrastructure | Mandatory | Nurse communications cabling may be run with other low voltage and data cables, where permitted by code. Nurse communications cabling shall be separated from any high voltage AC or DC wiring that exceeds 70.7 volts. |
| 4.19 | Data Networking | Interfaces | Mandatory | Ability to interface with peripheral medical devices such as, wireless fall alarms (bed/wheelchair pads), IV pumps, to receive alarms. |
| 4.20 | Data Networking | Interfaces | Mandatory | Ability to report hardware/software based alarms to the facility EHRS and wireless devices. |
| 4.21 | Data Networking | Interfaces | Mandatory | System must be able to bi-directionally interface with the facility EHRS system via HL7 protocol to automatically populate patient information at nurse station consoles. |
| 4.22 | Data Networking | Interfaces | Mandatory | NCS interface options shall be capable of supporting bedside rail event initiation controls, wireless bed event initiation, monitoring wireless device notifications, HL7, and Real-Time Locating System (RTLS). |
| 4.23 | Data Networking | Interfaces | Mandatory | Ability to interface with facility fire alarm system, as per as-built plans. |
| 4.24 | Data Networking | Interfaces | Mandatory | Ability to annunciate dome light and nurse console alarms, when triggered by facility fire alarm system. |
| 4.25 | Data Networking | Interfaces | Mandatory | System must be able to interface with more than one wireless communication system simultaneously. |
| 4.26 | Data Networking | Interfaces | Mandatory | Ability to interface with, at a minimum: |
a- The CCHCS Enterprise Health Record System (EHRS) b- Microsoft Active Directory (AD) c- Voice over IP (VoIP) d- Wireless communication systems such as, iPhones, pagers, or other industry standard mobile devices e- Real Time Location Systems (RTLS) f- CCHCS/CDCR Fire Alarm System.
| 4.27 | Data Networking | Security | Mandatory | CDCR/CCHCS will provide one VPN (Virtual Private Network) connection for diagnosing issues and maintaining the system. |
| 5.00 | TRAINING | |||
| 5.01 | Training | General | Mandatory | OEM training must be available to CDCR/CCHCS employees for the life of the system. |
| 5.02 | Training | General | Mandatory | Develop, with CCHCS Training Units, training content, class outlines, presentations, and user guides for both in-person and computer-based training. |
| 5.03 | Training | General | Mandatory | Provide training and training material for the following groups: T4T, End Users, Information Technology Support, Plant Operations/Facility Support. |
HRA Detailed Requirements
1.0 General Requirements Spreadsheet
Page &P of &N
Experience Requirements
| Unique ID | ||||
| #.x | Requirement Type | Mandatory/ Desirable | Requirement Description | Contractor Certification |
("Can Meet" or "Cannot Meet" the Requirement or select an option where specified) Experience Summary/ Resume Reference (Specify Experience Summary number or Personnel Name and Resume Page #/Location)
| 6.00 | COMPANY | ||
| 6.01 | Company/Contractor | Mandatory | Must possess one or more of the following: |
a) Either a California Contractors State License Board (CSLB) C-7 or C-10 Electrical Contractor License or
b) CSLB B – General Building Contractor License with a sub-Contractor with one or more of the required C licenses
OR
have reciprocity agreement currently in place, if located outside of California.
| If "Can Meet"; specify which and | ||||
| provide copies of relevant licenses or agreement | ||||
| 6.02 | Company/Contractor | Mandatory | Minimum of five (5) years experience/knowledge in implementing and supporting Nurse Call Systems. | |
| 6.03 | Company/Contractor | Mandatory | A minimum of three (3) technicians possessing certification of Confined Space Training. | |
| 6.04 | Company/Contractor | Desirable | Successfully completed NCS installations in detention and/or psychiatric nursing units. | How many? |
a) 1 installation
b) 2 installations
c) 3 or more installations
d) No experience with this type of installation
| 6.05 | Company/Contractor | Desirable | Methodology for mitigating distruption to existing Nursing units when replacing legacy Nurse Call Systems | |
| 7.00 | ENGAGEMENT MANAGER | |||
| 7.01 | Engagement Manager | Mandatory | Five years experience/knowledge in Project Management and Nurse Call Systems | |
| 7.02 | Engagement Manager | Desirable | Possess Project Management Professional (PMP) Certification, or similar education | |
| 7.03 | Engagement Manager | Desirable | Possess Certified Associate in Project Management (CAPM) Certification, or similar education | |
| 8.00 | NCS LEAD TECHNICIAN | |||
| 8.01 | Lead NCS Technician | Mandatory | Five years experience/knowledge in implementing and supporting Nurse Call Systems | |
| 8.03 | Lead NCS Technician | Mandatory | OEM Trained on proposed NCS | |
| 9.00 | NCS TECHNICIANS | Two (2) Technicians Required | ||
| 9.01 | NCS Technician | Mandatory | Minimum of 3 years of experience/knowledge in implementing and supporting Nurse Call Systems | |
| 9.02 | NCS Technician | Mandatory | OEM Trained on proposed NCS | |
| 10.00 | NURSING PROGRAM SME | |||
| 10.01 | Nursing Program SME | Desirable | Registered Nurse (RN) Degree | Specify Degree(s): |
a) CNA
b) LVN
c) RN
d) No Degree
| 10.02 | Nursing Program SME | Desirable | Minimum of 3 years experiencing advising clients on nursing unit functionality | Number of years experience? |
| 10.03 | Nursing Program SME | Desirable | OEM Trained on proposed NCS | |
| 11.00 | NCS TRAINERS | |||
| 11.01 | NCS Trainers | Mandatory | OEM Trained on proposed NCS | |
| 11.02 | NCS Trainers | Desirable | Minimum of 2 years of experience providing training on Nurse Call Systems | Number of years experience? |
HRA Detailed Requirements
1.0 General Requirements Spreadsheet
Page &P of &N
Glossary
| NCS Detailed Requirements Glossary | |
| Acronym or Term | Description |
| Code Calls | The American Hospital Association has recommended a set of codes for hospitals across the nation to use for types of emergencies (e.g. Code Red: Fire, smoke, or smell of smoke; Code Blue: Cardiac or respiratory arrest or medical). |
| EHRS | The CCHCS Electronic Health Records System (currently Cerner). |
| GUI | Graphical User Interface |
| HIPAA | Health Insurance Portability and Accountability Act |
| HL7 | Health Level Seven is a standard for exchange of information between medical systems. |
| Hot-swappable | Capable of replacement without requiring power down or restart of core system components. |
| NCS | Nurse Call System |
| OEM | Original Equipment Manufacturer |
| Quiet Mode | Ability to reduce volume |
| RTLS | Real-Time Locating System |
| Swing/Move | Ability to reassign a patient room from one nursing staff to another. |
| T4T | Training For Trainers |
| UL-1069 | Standard for Hospital Signaling and Nurse Call Equipment – This Standard applies to the traditional equipment found in the hospital environment. |
| Zone Light | Domes can be configured in a hospital setting to allow for visibility to a non-visible/hidden room. If the hidden room's dome light flashes, so will the visible domes in that zone, alerting the nursing personnel. |
&"Arial,Bold"CCHCS RFO EXHIBIT A-1 HRA Detailed Requirements Workbook Glossary
5.0 R&H DELETE
| Unique ID | |||||||
| 5.0 | Requirement Type | Category | Reference Category | Bidder's Library Sample | Priority | Requirement Description | MEETS REQUIREMENT? |
| YES or NO | DESCRIPTION |
Provide a detailed description on how the product will meet the requirement.
| 5.1 | Functional | Business | Recruitment and Hire: Section | HRA 1, 2 | |||
| BP 1-6, 8, 9 | Mandatory | The solution shall provide a Recruitment and Hiring section to manage and track all position recruitments from the point of request through new employee start date. | |||||
| 5.2 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall record, store, track and manage the entire lifecycle of a Recruitment and Hire from initiation through final determination. | ||
| 5.3 | Functional | Business | Recruitment and Hire: Audits | Mandatory | The solution shall provide the ability to access and review the complete lifecycle of a Recruitment and Hire for audit purposes. | ||
| 5.4 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall provide the ability to open a new RPA within a recruitment and pre-populate the RPA with the associated recruitment data. | ||
| 5.5 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall ONLY auto-send notifications associated to "Active" recruitments. | ||
| 5.6 | Functional | Business | Recruitment and Hire: Dashboard Metrics | Highly Desirable | The solution shall provide a Dashboard/Roll Up for Out of Compliance Metrics associated to the Recruitment and Hire section. | ||
| 5.7 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall provide an “At a Glance” view of a selected Recruitment. | ||
| 5.8 | Functional | Business | Recruitment and Hire: General | Highly Desirable | The solution should provide the ability to recognize which Recruitment and Hire documents/forms/templates are required based on the agency code in the position number. | ||
| 5.9 | Functional | Business | Recruitment and Hire: General | Highly Desirable | The solution should provide the ability to manage and track submission and receipt by date, of all candidate forms. | ||
| 5.10 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall provide the ability to access, open and modify documentation associated to a Recruitment and Hire. | ||
| 5.11 | Functional | Business | Recruitment and Hire: General | RH 1-11 |
RH-IF 1-12
RH-EF 1-22
| RH-L 1-14 | Mandatory | The solution shall provide the capability to populate Recruitment and Hire: letters, forms, and templates, save to recruitment files, and link to a specific applicant. | |||||
| 5.12 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall provide the ability to view, add, modify, and delete Recruitment and Hire data and associated documentation based on user role. | ||
| 5.13 | Functional | Business | Recruitment and Hire: General | Mandatory | The solution shall display viewable history of all Recruitment and Hire data modifications, and identify the user who performed the modification by first and last name, date, and time stamp. | ||
| 5.14 | |||||||
| AMENDED | Functional | Business | Recruitment and Hire: Security | Highly Desirable | The solution shall provide the ability to institute internal access security controls in the event that internal applicants are applying for positions where they may be able to access the position's confidential documentation. | ||
| 5.15 | Functional | Business | Recruitment and Hire Data Elements | Mandatory | The solution shall provide at least the following 271 Recruitment and Hire data fields and the associated business rules to manage and track various Recruitment and Hire activities for display, pre-population, manual entry, and calculation, if data exists. | ||
| 5.15.1 | Functional | Business | Recruitment and Hire: | ||||
| Hire Initiation | Mandatory | The solution shall display an "Initiator" data field that is pre-populated based upon the Initiator's log-in credentials. | |||||
| 5.15.2 | Functional | Business | Recruitment and Hire: | ||||
| Hire Initiation | Mandatory | The solution shall display the "Initiator" data field with a drop-down selection of users in the Directory by Name View. | |||||
| 5.15.3 | Functional | Business | Recruitment and Hire: | ||||
| Hire Initiation | Highly Desirable | The solution should associate an "auto fill" feature to the Initiator data field which will return the associated drop-down list based on the first few letters populated for user selection OR |
will pre-populate the field based on unique data input.
| 5.15.4 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a 'Unique Identifier' data field to link all components of a Recruitment (RPA, STD. 607, other documentation, Job Controls, etc.). | ||
| 5.15.5 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Date Vacant" date field. | ||
| 5.15.6 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Reason for Vacancy" data field with a drop-down selection (TBD). | ||
| 5.15.7 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Highly Desirable | The solution should display a "Pending Vacancy" Date data field. | ||
| 5.15.8 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation Notification | Highly Desirable | The solution should auto-send an email notification upon entry of a Pending Vacancy Date (distribution TBD Analyst and Managers). | ||
| 5.15.9 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Date Notified of Vacancy" date field. | ||
| 5.15.10 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation Notification | Highly Desirable | The solution should auto-send an email notification to the Analyst (distribution list TBD) to begin the recruitment process when Date Notified of Vacancy data field is populated. | ||
| 5.15.11 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Rollout Schedule Date" data field. |
Format: MM/YY
| 5.15.12 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Fill By Date" data field. | ||
| 5.15.13 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display the question: "Certification List?" with Yes and No selections.. | ||
| 5.15.14 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Certification List Requested Date" data field; IF Certification List Response is Yes. | ||
| 5.15.15 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation Notification | Mandatory | The solution shall auto-send a Certification List Request to the Certification Unit (distribution list TBD); IF the Cert Requested Date field is Yes. | ||
| 5.15.16 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display the question: "New Cert Required?" with Yes and No selections. | ||
| 5.15.17 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "New Certification Request Date" field; IF New Cert Required Response is Yes. | ||
| 5.15.18 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall auto-send a New Certification Request to the Certification Unit; IF New Cert Required Response is Yes. | ||
| 5.15.19 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display the question: Previous Cert Ordered? with Yes and No selections. | ||
| 5.15.20 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Assigned Analyst" data field. | ||
| 5.15.21 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Agency" data field to display the complete Agency name. | ||
| 5.15.22 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Physical Work Location" data field. | ||
| 5.15.23 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "SAP Number" data field. | ||
| 5.15.24 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display 4 separate data fields together to identify an employee's "Position Number": |
Format: (NNN NNN NNNN NNN) Field 1: Agency (3 digits) Field 2: Unit (3 digits) Field 3: Class Code (4 digits) Field 4: Serial (3 digits)
| 5.15.25 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Civil Service Classification" data field to pre-populate based on the Class Code in the associated Position Number. | ||
| 5.15.26 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a question: "Interchangeable?" with a check box selection. | ||
| 5.15.27 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Assignment Level" data field. | ||
| 5.15.28 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Highly Desirable | The solution should display a "Collective Bargaining Identified" (CBID) data field. |
Format: Alphanumeric
| 5.15.29 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Tenure" data field with a drop-down selection of the following options: |
Permanent Limited Term Temporary Retired Annuitant
TAU
CEA
Exempt
| 5.15.30 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Limited Term Reason" data field with drop-down selection; IF Tenure is Limited Term to include: |
MROR due to long term sick Leave of Absence Outside LT appointment Others TBD
| 5.15.31 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Limited Term (LT) Months" data field; IF the Tenure is Limited Term. | ||
| 5.15.32 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Expiration Date" data field; IF Limited Term is selected in the Tenure field. | ||
| 5.15.33 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "RA Months" data field; IF the Tenure is Retired Annuitant. | ||
| 5.15.34 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "RA Expiration Date" data field; IF the Tenure is Retired Annuitant. | ||
| 5.15.35 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Number of Months" data field; IF TAU is selected in the Tenure field. | ||
| 5.15.36 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Expiration Date" data field; IF TAU is selected in the Tenure field. | ||
| 5.15.37 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation Alert | Highly Desirable | The solution should display an alert "Verify if RPA has been Completed"; IF the Tenure data field has been modified, to ensure consistency between an RPA and the Application. | ||
| 5.15.38 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Time Base" data field with a drop-down of the following for selection: |
Full Time Intermittent Part Time
| 5.15.39 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "PT Fraction of Time" data field with a drop-down for selection (TBD); IF the Time Base selected is Part-time. | ||
| 5.15.40 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Confidential Designation" data field. | ||
| 5.15.41 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display an "Alternate Range/CEA Level" data field. | ||
| 5.15.42 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall provide the ability to associate multiple position numbers to one recruitment and Job Control Number. | ||
| 5.15.43 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display the question: "Multiple Positions associated to recruitment?" with an indicator for selection. | ||
| 5.15.44 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display a "Number of Positions" data field for drop-down selection; IF Multiple Positions associated to recruitment response is Yes. | ||
| 5.15.45 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall display the question: Are you sure you want to create XX positions? with Yes and No selections; IF the Number of Positions data field is populated. | ||
| 5.15.46 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Mandatory | The solution shall generate additional position line items to associate to the recruitment based upon the Number of Positions data field. The generated line items shall replicate the data elements from the primary line item, with the exception of the Serial Number in the Position Number which will be populated as XXX. |
(If HR is recruiting for a specific position (nurse) and has 5 authorized positions to fill at the same time they want to be able to track and manage all 5 positions using that one recruitment. Recruitment would remain open until all positions are filled).
| 5.15.47 | Functional | Business | Recruitment and Hire: | |
| Hire Initiation | Highly Desirable | The solution should display a question: "Subject to Hiring Restriction?" with a drop down selection of: |
HCHER
Ratio HCHER and Ratio None
| 5.15.48 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "HCHER Request Submitted Date" data field when HCHER OR HCHER and RATIO is selected. | ||||
| 5.15.49 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "HCHER Request Approved" data field with Yes and No selections; IF HCHER Date Submitted is populated. | ||||
| 5.15.50 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "HCHER Approved Date" data field; IF the HCHER Approved Response is Yes. | ||||
| 5.15.51 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "Ratio Submitted Date" data field; IF Ratio OR HCHER and Ratio is selected. | ||||
| 5.15.52 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "Ratio Request Approved" data field with Yes and No selections; IF the Ratio Date Submitted field is populated. | ||||
| 5.15.53 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Highly Desirable | The solution should display a "Ratio Approved Date" data field; IF the Ratio Approved Response is Yes. | ||||
| 5.15.54 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Mandatory | The solution shall display a "Due Date for Advertisement and Certification" data field. | ||||
| 5.15.55 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Mandatory | The solution shall display a "General Recruitment Comments" data field that is associated to the entire recruitment. | ||||
| 5.15.56 | Functional | Business | Recruitment and Hire: | |||
| Hire Initiation | Desirable | The solution should display a name and date stamp to each Comment added to the General Recruitment Comments data field. | ||||
| 5.15.57 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Final Duty Statement Approval Date" data field. | ||||
| 5.15.58 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Highly Desirable | The solution should display the question: "Exempt from Advertising?" with an indicator selection. | ||||
| 5.15.59 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a question: "Subject to Post & Bid (P&B)?" with Yes and No selections. | ||||
| 5.15.60 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Post & Bid Local?" with Yes and No selections; IF Post & Bid Response is Yes. | ||||
| 5.15.61 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Date Local Post & Bid Advertised" data field. | ||||
| 5.15.62 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Local Post & Bid Date Cleared" data field; IF the Local Post & Bid Response is Yes. | ||||
| 5.15.63 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Post & Bid Statewide?" with Yes and No selections; IF Post & Bid Response is Yes. | ||||
| 5.15.64 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Statewide Post & Bid Date Cleared" data field; IF the Statewide Post & Bid Response is Yes. | ||||
| 5.15.65 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Job Control Number?" with Yes and No selections. | ||||
| 5.15.66 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Job Control Number" data field; IF Job Control Number Response is Yes. | ||||
| 5.15.67 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Final Filing Date" field. | ||||
| 5.15.68 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement Notification | Desirable | The solution should auto-send an email notification one day prior to a Job Ad's Final Filing Date (distribution list TBD). | ||||
| 5.15.69 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Until Filled?" with Yes or No selection. | ||||
| 5.15.70 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display an "Until Filled Date" data field; IF Until Filled Response is Yes. | ||||
| 5.15.71 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement Notification | Highly Desirable | The solution should calculate and auto-send a notification to the "Assigned Analyst and Manager" when the Total Days for Job Ad field calculation is one day prior to being out of compliance. | ||||
| 5.15.72 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display an "Actual Date Advertised" data field. | ||||
| 5.15.73 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Highly Desirable | The solution shall display the question: "Post on CCHCS Career Website?" with an indicator for selection. | ||||
| 5.15.74 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement Notification | Highly Desirable | The solution should auto-send a notification, to the Workforce Development unit advising that a job was posted on CalHR ECOS and a request to post the job on the CCHCS.ca.gov website; IF the Post on Career website response is Yes. | ||||
| 5.15.75 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Highly Desirable | The solution should display the question: "Posted on CCHCS Career Website?" with an indicator for selection. | ||||
| 5.15.76 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Highly Desirable | The solution should display a "CCHCS Career Website Job Number" data field; IF the Posted on CCHCS Career website response is Yes. | ||||
| 5.15.77 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Total Days for Job Ad" to be Posted data field. | ||||
| 5.15.78 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the Total Days for Job Ad field calculation in RED; IF the calculation exceeds the compliance metric. | ||||
| 5.15.79 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Job Ad Reason for Non-Compliance" field with a drop-down list of Reasons for selection (list TBD). | ||||
| 5.15.80 | Functional | Business | Recruitment and Hire: | |||
| General | Mandatory | The solution shall display a "Comments" data field for all Reason for Non-compliance data elements when the Reason of "Other" is selected. | ||||
| 5.15.81 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display an "Actual Certification Ordered Date" data field; IF the user selects the data field the system will auto-populate the current date. | ||||
| 5.15.82 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Total Days for Certification" to be ordered data field. | ||||
| 5.15.83 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Certification Reason for Non-Compliance" data field with a drop-down list of Reasons for selection (list TBD). | ||||
| 5.15.84 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the "Total Days for Certification" field calculation in RED; IF the calculation exceeds the 7 calendar day compliance metric. | ||||
| 5.15.85 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Total Days for Advertisement and Certification Process" compliance metric. | ||||
| 5.15.86 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the "Total Days for Advertisement and Certification Process" field calculation in RED; IF the calculation exceeds the 7 calendar day compliance metric. | ||||
| 5.15.87 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Desirable | The solution should provide the ability to upload a CCHCS Career Website Job link to the associated recruitment. | ||||
| 5.15.88 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Re-advertisement?" with Yes or No selection. | ||||
| 5.15.89 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display a "Re-advertisement Date" data field; IF Re-advertisement Response is Yes. | ||||
| 5.15.90 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall reset all compliance metrics with the exception of Hire Tracking Log column “BY” Total Days to Complete Hire Process with Credentialing AND Hire Tracking Log column “BZ” Total Days to Complete Hire Process without Credentialing; IF Re-advertisement and New Cert Request Dates are populated. | ||||
| 5.15.91 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Mandatory | The solution shall display the question: "Extend Job Ad?" with an indicator for selection. | ||||
| 5.15.92 | Functional | Business | Recruitment and Hire: | |||
| Job Advertisement | Highly Desirable | The solution shall display the question: "Update to CCHCS Career Website Job Post required?" with an indicator for selection. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .