Attachment G - Traceability Matrix FINAL.xlsx
XLSX spreadsheet 129 KB Posted
- Attached to
- Laboratory Information Management System RFP
- Solicitation number
- 25-448DOIT-ADMIN-B-46893
- Issued by
- St. Clair County, Illinois
About this file
The document is a Traceability Matrix for the State of Illinois Department of Innovation and Technology's Laboratory Information Management System (LIMS) Request for Proposal (RFP 25-448DOIT-ADMIN-B-46893). The matrix is a comprehensive spreadsheet detailing desirable business and technical functionalities, service requirements, and mandatory performance requirements for a new laboratory information management system. The document provides a detailed breakdown of capabilities across several key areas including specimen intake, sample management, test and assay management, results management, inventory logistics, and reporting and delivery data.
The matrix requires potential vendors to respond to specific functionality requirements by indicating whether they can meet each requirement, how they will meet it (through out-of-the-box solutions, configuration, customization, or third-party products), and provide explanatory comments. The requirements cover a wide range of laboratory management needs, such as patient information management, sample tracking, test protocol definition, result validation, inventory management, barcode tracking, reporting capabilities, and integration with existing systems like OpenText Fax Solutions. The document is structured to allow precise vendor responses and enable the State of Illinois to comprehensively evaluate potential LIMS solutions against their specific operational requirements.
View the file
Other files
Show all 18
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
1. Title Page
| State of Illinois Department of Innovation and Technology |
| Laboratory Information Management System RFP |
| 25-448DOIT-ADMIN-B-46893 |
| Attachment G - Traceability Matrix |
2. Table of Contents
| State of Illinois Department of Innovation and Technology |
| Laboratory Information Management System RFP |
| 25-448DOIT-ADMIN-B-46893 |
| Attachment G - Traceability Matrix |
| Instructions | ||
| This page provides a Table of Contents for the Traceability Matrix (TM). Each tab is defined and includes a hyperlinked title for easy navigation. | ||
| Tab Title | ||
| Hyperlinked | Description | |
| 1. Title Page | Details the RFP and Attachment Title |
No response required in this tab
2. Table of Contents Details all tabs within the workbook No response required in this tab
3. Instructions Provides instructions for tabs the Offeror must fill out in their response No response required in this tab
4. Desirable Business Functionalities Details all desirable business functionalities for the solicitation Response required in tab
5. Desirable Technical Functionalities Details all desirable technical functionalities for the solicitation Response required in this tab
6. Service Requirements Details all service requirements for the solicitation, including deliverables, and submission timing/frequency of these deliverables No response required in this tab
7. Mandatory Performance Req. Details all performance requirements for the solicitation Response required in this tab
8. Performance Definitions Details performance metrics and definitions the contracted Vendor must maintain through their Solution No response required in this tab
9. Key Staff Mandatory and Non-mandatory, key staff roles, responsibilities, and experience desired to support successful implementation of the Solution No response required in this tab
3. Instructions
| Instructions and Key Definitions | ||
| This tab describes the tabs that require Offeror input, specifically tab 4. Desirable Business Functionalities , tab 5. Desirable Technical Functionalities, and tab 7. Mandatory Performance Req. Offeror must review all tabs and complete the actions described. | ||
| Instructions and Definitions for tab 4. Desirable Business Functionalities | ||
| Column Letter | Column Title | Instructions and Definitions |
| A | Requirement ID | Provides the unique ID for the Solution Desirable Business Functionality. |
| Instructions: This cell is locked and unable to be revised. | ||
| B | Level 0 Capability | Classifies the functionalities by level 0 capabilities. |
| Instructions: This cell is locked and unable to be revised. | ||
| C | Level 1 Capability | Classifies the functionalities by level 1 capabilities. |
| Instructions: This cell is locked and unable to be revised. | ||
| D | Desirable Business Functionality | Detailed description of the desirable business functionality. |
| Instructions: This cell is locked and unable to be revised. | ||
| E | Desirable Business Functionality Met | Possible Values: |
A. Yes: Offeror Solution can meet this desirable business functionality.
B. No: Offeror Solution cannot meet this desirable business functionality.
| Instructions: Offeror shall use the provided drop-down menu to identify their ability to meet each desirable business functionality. | ||
| F | Solution Method | Possible Values: |
A. Out of the Box: The desirable functionality will be met through available functionality.
B. Configuration: Adjusting the settings and options within the software to meet the desirable functionality without altering the core code of the software.
C. New Development/Customization: The desirable functionality will be met through customization, which requires custom code development.
D. Third-Party Product: The desirable functionality will be met by commercially available third-party software and is not included in this Proposal. NOTE: The name of the proposed third-party software vendor and proposed components must be indicated under "Explanation or Comments".
E. None: The desirable functionality will not be met by the Solution.
| Instructions: Offeror shall use the provided drop-down menu to identify how they can meet each desirable business functionality. | ||
| G | Explanation or Comments | Free text field. |
| Instructions: Offeror shall provide explanation or comments to explain entries in column F when necessary. | ||
| Instructions and Definitions for tab 5. Desirable Technical Functionalities | ||
| Column Letter | Column Title | Instructions and Definitions |
| A | Requirement ID | Provides the unique ID for the Solution Desirable Technical Functionality. |
| Instructions: This cell is locked and unable to be revised. | ||
| B | Level 0 Capability | Classifies the requirements by level 0 capabilities. |
| Instructions: This cell is locked and unable to be revised. | ||
| C | Level 1 Capability | Classifies the requirements by level 1 capabilities. |
| Instructions: This cell is locked and unable to be revised. | ||
| D | Desirable Technical Functionality | Detailed description of the desirable technical functionality. |
| Instructions: This cell is locked and unable to be revised. | ||
| E | Desirable Technical Functionality Met | Possible Values: |
A. Yes: Offeror Solution can meet this desirable technical functionality.
B. No: Offeror Solution cannot meet this desirable technical functionality.
| Instructions: Offeror shall use the provided drop-down menu to identify their ability to meet each desirable technical functionality. | ||
| F | Solution Method | Possible Values: |
A. Out of the Box: The desirable functionality will be met through available desirable technical functionality.
B. Configuration: Adjusting the settings and options within the software to meet the desirable technical functionality without altering the core code of the software.
C. New Development/Customization: The desirable technical functionality will be met through customization, which requires custom code development.
D. Third-Party Product: The desirable technical functionality will be met by commercially available third-party software and is not included in this Proposal. NOTE: The name of the proposed third-party software vendor and proposed components must be indicated under "Explanation or Comments".
E. None: The desirable technical functionality will not be met by the Solution.
| Instructions: Offeror shall use the provided drop-down menu to identify how they can meet each desirable technical functionality. | ||
| G | Explanation or Comments | Free text field. |
| Instructions: Offeror shall provide explanation or comments to explain entries in column F when necessary. | ||
| Instructions and Definitions for tab 7. Mandatory Performance Req. | ||
| Additional Information |
| Column Letter | Column Title | Instructions and Definitions |
| A | ID | |
| Instructions: This cell is locked and unable to be revised. | ||
| B | Service Level Requirement (SLR) Name | |
| Instructions: This cell is locked and unable to be revised. | ||
| C | Service Level Requirement (SLR) Description/Objective | |
| Instructions: This cell is locked and unable to be revised. | ||
| D | Target | |
| Instructions: This cell is locked and unable to be revised. | ||
| E | Measurement Formula | |
| Instructions: This cell is locked and unable to be revised. | ||
| F | Service Level Requirement (SLR) Reporting Period | |
| Instructions: This cell is locked and unable to be revised. | ||
| G | Measurement of Non-Compliance | |
| Instructions: This cell is locked and unable to be revised. | ||
| H | Exceptions | A free text field for the Offeror to use to document any proposed excpetions to the SLR. |
Note: DoIT will not negotiation any SLRs if exceptions are not proposed in the Offer.
Instructions: Offeror shall provide any exceptions to the SLR in column H.
4. Desirable Business Fn.
| ID# | Level 0 Capability | Level 1 Capability | Desirable Business Functionality | Desirable Business Functionality Met | Solution Method | Explanation or Comments | Back to tab 3. Instructions |
| B1 | Coordinate Specimen Intake Process and Sample Management | Patient Management | The solution should manage patient identification and patient information including, but not limited to: |
a. patient demographics
b. name
c. date of birth (DOB)
d. contact information
e. other relevant demographics as determined by DoIT Optional -
a. sex at birth
b. ethnicity
c. race B2 Coordinate Specimen Intake Process and Sample Management Sample Management The solution should allow easy and efficient sample tracking, registration, and identification, including, but not limited to:
a. single specimen ID which does not change from accessioning to reporting
| B3 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should support sample logging, sample history tracking and provide a sample history audit trail |
| B4 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should track samples referred to other laboratories for testing from data entry to final report |
| B5 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should manage sample information from collection to result reporting |
| B6 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should manage sample tracking from collection to result reporting |
| B7 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should manage sample accessioning from collection to result reporting |
| B8 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should be able to accept and manage clinical sample information including, but not limited to the following: |
a. patient/source name
b. sex
c. date of birth
d. address
e. submitter
f. external ID
g. date/time collected
h. test to be performed
i. specimen source B9 Coordinate Specimen Intake Process and Sample Management Sample Management The solution should accept and manage environmental sample information including, but not limited to the following:
a. Supply facility number
b. Name
c. Location
d. Field and Preservation Data
e. Collection date/time
f. Collector's name and address
g. Name and address of additional contacts
h. Sample type and matrix
| B10 | Coordinate Specimen Intake Process and Sample Management | Sample Management | The solution should allow for the attachment of laboratory reports in PDF format to the sample within IDPH's LIMS system as needed (e.g., lab reports from specimens referred to other laboratories for processing) |
| B11 | Perform Specimen Analysis | Test and Assay Management | The solution should support a wide range of tests, methods, and protocols commonly used in the laboratory |
| B12 | Perform Specimen Analysis | Test and Assay Management | The solution should deliver a fully completed LIMS testing module for the Clinical tests listed in Attachment K - Laboratory Tests & Equipment |
| B13 | Perform Specimen Analysis | Test and Assay Management | The solution should deliver a fully completed LIMS testing module for the Environmental tests listed in Attachment K - Laboratory Tests & Equipment |
| B14 | Perform Specimen Analysis | Test and Assay Management | The solution should have the option to add clinical testing assays |
| B15 | Perform Specimen Analysis | Test and Assay Management | The solution should have the option to add environmental testing assays |
| B16 | Perform Specimen Analysis | Test and Assay Management | The solution should define and manage: |
a. test protocols
b. test catalogs
c. test codes B17 Perform Specimen Analysis Test and Assay Management The solution should allow for customizable:
a. test profiles
b. test panels
c. test workflows
| B18 | Perform Specimen Analysis | Test and Assay Management | The solution should perform test planning |
| B19 | Perform Specimen Analysis | Test and Assay Management | The solution should support batch management capabilities including, but not limited to: |
a. grouping of samples
b. tests
c. results into batches for streamlined processing, review, and reporting B20 Perform Specimen Analysis Test and Assay Management The solution should provide comprehensive test management capabilities, including, but not limited to:
a. test definition
b. test scheduling
c. test result entry B21 Perform Specimen Analysis Test and Assay Management The solution should support sample preparation and aliquot management, including, but not limited to:
a. tracking of sample aliquots
b. dilutions
c. derivatizations
d. managing sample preparation protocols, calculations, and results B22 Perform Specimen Analysis Test and Assay Management The solution should support environmental monitoring capabilities, including, but not limited to:
a. monitoring environmental samples, such as air, water, and surface samples
b. managing related data, results, and reports
| B23 | Perform Specimen Analysis | Results Management | The solution should be able to receive, validate, store and manage laboratory test results |
| B24 | Perform Specimen Analysis | Results Management | The solution should be able to generate and transmit result reports electronically to authorized personnel |
| B25 | Perform Specimen Analysis | Results Management | The solution should allow for separate review and approval of results, not allowing for the same resource to review, approve, and release their own work |
| B26 | Perform Specimen Analysis | Results Management | The solution should be able to identify/alert on abnormal or critical results |
| B27 | Perform Specimen Analysis | Results Management | The solution should allow user to only review abnormal results instead of reviewing all results that are normal |
| B28 | Perform Specimen Analysis | Results Management | The solution should allow efficient result entry, review, and approval |
| B29 | Perform Specimen Analysis | Results Management | The solution should support result calculation, result validation, and result reporting |
| B30 | Perform Specimen Analysis | Results Management | The solution should also provide results trending, statistical analysis, and data visualization capabilities |
| B31 | Perform Specimen Analysis | Results Management | The solution should enable the users to enter results manually by batch or individually |
| B32 | Perform Specimen Analysis | Results Management | The solution should enable users to enter results electronically by batch or individually |
| B33 | Perform Specimen Analysis | Results Management | The solution should allow users to specify whether test results will be manually entered or resulted by an instrument |
| B34 | Perform Specimen Analysis | Results Management | The solution should support electronic messaging/notifications to designated users for samples flagged for incomplete data |
| B35 | Perform Specimen Analysis | Results Management | The solution should support electronic messaging/notifications to designated users for samples flagged as unsatisfactory |
| B36 | Perform Specimen Analysis | Results Management | The solution should allow authorized users to configure batch Quality Control (QC) requirements for each test method including, but not limited to: |
a. each type
b. frequency
c. run placement
d. acceptance criteria
| B37 | Perform Specimen Analysis | Results Management | The solution should be able to display both raw data and interpretations of sample results |
| B38 | Perform Specimen Analysis | Results Management | The solution should track technicians performing each step of sample testing |
| B39 | Perform Specimen Analysis | Results Management | The solution should allow batch approval of testing results with a “select all” option |
| B40 | Perform Specimen Analysis | Results Management | The solution should allow approval of QC results for reagents |
| B41 | Perform Specimen Analysis | Results Management | The solution should be able to create and print batch worksheets and allow users to modify the worksheet, add tests, and reprint the worksheet until the batch results are entered |
| B42 | Perform Specimen Analysis | Results Management | The solution should be able to populate the worksheet with information including, but not limited to: |
a. analyst name
b. date
c. time
d. method code
e. sample number
f. final volume, dilutions, reagents, and QC samples
| B43 | Perform Specimen Analysis | Results Management | The solution should prevent the release of results for final reporting until they are verified by laboratory staff with appropriate user access |
| B44 | Perform Specimen Analysis | Results Management | The solution should flag any “out of control” runs through use of quality control data and prevent release of results that do have not valid control results |
| B45 | Perform Specimen Analysis | Results Management | The solution should notify laboratory users and submitters if the sample is out of compliance based on assigned, configurable time values |
| B46 | Perform Specimen Analysis | Results Management | The solution should calculate appropriate sample hold times using configurable sample criteria including, but not limited to: |
a. sample collection date-time
b. receive date-time
c. test method
d. temperature
| B47 | Perform Specimen Analysis | Results Management | The solution should allow for separate review and approval of results, not allowing for the same resource to review, approve, and release their own work |
| B48 | Perform Specimen Analysis | Results Management | The solution should allow for the utilization of "canned" pre-created comments in all areas and free text comments in only approved areas for reporting |
| B49 | Manage Inventory and Logistics | Inventory Management | The solution should support reagent and inventory management, including, but not limited to: |
a. tracking of reagents
b. consumables
c. other laboratory supplies
d. managing reagent expiration dates
e. stock levels
f. reordering
g. manual adjustments of inventory amounts B50 Manage Inventory and Logistics Inventory Management The solution should support inventory tracking through features including, but not limited to:
a. inventory levels
b. reordering
c. stock management
| B51 | Manage Inventory and Logistics | Inventory Management | The solution should support product and lot genealogy |
| B52 | Manage Inventory and Logistics | Inventory Management | The solution should perform test planning |
| B53 | Manage Inventory and Logistics | Inventory Management | The solution should consolidate product sample data and documentation |
| B54 | Manage Inventory and Logistics | Inventory Management | The user should be able to filter and review abnormal and normal results |
| B55 | Manage Inventory and Logistics | Inventory Management | The solution should have inventory management functions that will provide alerts when items/products are scheduled to expire. Alerts should show on screen as well as have the ability to be sent to an illinois.gov email address if necessary |
| B56 | Manage Inventory and Logistics | Inventory Management | The solution should have configurable inventory management par levels and provide alerts when a par level is reached |
| B57 | Manage Inventory and Logistics | Inventory Management | The solution should have inventory management functions that will provide alerts when instruments require scheduled service. Alerts should show on screen as well as have the ability to be sent to an illinois.gov email address if necessary |
| B58 | Manage Inventory and Logistics | Inventory Management | The solution should have inventory management functions that prevents the use of expired reagents |
| B59 | Manage Inventory and Logistics | Inventory Management | The solution should maintain an inventory of laboratory supplies used in the lab, including, but not limited to: |
a. chemicals
b. reagent test kits
c. gloves
d. lab coats
| B60 | Manage Inventory and Logistics | Inventory Management | The solution should track the inventory of laboratory supplies using barcode technology |
| B61 | Manage Inventory and Logistics | Inventory Management | The solution should have the ability to support hyperlinks and QR codes to items, including, but not limited to: |
a. SDS sheets
b. package inserts for exposure and safety information B62 Manage Inventory and Logistics Inventory Management The solution should track the inventory of laboratory supply products with fields including, but not limited to:
a. receive date
b. product name
c. lot number
d. expiration date
e. quantity
f. location of storage
g. procurement vendor name B63 Manage Inventory and Logistics Sample Tracking The solution should provide robust sample tracking features, including, but not limited to:
a. sample receipt
b. storage
c. transfer
d. disposal B64 Manage Inventory and Logistics Sample Tracking The solution should support chain of custody documentation to ensure sample integrity and traceability, including, but not limited to:
a. electronic signatures
b. audit trails
| B65 | Manage Inventory and Logistics | Sample Tracking | The solution should assign and maintain a unique specimen/sample identification number throughout the life-cycle of the specimen |
| B66 | Manage Inventory and Logistics | Sample Tracking | The solution should provide positive web-based sample tracking from receipt through the reporting of results using the sample bar code or the accession number |
| B67 | Manage Inventory and Logistics | Sample Tracking | The solution should link bar codes to the accession number at the time of accessioning |
| B68 | Manage Inventory and Logistics | Sample Tracking | The solution should use 2d barcode technology from any workstation with a barcode reader attached using standards such as Code 39 and Code 128 |
| B69 | Manage Inventory and Logistics | Sample Tracking | The solution should have the ability to send ledgers within IDPH in either hard copy or electronic format |
| B70 | Manage Inventory and Logistics | Sample Tracking | The solution should have the ability to create ledger containing data elements including, but not limited to: |
a. Invoice Number
b. Billing Date
c. Provider ID
d. Provider Name
e. Provider Address
f. Number of Specimens
g. Bill Amount
h. Validation Stamp Area
i. Current Date
j. CPT Codes
k. ICD10 codes
l. Cost/Price B71 Report and Delivery Data Report and Delivery Data The solution should provide robust reporting and analytic capabilities including, but not limited to:
a. generating standard reports
b. generating ad hoc reports
c. tracking key performance indicators (KPIs)
d. providing insight into laboratory operations
e. providing insight into laboratory performance
| B72 | Report and Delivery Data | Report and Delivery Data | The solution should allow health care providers and sample submitters to print labels with patient/source information that can be attached to the specimen/source for transmission to the lab |
| B73 | Report and Delivery Data | Report and Delivery Data | The solution should allow the end-user to print reports, forms, documents and labels to the user’s default printer |
| B74 | Report and Delivery Data | Report and Delivery Data | The solution should integrate with OpenText Fax Solutions for report faxing capability |
| B75 | Report and Delivery Data | Report and Delivery Data | The solution ad hoc reporting tool should have query parameters including, but not limited to: |
a. Follow data accessibility permissions
b. Be configurable as read only or read‐write access based on permissions
c. Be flexible and ad hoc configurable
e. Incorporate search engine capabilities for free text fields
f. Utilize logical expressions (>, <, =, contains, and, or)
g. Be exportable in .XLSX and .CSV table formats
h. Capable of selecting samples to for report generation
| B76 | Report and Delivery Data | Report and Delivery Data | The solution should use fully configurable reports to create the laboratory results to be sent to the submitters |
| B77 | Report and Delivery Data | Report and Delivery Data | The solution should automatically report numeric results based on the number of significant figures and decimal places specified by the user |
| B78 | Report and Delivery Data | Report and Delivery Data | The solution should automatically report results below the numerical data value method detection limit specific by the user |
| B79 | Report and Delivery Data | Report and Delivery Data | The solution should provide the ability to the authorized user to enter text values into the results fields |
| B80 | Report and Delivery Data | Report and Delivery Data | The solution should be able to create user-defined extracts of test data for electronic transmittal to specific users utilizing a standard file format including, but not limited to: |
a. comma-delimited flat files B81 Report and Delivery Data Report and Delivery Data The solution should allow ad hoc queries based on fields including, but not limited to:
a. submitter ID numbers
b. funding code
c. lab section
d. test type
e. result
f. sample type
g. sample source B82 Report and Delivery Data Report and Delivery Data The solution should be able to generate ad hoc reports including, but not limited to:
a. total tests
b. positivity rates
c. positive test patterns by type of test
d. turn-around-time statistics
| B83 | Report and Delivery Data | Report and Delivery Data | The solution should provide authorized users documentation specifying how data will be transferred to an “archive” location |
| B84 | Report and Delivery Data | Report and Delivery Data | The solution should provide the ability for the end user to view "archived" data without restoring the data to the “active” location |
| B85 | Report and Delivery Data | Report and Delivery Data | The solution should be able to select tests for diversion to CDC or a referral laboratory and create a file of diverted tests. The system should have the capability to create packing lists and other documentation for diverted tests |
| B86 | Report and Delivery Data | Report and Delivery Data | The solution should be able to create packing lists for diverted tests |
| B87 | Report and Delivery Data | Report and Delivery Data | The solution should include workflow dashboards and statistical data reports |
| B88 | Report and Delivery Data | Report and Delivery Data | The solution should provide the ability for authorized users to generate standard and ad hoc reports that monitor key performance indicators (KPIs) and track laboratory performance including, but not limited to: |
a. number of incomplete samples
b. number of complete samples
c. completed but unprocessed samples
d. average processing time
e. aid in planning resources
| B89 | Report and Delivery Data | Report and Delivery Data | The solution should allow for data export and data import in standard formats including, but not limited to: HL7 and DICOM |
| B90 | Report and Delivery Data | Report and Delivery Data | The solution should offer expanded query capabilities |
| B91 | Report and Delivery Data | Report and Delivery Data | The Solution should provide the ability to send finalized reports via email (or an attachment on the portal) |
| B92 | Report and Delivery Data | Report and Delivery Data | The Solution should have the capability to push messages to the intended workers without requiring them to specifically inquire for the data, aligned with business process. This includes, but is not limited to: |
1) notifying the staff of pending testing requests that have not been reported
2) alerting staff of samples beyond turn around time
3) alerting staff to samples with pending demographic data needed to meet acceptability requirements
4) providing end of day logs that shows samples pending results
| B93 | Report and Delivery Data | Report and Delivery Data | The solution should be able to make corrected/amended reports while retaining all previous report versions that are associated with that sample |
| B94 | Integrate Devices | Integrate Devices | The solution should have the ability to configure workflows for a wide range of laboratory processes |
| B95 | Integrate Devices | Integrate Devices | The solution should interface with automated sample handling systems |
| B96 | Integrate Devices | Integrate Devices | The solution should integrate with optical character recognition systems (currently Optiform), analytical instruments, and system-to-system communications via web services, file transfer (text, CSV, HL7, ASCII, etc.) and ODBC database communications |
| B97 | Integrate Devices | Integrate Devices | The solution should integrate with the IDPH USA Food Safety application used by the Division of Food Drugs and Dairies. System integration should include, but not limited to: |
a. transmission of food sample collection data to the LIMS electronically
b. full integration with the food safety application
c. ability to electronically send test results and raw test data to the food safety application and update the field record
| B98 | Integrate Devices | Integrate Devices | The solution should receive test orders, including basic demographics, using an application program interface (API) or other method such that scannable submission forms may be utilized to avoid hand entry of data directly into the LIMS |
| B99 | Integrate Devices | Integrate Devices | The solution should have the ability for electronic order entry for test requisitions and/or requests |
| B100 | Integrate Devices | Integrate Devices | The solution should create bi‐directional test ordering and results reporting with external stakeholder LIMS systems |
| B101 | Integrate Devices | Integrate Devices | The solution should supply a web‐based portal for data exchange and allow for on-line entry, by internal or external stakeholders, of information to facilitate reaccessioning of specimens |
| B102 | Integrate Devices | Integrate Devices | The solution should automatically capture data and electronically interface with laboratory instrumentation including, but not limited to: |
a. analyzers
b. all equipment listed in Attachment K - Laboratory Tests & Equipment
| B103 | Integrate Devices | Integrate Devices | The solution should automatically upload laboratory result and quality control (QC) data from laboratory instruments to LIMS replacing manual entry, user created excel macros, and paper records |
| B104 | Integrate Devices | Integrate Devices | The solution should provide data intelligence analysis functionality with both metric and standard measurements |
| B105 | Integrate Devices | Integrate Devices | The solution should offer data trending and tracking of specific metrics with statistical analysis of routine data collection and control charts |
| B106 | Integrate Devices | Integrate Devices | The solution should maintain a record of equipment locations and equipment information, including, but not limited to: |
a. manufacturer
b. model number
c. serial number
d. year of purchase
e. state property ID number
f. any required instrument service dates
| B107 | Integrate Devices | Integrate Devices | The solution should be flexible and able to accommodate changes in required testing and instrumentation |
| B108 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should manage and maintain a table of clients/providers that contains contact information including, but not limited to: |
a. Name
b. Mailing address
c. National Provider Identification (NPI) or Submitter's code number
d. Contact name
e. Telephone numbers
| B109 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should have configurable screen layouts to align with the submissions, with the ability to add functions to the program menu and all other screens allowing the database administrator to keep the LIMS current with user needs |
| B110 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should be able to verify the accuracy of demographic zip code/city combination with correct information available from the US Post Office |
| B111 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should enable initial import of city/zip codes and periodic maintenance of this table by administration based on user role/access |
| B112 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should show the success of data imported into the system, particularly with provider tables and electronic importation of demographic data for test orders |
| B113 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should provide secure data import and place barriers for specific data types |
| B114 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should provide audit and compliance reporting capabilities, allowing for tracking and reporting of all system activities including, but not limited to: |
a. user actions
b. data changes
c. system events for compliance with regulatory requirements
| B115 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should have the ability to support X12 codes, or current standard, and HIPAA-compliant electronic transactions for billing purposes |
| B116 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should support user authentication, user authorization, and user role management |
| B117 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should provide the ability to manage user accounts, password policies, and user privileges |
| B118 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should support electronic signatures and audit trails for compliance with regulatory requirements |
| B119 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should allow authorized users to add and configure new tests in a timely manner (<6 months) |
| B120 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should support compliance with including, but not limited to FDA 21 CFR Part 11, ISO 17025, ISO 9000 Consumer Product Safety Act (CPSA), and other regulatory requirements and best practices |
| B121 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should meet compliance standards (CLIA, NCCLS, ISO 17025, etc.) |
| B122 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should allow system administrators to set permissions to make sure that only qualified staff can authorize key processes |
| B123 | Manage Lab Services Delivery and Administration | Manage Lab Services Delivery and Administration | The solution should allow system administrators to set permissions to make sure that only qualified staff can view and amend critical data |
| B124 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should support laboratory workflow and task management processes including, but not limited to: |
a. sample routing
b. approval workflows
c. user-defined workflows
| B125 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should support performing resource planning |
| B126 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should support assigning and tracking tasks |
| B127 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should support managing work queues |
| B128 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should prioritize work based on criteria including, but not limited to urgency and priority |
| B129 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should have the ability for users to set up automated alerts and notifications for specific events including, but not limited to: |
a. out-of-spec results
b. overdue tasks or pending approvals to ensure timely actions and compliance with laboratory processes
| B130 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should allow for easy configuration and customization of workflows to accommodate the laboratory's specific needs |
| B131 | Manage Lab Services Delivery and Administration | Workflow and Task Management | The solution should comply with relevant regulatory requirements including, but not limited to: FDA, ISO, and CLIA regulations, and provide appropriate documentation and audit trails to support regulatory audits and inspections |
| B132 | Manage Lab Services Delivery and Administration | Quality Control | The solution should support quality control processes including, but not limited to: |
a. quality control sample management
b. control charting
c. alert notifications for out-of-spec results B133 Manage Lab Services Delivery and Administration Quality Control The solution should have quality control features including, but not limited to:
a. setting up and managing quality control samples
b. generating quality control charts
c. tracking and managing quality control data for ongoing performance monitoring and assessment
| B134 | Manage Lab Services Delivery and Administration | Quality Control | The solution should undergo validation processes, including but not limited to, IQ/OQ/PQ (Installation Qualification, Operational Qualification, Performance Qualification), and provide appropriate documentation to support compliance with regulatory requirements |
| B135 | Manage Lab Services Delivery and Administration | Quality Control | The solution should be able to simplify the quality control process by ensuring that SOPs and business rules are being followed |
| B136 | Manage Lab Services Delivery and Administration | Quality Control | The solution should allow for Quality Control to be saved with run information for future troubleshooting or QA improvement |
| B137 | NBS - Conduct Dried Blood Spot Testing | Patient Management | The solution should capture all relevant newborn patient demographics including, but not limited to: |
a. name
b. date of birth (DOB)
c. gender
d. contact information
e. other relevant demographics as determined by DoIT
f. mother's name Optional -
a. ethnicity
b. race B138 NBS - Conduct Dried Blood Spot Testing Test Ordering The solution should allow authorized health care providers to place orders for newborn screening tests based on established screening protocols including, but not limited to:
a. blood tests
b. metabolic tests
c. performing molecular (DNA-based) screening
| B139 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should be able to deliver a Laboratory Newborn Screening testing module for the Newborn Screening Tests listed in Attachment K - Laboratory Tests & Equipment |
| B140 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should be able to order and result tests for disorders and diseases, including, but not limited to: |
a. amino and urea cycle disorders
b. biotinidase deficiency
c. congenital adrenal hyperplasia
d. congenital hypothyroidism
e. cystic fibrosis
f. fatty acid oxidation disorders
g. galactosemia
h. lysosomal storage disorders
i. organic acid disorders
j. phenylketonuria
k. severe combined immune deficiency
l. sickle cell disease
| B141 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should support quality assurance testing methodology |
| B142 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should allow follow up testing that screen for the presence of certain lysosomal storage disorders known as Krabbe, Pompe, Gaucher, Fabry, and Niemann-Pick after six months for all newborns meeting defined criteria in Illinois statute: 410 ILCS 240/3.1 |
| B143 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should allow follow up testing that screen for the presence of severe combined immunodeficiency disease (SCID) after 12 months for all newborns meeting defined criteria in Illinois statute: 410 ILCS 240/3.2 |
| B144 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should allow follow up testing that screen for the presence of certain lysosomal storage disorders known as mucopolysaccharidosis I (Hurlers) and mucopolysaccharidosis II (Hunters) after 12 months for all newborns meeting defined criteria in Illinois statute: 410 ILCS 240/3.3 |
| B145 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should allow follow up testing that screen for the presence of adrenoleukodystrophy (ALD) after 18 months for all newborns meeting defined criteria in Illinois statute: 410 ILCS 240/3.4 |
| B146 | NBS - Conduct Dried Blood Spot Testing | Test Ordering | The solution should allow follow up testing that screen for spinal muscular atrophy using a method that determines the presence or absence of the intact or normal SMN1 gene for all newborns meeting defined criteria in Illinois statute: 410 ILCS 240/3.5 |
| B147 | NBS - Conduct Dried Blood Spot Testing | Sample Collection Tracking | The solution should provide functionality to track the collection of samples from newborns, including, but not limited to: |
a. sample collection date
b. sample type
c. sample collection location
| B148 | NBS - Conduct Dried Blood Spot Testing | Sample Collection Tracking | The solution should generate unique identifiers for each sample and the unique identifiers need to remain with the sample throughout the lifecycle of testing to ensure accurate tracking and traceability |
| B149 | NBS - Conduct Dried Blood Spot Testing | Sample Testing and Reporting | The solution should facilitate testing of newborn samples within 24 hours of birth |
| B150 | NBS - Conduct Dried Blood Spot Testing | Sample Testing and Reporting | The solution should provide automated test result reporting to authorized health care providers |
| B151 | NBS - Conduct Dried Blood Spot Testing | Sample Testing and Reporting | The solution should store results securely for future reference and analysis |
| B152 | NBS - Conduct Dried Blood Spot Testing | Sample Testing and Reporting | The solution should temporarily provide screening through an accredited laboratory selected by the Department if the Department doesn't have the capacity to provide screening through the State Laboratory |
| B153 | NBS - Conduct Dried Blood Spot Testing | Results Management | The solution should allow health care providers to manage newborn screening results |
| B154 | NBS - Conduct Dried Blood Spot Testing | Results Management | The solution should allow external health care providers to review test results within the NBS system |
| B155 | NBS - Conduct Dried Blood Spot Testing | Results Management | The solution should identify "abnormal" results based on established thresholds |
| B156 | NBS - Conduct Dried Blood Spot Testing | Results Management | The solution should have a test pending result in cases where the samples are sent out (i.e., Krabbe samples for sequencing). |
| B157 | NBS - Conduct Dried Blood Spot Testing | Results Management | The solution should allow health care providers to generate ad hoc reports for further analysis and follow up |
| B158 | NBS - Conduct Dried Blood Spot Testing | Decision Support | The solution should allow the establishment of precise threshold values ensuring defined identification of abnormal results for each screening test |
| B159 | NBS - Conduct Dried Blood Spot Testing | Decision Support | The solution should provide decision support functionality to help health care providers interpret newborn screening results and identify infants who require further evaluation or intervention based on established guidelines |
5. Desirable Technical Fn.
| ID# | Level 0 Capability | Level 1 Capability | Desirable Technical Functionality | Desirable Technical Functionality Met | Solution Method | Explanation or Comments | Back to tab 3. Instructions |
| T1 | General System Behavior | Usability | The Solution should provide a user interface that should be simple, consistent, and aligned with business process throughout all areas and functions of the System. | ||||
| T2 | General System Behavior | Usability | The Solution should minimize the number of mouse clicks/user interactions to complete any task, aligned with business process. | ||||
| T3 | General System Behavior | Usability | The Solution should use a Graphical User Interface (GUI) to help the user navigate to the next logical step in the workflow, or freely navigate to other parts of the System functionality, and then allow the user to return to complete the in-process task aligned with business process. | ||||
| T4 | General System Behavior | Usability | The Solution should speak the users' language, with words, phrases and concepts familiar to the user, rather than System-oriented terms consistent with business process. | ||||
| T5 | General System Behavior | Usability | The Solution should accommodate diverse populations of users including those with disabilities and limited English proficiency as defined in section 504 of the Rehabilitation Act of 1973, and as defined by the Illinois Information Technology Accessibility Act (P.A. 95-307, eff. 8-20-07). | ||||
| T6 | General System Behavior | Usability | The Solution should follow real-world Illinois IDPH terminology and conventions, making information appear in a natural and logical order. | ||||
| T7 | General System Behavior | Usability | The Solution should allow the users to easily navigate to a variety of functions available to them without having to move sequentially through excessive menus and screens, aligned with business process. | ||||
| T8 | General System Behavior | Usability | The Solution should include, at minimum, the following improved features and capabilities vis-a-vis existing systems: |
A. Drill down and look up functionality to minimize time required for access to more detailed information B. Multi-tasking and multiple window capability, including split screens C. Search capabilities to allow retrieval by name, DOB, specimen number or other parameters as defined by DoIT D. Ability to tab and mouse through data fields and screens.
| T9 | General System Behavior | Usability | The Solution should support undo and redo, or provide onscreen confirmation/acceptance to the user to confirm a change that is permanent and cannot be "undone". |
| T10 | General System Behavior | Usability | The Solution should provide users with a clearly marked "emergency exit" for the instances when a user mistakenly chooses a function and such "emergency exit" should be simple with minimal dialogue, and leave all data unchanged. |
| T11 | General System Behavior | Usability | The Solution should follow standardized conventions and limit the use of words, situations, or actions that have multiple meanings. |
| T12 | General System Behavior | Usability | The Solution should eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action, while ensuring the integrity of data. |
| T13 | General System Behavior | Usability | The Solution should minimize the need for users to memorize by making options visible. |
| T14 | General System Behavior | Usability | The Solution should provide the option to have rollover/tooltip help or context messages and provide the option to turn off this option in the user preferences profile. |
| T15 | General System Behavior | Usability | The Solution should provide all user instructions in a visible or easily retrievable location, when appropriate. |
| T16 | General System Behavior | Usability | The Solution should cater to both inexperienced and experienced users and should provide accelerators (e.g., onscreen short cuts, hot-keys, alternate workflows, etc.) to speed up the interaction for the expert user, aligned with business process. |
| T17 | General System Behavior | Usability | The Solution should allow users to create shortcuts (e.g., onscreen short cuts, hot-keys, etc.) for frequent actions, aligned with business process. |
| T18 | General System Behavior | Usability | The Solution should express its error messages in plain language, precisely indicate the problem, and constructively suggest a solution, aligned with business process. |
| T19 | General System Behavior | Usability | The Solution should use colors to enhance user experience and System usability while complying with all disability requirements notated elsewhere in these requirements, aligned with business process. |
| T20 | General System Behavior | Usability | The Solution should allow the user to navigate to any functional component from a client landing page, aligned with business process. |
| T21 | General System Behavior | Usability | The Solution should alert the user with information relevant to required next steps, aligned with business process. |
| T22 | General System Behavior | Usability | The Solution should provide drop downs, list boxes and multi-selection for all key entry, and text entry should display existing values for selection (system based auto fill) (but specifically disallow client browser based auto fill). |
| T23 | General System Behavior | Usability | The Solution should accommodate point and click selection and check box entry for all relevant data entries to ensure that the user does not have to enter textual data that may already be available to the System, aligned with business process. |
| T24 | General System Behavior | Usability | The Solution should facilitate data entry and should contain pop-up list boxes for all code fields in all processing windows and allow selection of the entry with use of hot keys, aligned with business process. |
| T25 | General System Behavior | Usability | The Solution should provide field level on-screen edits with limited user override capabilities, aligned with business process. |
| T26 | General System Behavior | Usability | The Solution should provide the ability to make fields visible/invisible depending on parameters, user rights, consent, and access controls, aligned with business process. |
| T27 | General System Behavior | Usability | The Solution should hide fields not accessible to a given user based on access rights, member consent, and fields not in use, aligned with business process. |
| T28 | General System Behavior | Usability | The Solution should have a cursor that should automatically advance to the next logical input field when the maximum allowed numbers of characters have been entered for the keyed field (where applicable) or when the user presses the "Enter" key, aligned with business process. |
| T29 | General System Behavior | Usability | The Solution should provide the option of having a selection from the drop down boxes automatically and take the user to the next input field, aligned with business process. |
| T30 | General System Behavior | Usability | The Solution should provide validation checks at the time of each field entry as the default mechanism, aligned with business process. |
| T31 | General System Behavior | Usability | The Solution should identify invalid entries to the user as immediately as possible, aligned with business process. |
| T32 | General System Behavior | Usability | The Solution should provide the ability to suggest or automatically change entries that do not conform to data entry standards, to be defined in the detailed System design and meta data models in collaboration with DoIT, aligned with business process. |
| T33 | General System Behavior | Usability | The Solution should be designed to include only the necessary information and functionality on screens and should be based on the user's access level and the user's configuration, aligned with business process. |
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 .