Here are sample functional requirements from the Lab RFP template:
|
| ►
Patient Registration
|
|
Support ADT interface using HL7 standard with HIS to receive patient demographic data.
|
|
Support patient inquiry by patient name regardless of punctuation or spaces (e.g. Mc Donald or O'Donnell).
|
|
Provide ability to identify and store which facilities a patient is associated with in a multi-entity environment.
|
|
Support ability to automatically purge patient records based on user-defined criteria.
|
|
Support patients with different medical record numbers but having a common account/billing number. (ex: Outreach, HMO patients with unspecified account number.)
|
| ►
Order Entry
|
|
Support direct on-line entry of orders into lab system with ability to send orders back to HIS through the interface.
|
|
Include patient location (e.g. nursing station, room and bed for inpatients or outpatient location) in order data.
|
|
Provide on-line help displaying user-defined test codes (e.g. mnemonics) and descriptions for ordering.
|
|
Automatically check for and warn of duplicate single test orders within profile orders.
|
|
Support automatic cancellation of future orders based on user-defined criteria (e.g. ten days after discharge of patient).
|
| ►
Specimen Control
|
|
Support ability to "bundle" multiple procedures ordered into one accession number based on user defined parameters.
|
|
Support bar coded wrist bands for patient identification, which can be read with a wand by a phlebotomist when collecting specimen.
|
|
Print patient ID numbers (Medical Record No., Master Patient Index No., Financial No.) on collection labels.
|
|
Support specimen login (specimen receipt) method for both Clinics and Hospitals which accommodate differences in workflow with minimal keystrokes.
|
|
Provide ability to enter freetext identification of non-laboratory personnel collecting specimens.
|
| ►
Worklists
|
|
Provide ability to generate loadlists for each specific automated analyzer.
|
|
Provide ability to print worklists for individual test, groups of tests and profiles.
|
|
Support ability to re-allocate work from one work station to another (e.g. instrument to instrument, entity to entity).
|
|
Provide ability to use worklists to enter test results by workstation.
|
|
Provide ability to exclude accession(s) in worklist during batch verification.
|
| ►
Results Reporting
|
|
Support capture and processing of result data from automated analyzers via computerized (i.e. TCP/IP) interface.
|
|
Support the ability for user to suppress specific parameters from an instrument interface from displaying in result entry function.
|
|
Provide ability to define delta values (absolute, % change) across facilities and alert users when delta has been exceeded during result entry.
|
|
Provide ability to alert users prior to release of a result that is defined as a critical value.
|
|
Provide capability to allow a portion of a profile to be verified and reported before complete profile is verified and reported.
|
| ►
Quality Control
|
|
Ability to allow control limits to be set/defined by authorized users.
|
|
Provide capability to automatically validate that lab-defined QC rules are met before allowing release of patient result.
|
|
Provide ability to normalize control data so that all QC levels can be used simultaneously to provide sufficient number of data points.
|
|
Provide ability to provide option to print Levy-Jennings plot showing individual data points.
|
|
Provide ability to link patient testing to a specific workstation or rack number.
|
| ►
Patient Reporting
|
|
Allow authorized users to easily define multiple patient report formats (e.g.custom address headers, HIV excluded, etc). Comment on any limitations to number of formats available.
|
|
Provide ability to print separate reports for all physicians (e.g. consulting, ordering, referring,etc) associated with a patient.
|
|
Provide ability to print HIS or LIS patient-level comments stored in patient account record (e.g. patient on Heparin therapy).
|
|
Provide ability for authorized users to reformat interfaced reference lab results, and print on patient reports.
|
|
If archiving patient data is needed, provide ability to fully restore and print data on patient report.
|
| ►
Management Reporting
|
|
Provide audit of all transactions from order entry to result verification (Master Log).
|
|
Provide ability to print daily detailed master log sorted by user-defined criteria of all resulted lab tests for audit purposes.
|
|
Provide ability to print report of original and any/all subsequent results when results are modified after verification including modified date/time, user id and any pertinent comments.
|
|
Provide ability to report all patients who had a specific test and whose test results were within a specified numeric range (e.g. cholesterol > 200), by provider.
|
|
Support ability to print report of selected patient tests based on end user defined categories to capture statistics for vendor reimbursement.
|
| ►
Billing
|
|
Support user-defined customization of billing interface transaction files to include specific order or patient information with charges
|
|
Provide ability to define manually billed procedures for all test types (e.g Microbiology, Blood Bank).
|
|
Provide ability to define charges for single procedures or for profiles with multiple procedures.
|
|
Provide ability to automatically identify and eliminate duplicate phlebotomy charges.
|
|
Maintain all patient billing / charge transactions on-line and allow end user to view patient billing history.
|
| ►
Microbiology
|
|
Provide ability to create and modify an on-line dictionary of pre-coded specimen source designations.
|
|
Provide ability to record comments about specimen including adequacy, collection method, etc. during receiving and processing.
|
|
Support ability to flag positive results and store in permanent record based on user-defined parameters.
|
|
Alert user, in batch resulting, when an accession had a previous positive result prior to result verification/release of a negative result. Comment on scenarios where alerts would fail.
|
|
Automate identification of patients that are infection risks based on culture resulting and post to Infection Control functions.
|
| ►
Hematology
|
|
Support ability to build multiple morphology descriptions for each cell type (e.g. WBC, RBC, platelets).
|
|
Support ability to calculate and report absolute white blood cell count when a manual differential count is performed.
|
|
Support entry of Complete Blood Count cell differential into PC through user-defined keys on keyboard.
|
|
Provide system alerts prior to result release to indicate additional testing is required based on user defined parameters (e.g. reducing substances for newborn).
|
|
Support entry of multiple types of body fluid cell differentials into PC through user-defined keys on keyboard (e.g. synovial, semen, etc.).
|
| ►
Blood Bank
|
|
Track status of blood request orders by patient medical record number (e.g. received, ready, dispensed, released).
|
|
Allow user to determine event which drives billing of credits for returned units of blood recording time in and time out.
|
|
Units entered into system automatically assume a default status that is user-defined by component.
|
|
Support printing and reprinting of a Transfusion Record based on user-defined parameters, including a product label for all products prepared for transfusion at either time of crossmatch or issue.
|
|
Maintain, display and print complete blood product history indefinitely for all transactions (e.g., user Ids, inspection at receipt and issue, product modifications, status changes, etc).
|
| ►
Anatomic Pathology
|
|
Support ability to identify specimen type for a given accession number (e.g. bone marrow, surgical, ngyn fluid).
|
|
Provide ability to track activity for cases with pending special procedures such as outside consultation, special stains.
|
|
Provide for flags on reports for quality assurance, tumor board, and other user defined criteria.
|
|
Create ad hoc reports by user defined criteria, e.g. patients by age, location, specimen type, malignancy, etc.
|
|
Provide ability to print worksheets that include previous diagnoses, demographic and accessioning information and user-defined templates for Gyn Cytology.
|
| ►
HIPAA
|
|
Support an enterprise-wide single sign-on user authentication process that allows individual users to logon to different systems with one global user ID and password.
|
|
Support data access controls that allows assignment of security at the data element level within files.
|
|
Support a separate Provider file that can accept and process automatic updates from a national Provider Database.
|
|
Support Health Plan ID in all software modules that use Health Plan ID.
|
|
Provide ability to create data files for teaching purposes that meet HIPAA guidelines for compliance (e.g. tracking without specific patient information).
|
| ►
Technical & Support
|
|
Provide contractual commitment to support HL7 (Health Level 7) healthcare industry system integration standards.
|
|
Provide ability to support a single database that is not partitioned but can be customized by entity for different business needs.
|
|
Support graphical user interface GUI (e.g. Windows, buttons, toolbars, mouse, etc.) and menu-driven user control and initiation of system functions.
|
|
Provide interface to and allow archival of data on archive storage media (e.g. CD-ROM, tape).
|
|
Provide future software releases and updates to all applications as part of regular software maintenance fees.
|
| ►
More requirements are included in the actual RFP, this is only a sample. |