RFI LIMS Draft 13 Feb 2020.pdf

Enterprise Laboratory Information Management System (LIMS)

This Request for Information (RFI) is for planning purposes only and is not a Request for Proposal (RFP), Invitation for Bid (IFB) or an obligation on the part of the Government to acquire any services. Responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. The Government reserves the right to determine how it should proceed as a result of this notice. Furthermore, those who respond to this RFI should not anticipate feedback with regard to its submission. The Government will not pay any cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the responding party's expense. The information provided in this RFI is subject to change and is not binding on the Government. Any information provided by industry to the Government as a result of this RFI is strictly voluntary. Responses will not be returned. The information obtained from industries' responses to this notice may be used in the development of an acquisition strategy and a future RFP (if applicable).

1. BACKGROUND

The DLA Enterprise seeks a Laboratory Information Management System (LIMS) that allows our lab personnel to effectively manage samples and data associated with sampling, testing and equipment calibrations. Our labs should be able to automate workflows, integrate instruments within tablets and PCs, and manage samples and associated information. Additionally, this will allow the labs to produce reliable results more quickly and while tracking data from sequencing runs over time and across experiments to improve efficiency.

2. PURPOSE

Today DLA Enterprise labs operating using differing instances of Microsoft Access Databases, Enterprise Business Solution (EBS) Quality Management, EBS Supplier Resource Management and local shared drives.

The goal is to convert historical data from these legacy systems to an enterprise standard Laboratory Information Management System

DLA wants to leverage technology to receive, manage, store and share Laboratory information data to support business processes. DLA is looking to understand from industry the art of the possible in creating a LIMS which has Core Lab Management, Workflow Functionality, Reporting, Equipment Calibration & Table Sync, Standards and Specifications, and Business Module Capability.

3. SCOPE

DLA is seeking to implement an end-to-end solution for laboratory Information Management that will leverage the latest technology advancements to automate for process efficiencies. DLA wants to understand the latest technologies to work alongside our SAP Quality Module Enterprise Solution. SAP Quality Management (QM) is a component of SAP ERP Central Component (ECC) that helps businesses implement and run quality control processes. It is designed to prevent defects, enable continuous process improvement, and establish sustained quality control programs. Potential benefits for the organization include compliance with manufacturing quality regulations, lower operating costs, and improving customer satisfaction. We have nine Core laboratory Information Management Processes are seeking information for.

1. Document management

2. Personal management

3. Supply management

4. Financial management

5. Training management / Certified Operators

6. Test plan management

7. Test code management

8. Job order/location management

9. Unit of Measure management - conversion tables

4. REQUIREMENTS

The new laboratory Information Management can be a web-based or a Graphic user interface (GUI) application and must support the requirements in this section. This is a combination of currently implemented requirements and future capability needs.

The future laboratory Information Management must perform the following:

Workflow Functionality

2) Provide workflow functionality with process and task management. Provide ability to systemically assign, receive, track, process, and monitor workload. Ability to efficiently track testing addition, deletes, status of approvals, and record retention requirements via workflow. Track and publish status of program participants and associated testing approvals. Track modifications, suspensions, and revocations. See the following:

a. Audit trail

b. Barcoding

c. Chain of custody

d. Data entry and validation

g. Sample management & tracking

i. Electronic data exchange

k. Review/approval process

j. Test traveler creation – for audit purposes

k. Ability to capture images and screen shots via external device (Tablet PC)

Reporting

3) Provide reporting capabilities associated with data mining, metrics, and workload reporting.

Maintain historic archive data with the ability to store, search, modify, and delete records.

Capability to store, edit, delete, and retrieve documents from document storage. Integrate and establish equivalent functionality and data storage currently utilized within the current databases. Legacy/Historic system data currently utilized to be provided to aid with establishing SAP data records and creating historic data records within SAP. See the following:

a. Ability to receive external test reports with images

b. Data warehousing and mining

c. Reports should have the ability to display photo images and charting

d. Data to feed into Enterprise Data Warehouse (EDW), SAP HANA

e. Metrics module – Performance metrics / cycle times / individual performance

f. Automated test report generation

g. Shelf life program report

h. CoA generation with digital signature of lab representative

i. Ability to perform ad-hoc queries of data and export into csv and excel formats

Equipment Calibration & Table Sync

4) Provide a method of evaluating and tracking the precision and accuracy of measurement equipment.

Instrument calibration will eliminate or reduce bias in an instrument's readings over a range for all continuous values. The LIMs should also be integrate lab Equipment, PCs (thick/thin) and Tablet PCs. See the following:

a. Integration of electronic notebooks via Tablet PC and interface with LIMS)

b. Interface equipment within house test methods (calibration methods)

c. Tablet Interface with local test equipment via Equipment ports

d. Instrument calibration & maintenance reporting and scheduling

e. Develop extended utilization of thick/thin client laptops

Standards and Specifications

5) Provide the ability to access Standards and Specifications various specialties and DLA contractual information in EBS. See the following:

a. Ability to view American Association of Textile Chemists and Colorists (AATCC), American Society for Testing and Materials (ASTM), National Fire Protection Association (NFPA), International Organization for Standardization (ISO) Test Methods

b. Proficiency testing

c. Ability to open quality contractual data in Enterprise Central Component (ECC) via the LIMS

d. DNA module

e. PROM/ROM module

Business Module Capability

6) The DLA Enterprise LIMS solution should have the ability to have unique modules based on the business of the laboratory. DLA manages a variety of commodities. While the core Lab requirements will be the same for all labs, certain labs may require differing test plans, sets, and series. The DLA labs may also require differing equipment calibration methods, Standards and Specifications. DLA has the following lab types:

a. DLA Energy Labs (Petroleum and Gases)

b. DLA Land and Maritime (Electronics and Mechanical Labs)

c. DLA Troop Support (Clothing, Textiles, Analytical and Mechanical Labs)

The new system should be fully compliant with FIPS 200 and NIST 800-53. These are the key areas of focus under the NIST 800-53:

a. AC Access Control

b. AU Audit and Accountability

Requirements for the future solution are categorized below. Some of the requirements have multiple functionality and will appear in more than one category.

Hosting

1) High Availability – 95% Uptime to include Software Upgrade Outages

2) Disaster recovery – Restore service within a week without a custom solution

3) Operation System Agnostic

4) Cloud Capable – Federal Risk and Authorization Management Program (FEDRAMP) Certified

Technical Requirements

1) 508 Compliant

2) Defense Information Systems Agency (DISA) Security Technical Information Guide (STIG) a

Compliant OR compliant with NIST 800-53

3) National Information Assurance Partnership (NIAP) Certified

4) Joint Interoperability Test Command (JITC) Compliant

5) Scalability – ability to add roughly 20 new users per yearly efficiently

Key Performance Indicators

1. Meet or exceed the following Key Performance Indicators

a. User Interface refresh is < 3 seconds

b. File(s) size < 100mB

c. Screen to screen < 8 seconds

d. Search returns < 10 seconds

e. Import < 5 minutes

f. Screen Data < 5 minutes

g. Send to Routing (system to system) < 10 seconds

h. Save < 10 seconds

i. Back < 10 seconds

j. Export < 30 seconds

k. Upload attachments < 10 seconds

2. Mass load/Query/Transaction processing are completed:

a. <300 =/< 1 minute

b. 301 – 1000 =/< 3 minutes

c. 1001 – 5000 =/< 1 hour

d. 5001 =/< 24 hours

5. SUBMISSION REQUIREMENTS

RFI Response Assessment

This Request for Information (RFI) is for planning purposes only and is not an obligation on the part of the Government to acquire any services. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. The Government reserves the right to determine how it should proceed as a result of this notice. Furthermore, those who respond to this RFI should not anticipate feedback with regard to its submission. The Government will not pay any cost incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the responding party's expense. The information provided in this RFI is subject to change and is not binding on the Government.

Any information provided by industry to the Government as a result of this RFI is strictly voluntary and optional. Please provide as much information as feasible. Responses will not be returned. The information obtained from industries' responses to this notice may be used in the development of an acquisition strategy and a future RFP (if applicable).

To assist the contracting office in making a determination regarding the level of participation by small business in any subsequent procurement that may result from this RFI, you are encouraged to provide information regarding your plans to use joint venturing (JV), partnering or consortiums to meet each of the requirements areas contained herein. You should provide information on how you would envision your company's areas of expertise and those of any proposed JV/partnering/consortium would be combined to meet the specific requirements contained in this RFI

Response Instructions

RFI responses should be font no smaller than 12pt, single-spaced. Responses shall not exceed 250 words per question. Provide any additional information you deem pertinent; with a 10 page total limit. RFI responses must provide the following information.

Email your company capabilities in response to this RFI to Nicholas.Becht@dla.mil

RFI response must be submitted no later than March 16, 2020, 4pm EST.

Primary Point of Contact

Nicholas Becht Email Nicholas.Becht@dla.mil Phone: (215) 737-2594

Contracting Office Address

DLA Contracting Support Office (DCSO-P) 700 Robbins Avenue Philadelphia,PA19111 United States

• Section 1 - Cover Letter. The cover letter must include the following information:

• Company name

• Company business size with socioeconomic classification based on North American Industry Classification Code.

• Company point of contact and contact information (name, address, phone number, email address, and fax number)

• Date submitted.

If more than one solution is proposed from a team of providers, all company information should be presented (name, size, etc.).

• Section 2 - Market Research Questions. The purpose of this section is to obtain information that will assist in making a decision on whether any solutions are available in the market to satisfy the requirements and objectives; and determining a ROM pricing estimate. The RFI defines solution as the software that is an application package. If the full solution requires multiple market solutions, each vendor solution should be described.

Functional Solution

1. Describe an end-to-end solution that would support outlined requirements. Provide a high-level architecture to include software to support requirements. Map requirements to proposed software solution and identify any requirements gaps. Provide reference for your three largest commercial clients utilizing similar software solutions.

2. Do you have business case/return on investment/white papers regarding benefits and costs of implementing your product? If so, provide a reference summary within your response and provide the investment/white papers as a separate submission in support of the reference summary (not included in page count).

3. Does your product have the ability, out of the box, to perform all of the capabilities? If not, which requirements are not supported out of the box? What is the level of effort (and approximate cost/time) associated with adding the capability? How is customized development done within the confines of the product?

Technology Platform

4. Application Type. On what type of technology is your solution based?

mailto:Email mailto:Nicholas.Becht@dla.mil

5. Future Technology. What are your technology plans/roadmap for the proposed solution?

Describe how you keep your product up-to-date with improvements in information technology.

What is the schedule for future patches and upgrades? What is your software life cycle as it pertains to customer software upgrades? How long do patches and upgrades take on average?

What software engineering methods are available and how can they lend to more timely delivery of enhancements?

6. Information Security Requirements. Federal IT implementations entail significant security requirements and compliance with National Institute of Standards and Technology (NIST) mandates. Has your software been certified and accredited by a federal agency using either NIST, or the DOD Risk Management Framework (RMF)? If not, how do you plan to satisfy those requirements?

7. Section 508 of the United States Workforce Rehabilitation Act. Is the solution Section 508 compliant? Provide substantiation.

8. Prices. What is the ROM price for the software, licensing fees, maintenance fees, and system integration services for the proposed solution? Provide a separate price for each proposed element and include any pricing assumptions in your response. Please contact the contracting office if you need further clarification. Clarifications will be published in FedBizOpps. (see details below on the ROM submittal)

9. Licenses. What is your licensing Schema?

10. Disaster Recovery. What is your disaster recovery plan?

11. User Support. Is there a ticketing system?

12. Knowledge Management. How do your clients use your knowledge library? Do you have a list of clients that can speak to this?

13. Interfaces and Extensibility. What APIs or services does your solution provide to enable connections to other systems? What standards do those services leverage?

Implementation and Risk

14. Implementation Sequencing and Durations. Given your understanding of our requirements and environment, what is your typical implementation model? What is the estimated timeline from project initiation to full deployment? Please provide key milestones and the time it will take for each milestone within the timeline.

15. Risk. What are the five major risks associated with using your proposed solution to meet the requirements?

Vendor and Product Viability

16. General Services Administration (GSA) Schedules and Other Contract Vehicles. What GSA Multiple Award Schedule contracts, Government-wide Acquisition Contracts, Multi-Agency Contracts, or other contract vehicles does your company have to support the purchase of the proposed solution?

17. Enterprise Vendor Viability. As the vendor of the solution, provide an assessment of the strength of your customer base, and your presence in the market.

18. Vendor Support Services. What is the extent of support services for the solution proposed, including technical support, training, and consulting operations?

19. Product Maturity. What is the software lifecycle phase of the proposed solution?

Rough Order of Magnitude (ROM) Pricing

Please submit one ROM cost estimate for each proposed solution. The ROM estimate will help the Government determine the potential cost of acquiring and maintaining a solution over its life cycle. Please use the pricing template shown at Appendix V, to submit the estimate.

Vendors should use the following ground rules and assumptions to develop their ROM cost estimates.

• Cost period. Provide ROM pricing for a 3 or 4-year period, including annual inflation.

• Current-year dollars. Express costs in the value of the year in which a cost is expected to occur, including the effects of inflation.

• Inflation. Apply inflation using the appropriate annual inflation factor, where applicable.

• Ownership cost elements. Break out cost elements separately between 1.0 investment cost elements and 2.0 sustainment cost elements.

o 1.0 Investment cost—cost to acquire and deploy the system, including, but not limited to, software, integration/implementation customization, testing, initial training, and deployment.

o 2.0 Sustainment cost—cost to maintain and support the system over its life cycle, including, but not limited to, software maintenance and upgrades, help desk support, and recurring training.

• Scope. Provide ROM pricing to acquire, implement, maintain, and sustain a fully operational solution.

• System capabilities. Include pricing for requirements and system capabilities included in this RFI.

• Key milestone schedules. Provide a statement on feasibility of adhering to this milestone schedule for your solution. Assume the following schedule for pricing purposes only:

o Contract award C o Initial Operating Capability (IOC) C + 3 months o Final Operating Capability (FOC) C + 6 months

• Basis of estimate. List general ground rules and assumptions used to generate the ROM estimate for each cost element in a basis of estimate. Provide the details used to price each cost element explaining how costs were derived, including the assumptions made, unit costs, cost factors, quantities, hours, and calculations used to estimate costs.

• Cost elements.

o 1.0 Investment cost elements

1.1 Software. Include costs for system deployment software, including licensing, user fees, and application server fees for new software programs and an archive or backup copy required in the development and pilot environments as well as the cost for software warranties and initial documentation.

1.2 Interfaces. Include the cost to develop new system interfaces required to conform to user requirements and technical environment. Assume that interfaces fall into one of three categories (1) simple/small interfaces, (2) moderate/medium interfaces, and

(3) difficult/large interfaces. Please provide pricing for each category type.

1.3 Integration and implementation. Include the cost to develop requirements and business rules, customize/design the system, and access the initial setup.

1.4 Testing. Include costs for developmental and operating testing as well as for pilot testing to validate the proof of concept.

1.5 Initial training. Assume a 2 day initial on-site train the trainer class for functional users at multiple sites (Richmond VA, Columbus OH, Philadelphia PA).

If the vendor recommends additional training, include pricing and provide basis of estimate.

1.6 Deployment. Include the cost to install and activate an executable solution, including IOC and FOC activities.

o 2.0 Sustainment cost elements

2.1 Software Maintenance, Upgrades. Annual cost to provide software maintenance, including modifications, revisions, enhancements, corrections, and updates. Includes the cost to provide major software releases as applicable to the solution proposes.

2.2 Help Desk Support. Include the annual cost to provide Level-3 help desk support.

2.3 Training (Recurring). Include the costs for annual follow-on training based on employee attrition (turnover) rates.

o Cost template revisions. Add cost elements or adjust the price template where applicable to appropriately price the proposed solution.

o ROM cost risk. Identify at least three significant cost risk factors that could potentially increase (drive up) the cost of the projected ROM estimate submitted. Also, indicate the risk rating (high, medium, or low) for each cost risk and the expected percentage increase in total cost if the risk occurs.

APPENDIX I

ROM Pricing Template/Cost Estimate

OWNERSHIP COST ELEMENTS Year 1 Year 2 Year 3 Year 4 Tota l

1.0 INVESTMENT $0.00 $0.00 $0.00 $0.00 $0.00

1.1 Software $0.00 $0.00 $0.00 $0.00 $0.00

1.1.1 Licenses (enterprise) $0.00 $0.00 $0.00 $0.00 $0.00

1.1.2 User Fees $0.00 $0.00 $0.00 $0.00 $0.00

1.1.3 Appl ication Server Fees $0.00 $0.00 $0.00 $0.00 $0.00

1.2 Interfaces $0.00 $0.00 $0.00 $0.00 $0.00

1.3 Integration, Implementation $0.00 $0.00 $0.00 $0.00 $0.00

1.3.1 Requirements , Bus iness

Rules $0.00 $0.00 $0.00 $0.00 $0.00

1.3.2 Customization, Des ign, Development $0.00 $0.00 $0.00 $0.00 $0.00

1.3.3 Access Setup $0.00 $0.00 $0.00 $0.00 $0.00

1.4 Testing $0.00 $0.00 $0.00 $0.00 $0.00

1.5 Tra ining (Ini tia l ) $0.00 $0.00 $0.00 $0.00 $0.00

1.6 Deployment $0.00 $0.00 $0.00 $0.00 $0.00

2.0 SUSTAINMENT $0.00 $0.00 $0.00 $0.00 $0.00

2.1 Software Maintenance, Upgrades $0.00 $0.00 $0.00 $0.00 $0.00

2.2 Help Desk Support $0.00 $0.00 $0.00 $0.00 $0.00

2.3 Tra ining (Recurring) $0.00 $0.00 $0.00 $0.00 $0.00

GRAND TOTAL $0.00 $0.00 $0.00 $0.00 $0.00

BASIS OF ESTIMATE

1.1 Software

1.2 Interfaces

1.3 Integration, Implementation

1.4 Testing

1.5 Tra ining (Ini tia l )

1.6 Deployment

2.1 Software Maintenance, Updrade

2.2 Help Desk Support

2.3 Tra ining (Recurring)

Program Name

Request for Information

Rough Order of Magnitude Cost Estimate

Date: enter date here

APPENDIX II

ROM Pricing Template/Functional Requirement Estimate

LABORATORY MANAGEMENT SOLUTION

FUNCTIONAL REQUIREMENTS

NOTE: Detailed Descriptions of features are REQUIRED for all responses.

A - Feature is available off the shelf.

N - Feature is not available.

C - Feature is available with additional cost and custom programming.

Functional Description Feature Availability Detailed Description

SYSTEM ARCHITECTURE AND MAINTENANCE

Provide an outreach system that operates in a Windows environment.

Provide an outreach system that employs a centralized relational database.

Allow the outreach system to operate on all networking infrastructures, including local and wide area networks, and Internet based connectivity linking all practice sites.

Provide the ability for outreach solution to integrate with any LIS.

Provide the ability for outreach solution to integrate with multiple LIS’.

Allow full system functionality from any computer, regardless of computer specifications.

Provide a scalable system that can be expanded easily as our facility grows.

Provide an operational environment that will ensure the security and integrity of the system and all its data.

Provide for redundant storage of all system data files.

Provide for redundant processing capabilities to protect against processor failures.

Provide a checkpoint recovery capability to restore data files after a system failure.

Provide expanded descriptions for error messages.

Please describe any scheduled maintenance procedures.

SECURITY AND AUDITING

Provide a multi-level security system that is separate from the LIS to ensure the confidentiality of patient-related information and to control access to outreach functions and features.

Restrict access to specific areas of the application based on system function to be performed.

Provide practice level security ensuring that associates of one practice cannot gain access to the patient records of another practice.

Allow password protection at different levels (i.e. system administrator, phlebotomy, nursing, provider, etc.).

Allow a user of proper security clearance to modify the database parameters once the system is live, without requiring programming knowledge.

Restrict access to configuration tables, profile indexes, etc. to designated personnel via security controls.

Maintain an automated system log of user sign-on activity.

Maintain an audit trail for system entries including user code, date, and time of each system transaction.

Provide multi-level password security down to options within menus.

INTERFACING

Provide operational interfaces for the following applications (Please provide a functional description of each interface available):

Provide additional interfaces for multiple systems.

Provide all interfaces as an integral part of the application requiring no additional third-party software to implement or maintain the interface.

Provide technical support for all active interfaces.

ORDER ENTRY

Allow laboratory orders to be entered from any computer on or off the local network.

Allow the lab to develop and customize orderable items.

Allow simple test ordering: Single header linked to a single test result field (

Allow compound test ordering: Single header linked to multiple test result fields (e.g. CBC, Lipid Panel, and Comprehensive Metabolic Panel).

Allow the user to order tests by entering test codes and/or by selecting from a test menu.

Automatically alerts users to previously ordered lab work.

Allow at the time of ordering a request that patient lab results be sent to more than one provider.

Allow entry of four diagnosis codes for each ordered test.

Provide automatic label printing as orders are entered.

Allow lab-defined label configuration.

Describe the bar code formats your outreach solution accepts and prints.

Provide the specific sample requirements or sample tube types at the time of order entry.

Support sample storage and retrieval modules for the purpose of drug testing, add-on testing, etc.

Allow a miscellaneous test code so previously undefined tests can be ordered and charged.

Ability to correct a field on a screen without having to re-enter entire order transaction.

Allow entry of orders for future dates.

Allow splitting one ordered test into more than one request

Automatically check for and warn of duplicate single test orders with profile orders.

Provide simple method to order additional test requests on sample already received and processed in lab.

Allow cancellation of an order without canceling prior results.

Provide flexible, customizable Sample ID formats.

Print sample collection labels for timed and routine collections.

Allow for multiple labels per test to print.

Print instructions/comments (e.g. do not collect from right arm) on sample labels.

Print aliquot labels when more than one test is drawn in the same collection tube.

Provide that uncollected samples continue to appear on subsequent lists until cancelled or collected.

Provide for easy free text entry of information such as critical result notification, sample rejection, or culture sites.

Provide for intelligent prompting for accessioning; e.g. When a wound culture is ordered, the system prompts the user for site/location.

Provide easy access to sample requirements for laboratory users.

Provide intelligent sample labeling – groups samples in chemistry together and prints on labels, while hematology tests print on separate label and microbiology prints separately. Allows for making the number of labels customizable for each test.

Provide intuitive user interface – easy to locate screens for accessioning, reporting queries, etc.

Provide for an easy, systematic, and logical method of adding, editing, or deleting tests in the test code dictionary.

When looking up a patient in the system, tests performed on that patient and test results are made available without additional steps.

Allow outreach clients to customize their own order entry screens to fit their practice’s needs.

Allow outreach clients to customize colors and logos of the system for their practice only.

RESULT REPORTING

Provide ability to auto deliver results by the following methods:

Web Delivered (i.e. Provider logs in to a website to retrieve results)

Email

Fax

Print

Electronic interface to client information system (EMR, HIS, PMS, etc.)

Accept images, graphics and linked documents from a host LIS via interface to display on reports.

Provide ability to designate HTML or PDF format of reports.

Maintain patient result history indefinitely.

Provide ability to purge results after a specific amount of time if desired.

Provide ability to graph historical results on a report.

Provide scheduler for automatic result delivery.

Allow re-delivery of results.

Automatically maintain a record of reports delivered by each reporting modality (FAX, Printer, and E-Mail, etc.). Provide easy access to these results at any time.

Allow patient test to be incomplete for at least 8 weeks in the system.

Print daily detailed master log of all work performed in lab for audit purposes.

Display abnormal or critical results uniquely from other results.

Allow for cumulative result reporting.

Please explain.

Describe the procedure for correcting test results that have been resulted. After correcting, are the corrections able to be altered?

Print list of received but untested samples due to insufficient quantity.

Allow for a comment to be placed on the sample accordingly.

Includes features that allow batch reporting.

Provide ability to batch print and batch acknowledge receipt of results.

Provide the date/time reported on reports transmitted by FAX, laser printer, and e-mail.

Provide a permanent log of all test results that have been edited.

Workstations work independently of each other. Multiple functions can occur simultaneously without one party having to exit the system.

Provide flexible reporting formats.

Provide the ability to access all patients of a particular client by name, date, or date range.

Allow look-up of patient and patient results by client number.

SAMPLE STATUS AND TRACKING

Provide the ability to track patient samples throughout the testing process.

Provide identification of the individual who ordered the test, collected the sample, and released the test results, including the date and time of these occurrences so that this information is accessible throughout the process.

Support user-defined priorities.

Include data for tracing order (dates, times, tech ID, results) from order entry to final reporting in master log.

Provide index to master log by accession number.

Provide customizable sample storage tracking including identification of freezers, refrigerators, etc.

Allow sample storage/retrieval by use of a barcode scanner (i.e. the requisition is scanned into the system and the system tells the laboratory where the sample is stored in the lab).

MANAGEMENT AND ADMINISTRATION

Provide ability to create completion reports by date.

Provide ability to create cancelled test reports that include test name and reason for cancellation.

Provide ability to create turnaround time reports by date.

Provide a summary report for test usage over a user-definable period of time.

Provide ability to print a list of draws that need to be performed.

DATA MINING

Provide user-friendly report generator with graphical user interface as an integral part of the outreach application.

Provide ability to create reports from any computer.

Provide ability to create a billing report.

Provide ability to create a report showing all tests completed during a date range.

Provide ability to create a report for order exceptions.

Provide ability to generate patient lists (with certain demographic data) who meet specific result criteria for public health reporting.

Provide ability to create reports on standing or recurring orders.

Provide ability to write queries using logic in great detail within the application.

Support the use of commercially available tools for report generation.

Provide ability to save commonly performed searches.

Provide ability to schedule automatic, unattended runs of data reports.

Provide ability to create reports to mine patient data for specific practices within the application

Provide on-line help screens to assist novice users in all applications.

Response Instructions