Newborn Screening Laboratory Information Management System, Maintenance, and Support Services

The Vendor is required to provide a commercial-off-the-shelf (COTS) Laboratory Information Management System (LIMS), maintenance, and support services for the department Newborn Screening (NBS) Program.
- The State prefers to leverage either the on-premises State-hosted virtualized data center or a scalable State tenant in an externally hosted approved cloud platform.
- The State’s Infrastructure as a Service Program currently includes Google (GCP) and Amazon Web Services (AWS). The hosting platform must be approved by the State.
- The system must allow for user configuration of new protocols.
- The system must allow for user configuration of new data fields.
- The system must allow for user configuration of new alerts.
- The system must allow for user configuration of new workflows.
- The system must allow users to update case definitions, role-based permissions, and result reporting logic as new program needs arise.
- The system must allow users to modify simple configurations, such as adjusting dropdown options, workflows, and lab report parameters.
- Support secure offline data entry when connectivity is unavailable, with automatic synchronization once reconnected.
- Enforce local encryption, data validation, and retention rules for offline sessions.
- The LIMS must provide a failover solution to ensure continued data input and processing in the event that a key system goes down, preventing operational disruption and loss of data.
- LIMS provides service resiliency by means of physically separate data centers or failover environments.
- Backups scheduled daily, weekly, or at other appropriate intervals.
- must provide redundant storage locations to prevent data loss with automated processes to help maintain consistency and reliability.
- Backups should be encrypted and stored securely to prevent unauthorized access and/or data breaches.
- Must support regular backup testing of the restore process to ensure backup process is functional and efficient when needed.
- Must include well documented backup strategy to support the restore process effectively during emergencies.
- Transition Plan & Change Management Plan
• Must include a clearly defined deployment plan and transition plan, including pre-release testing requirements and sign-off criteria.
• Must implement a standardized process for submitting, categorizing, evaluating, and approving change requests throughout the contract period.
• Must provide ongoing status updates and maintain a version-controlled change log with detailed entries, including modification date, responsible personnel, and implementation notes.
• Must verify that the system meets all business and technical requirements through functional, regression, and integration testing before transitioning to production.
• Must verify the security of the system meets all security and compliance requirements through penetration testing, access control validation, encryption testing, secure data storage and transmission testing, and audit log verification before transitioning to production.
• Must verify system performance through response time testing, load testing, and number of millions of Instructions per Second (MIPS) at which the system functions before transitioning to production.