Laboratory Information Management System

The Vendor is required to provide comprehensive laboratory information management system (LIMS) solution for its clinical laboratory in city.
- The LIMS will be utilized by various sections within the laboratory for efficient management, analysis, and reporting of laboratory data.
- The City has approximately 23,000 employees with approximately 500 employees involved in the procurement and/or contracting process.
- System include:
•    The system shall support electronic test orders and results (ETOR).
•    Requests for analysis shall be created in the system and shall have a unique identifier. The status of a request shall be identifiable at any time during its life cycle.
•    The system shall provide a workflow for approving or rejecting the request for analysis.
•    The system shall associate a request with a sample/specimen.
•    The system shall allow the ability to use an existing sample in a new request.
•    The system shall allow an authorized user to update requests before, during, and after requested analyses have been completed.
•    Requests shall be marked as completed/closed upon completion of all sample analyses.
•    Requests can be assigned by different suites of tests (grouping) rather than selecting individual tests one by one (ability to select multiple at once).
•    Request shall allow for one or more samples and information common to all the samples in the request to be recorded once at the request level.
•    The system shall reject incoming electronic test requests if all required data is not present. I.e., provider NPI is required, if blank then system will not accept test request.
•    The system shall support configurable request templates. Templates shall be configurable based on client business rules (i.e., sample, analysis type, roles, and customers).
•    The system shall have the ability to import data files in multiple formats (*.csv, *.txt, etc.) To support various functionality, i.e. Test request creation, data tables populated, create new system records, etc.)
•    The system should have the ability to mass delete / suspend received test requests which never had a sample received to test against. The system shall allow the creation of ad hoc samples for those delivered via walkup, drop-box, couriered, or mailed. The analyst shall be able to choose tests and analyses via a sample template.
•    The system shall support manually logging of samples either as part of a batch customer, as part of a QC sampling plan, or as individual, ad-hoc, unrelated samples.
•    Sample receipt shall be recorded in the system (user, location, and date/time stamp) using sample barcodes, and have the ability to print the barcode labels as we collect the samples simultaneously.
•    The system shall have separate fields for patient first, middle, and last name. 
•    The system shall be able to manage the process of initiating, receiving, testing, and releasing of samples; and if limits are defined, compare that data versus limits. 
•    The system shall allow the manual and automated (e.g. Csv file, API, web services, etc.) Creation of samples.
•    The system shall not contain redundant fields requiring updating in multiple areas. Samples in the system can be assigned to one or more workflows/tests.
•    When samples are logged or received in the lab, the associated tests can be automatically added to an analyst’s or a role's backlog.
•    The system shall have the ability to have a default user and/or role for a given study, test, and test combination.
•    The system shall provide the ability to automatically assign work (preparation, analysis, reviews, and other activities) to individuals or roles based on business rules and workflow or manually by a leader/manager.

- Contract Period/Term: 2 years
- Pre-Proposal Conference Date: October 30, 2025
- Questions/Inquires Deadline: November 6, 2025