|
Here are some
sample functional requirements from our LIS RFP: |
|
► Store diagnoses codes in registration function. |
|
► Support retrieval of patient records by partial (e.g. first few letters
of) patient last name. |
|
► Support interface to order communications system of HIS to automatically
receive order data. |
|
► Include test, profile, or battery name (mnemonic code) in order data. |
|
► Process orders for profiles that include multiple tests (e.g. cardiac
enzyme profile). |
|
► 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 (e.g. group
tests, pre-op, coag screen). |
|
► Allow review and verification of held orders on-line by technologist. |
|
► Automatically check for and warn of duplicate single test orders with
profile orders. |
|
► Support cancellation of tests--logging accession #, test code, patient
name, reason, date, time, and tech ID. |
|
► Provide simple method to order additional test requests on sample already
received and processed in lab. |
|
► Allow cancellation of an order without canceling results. |
|
► Provide access to price information within order entry function. |
|
► Provide option to assign assession numbers at time of specimen receipt. |
|
► Print specimen collection labels for timed and routine collections. |
|
► Provide multiple labels per test ability to print. |
|
► Print tube type and volume on specimen labels. |
|
► Print instructions/comments (e.g. do not collect from right arm) on
specimen labels. |
|
► Print phlebotomist activity summary showing first & last draw times,
locations, # patients drawn, and # misses. |
|
► Allow patient test to be incomplete for at least 8 weeks in the system. |
|
► Flag routine orders when timed pick-up or stats etc. are ordered, to
prevent multiple sticks. |
|
► Print aliquot labels when more than one test is drawn in the same
collection tube. |
|
► Ability to remove unsuitable or lost specimens from work list, flag in
system, and activate recollection. |
|
► Provide that uncollected specimens continue to appear on subsequent lists
until cancelled or collected. |
|
► Support a way to identify the phlebotomist, (doctor, nurse, etc.) in
system for specimens not drawn by laboratory personnel. |
|
► Track worklists by unique control number for on-line inquiry, reporting,
and audit purposes. |
|
► Allow user to easily define worklist formats for different work stations
without programming. |
|
► Print worklists by workstation. |
|
► Print ordering physician on worklist. |
|
► Print the lot number of the reagent in use for the specific test on the
worklist. |
|
► Flag uncollected specimens on worklist. |
|
► Allow lab technologist to update worklist on-line for STAT tests. |
|
► Provide on-line inquiry into work list by test type. |
|
► Print daily detailed master log of all work performed in lab for audit
purposes. |
|
► 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. |
|
► Assign quality control specimens to a worklist on a rotating basis, in a
predefined sequence, specific to each worklist. |
|
► Support ability to edit, insert, and delete items on worklists to meet
immediate needs. |
|
►
Support capture and processing of result data from automated analyzers via
computerized (e.g. RS-232) interface. |
|
►
Automatically record start, stop, and elapsed time of automated analyzer
tests. |
|
► Display patient age and sex in results entry screen. |
|
►
Provide capabilities for graphic display of test results. |
|
►
Support entry of comments for non-numeric results and interpretative
reporting in results entry screens. |
|
►
Maintain edit table of lab-defined panic, delta, and reference result
ranges based on age and sex. |
|
► Display previous test's value, time, and date if delta check limit is
exceeded during result entry. |
|
►
Print list of received but untested specimens due to insufficient
quantity. |
|
►
Print list of all patient tests that require scrutiny (e.g exceed delta
check, panic values, reference intervals). |
|
► Track activity for special procedures related to surgical pathology. |
|
►
Provide physician utilization report (e.g. number of tests requested by a
physician). |
|
►
Generate outpatient statistics based on financial class. |
|
►
Calculate employee productivity by shift, by month, by year, and to date. |
|
►
Allow stats to be weighted more than routine procedures. |
|
► Ability to generate patient lists (with certain demographic data) who meet
specific result criteria for public health reporting. |
|
►
Maintain calibration records for on-line instruments. |
|
►
Allow for instrument status (recent service, troubleshooting, etc.) to be
stored on-line. |
|
►
Generate revenue reports by test. |
|
►
Count slides as one-half for certain types of specimens for calculation of
slides screened by a Cytotechnologist. |
|
► Provide ability for user to determine and change the workload for a
Cytotechnologist at any time. |
|
► Report the technical supervisor's re-examination of 10% of each
Cytotechnologist's case workload. |
|
► Compare the annual statistical evaluation for each Cytotechnologist
against the laboratory for the number of gynecologic cases where cytology
and histology are discrepant. |
|
► Report daily cytology smear quality review. |
|
► Support automatic interface to HIS for transmitting patient lab charge
data. |
|
► Provide group billing for non-hospital clients (e.g. physician's office,
clinics). |
|
► Support multi-tiered price structure by service type (e.g. IP, OP,
contract, referred). |
|
► Support price structure that accommodates higher prices for tests with
multiple CPT4 codes. |
|
► Support entry of reason for discarded, outdated, and quarantined units. |
|
► Support entry and tracking of lot number of reagent used for a particular
patient. |
|
► Alert the user to the entry of an ABO & Rh type that disagrees with
previous results. |
|
► Provide report of units outdated, returned to supplier, and % units
crossmatched but not transfused, by diagnosis & surg. procedure. |
|
► Provide comment field in blood unit inventory record. |
|
► Allow manual entry of date/time of issue of unit if system was down. |
|
► Ability to track blood products e.g. packed cells, whole blood, FFP, Cryo,
Platelets, etc. |
|
► Display antibodies with patient demographics. |
|
► Log all transactions by date, by time, by technologist. |
|
► Allow simultaneous multiple crossmatches on multiple patients. |
|
► Provide monthly report of crossmatch to transfusion ratio. |
|
► Ability to identify autologous / designated donations or a special antigen
type. |
|
► Ability to override the system if an incompatible unit needs to be
transfused. |
|
► Warn user if retyping results entered do not match the blood type entered. |
|
► Ability to assign a pooled number for 2 to 10 units combined for a single
transfusion. |
|
► Alert personnel if an outdated unit is chosen from inventory. |
|
► Provide on-line help screens to assist novice users in all applications. |
|
► Provide multi-level password security down to options within menus. |
|
► Utilize code tables for processing control and other system parameters
that can be maintained by system administrator. |
|
► Provide user-friendly report generator software with graphical user
interface. |
|
► Provide access to system maintained data element definitions within report
writer software. |
|
► Maintain and allow on-line access to a system-wide data dictionary. |
|
► Provide data management design that supports integration and sharing of
data among all applications. |
|
► Provide data management features that eliminate the redundant maintenance
of duplicate data (e.g. relational database, etc.). |
|
► Provide sufficient back-up and recovery features to assure minimal data
loss due to a system failure, power outage, etc. |
|
► Provide sufficient back-up and recovery features to assure minimal data
loss due to a system failure, power outage, etc. |
|
► Provide technical documentation for support staff including system
overviews, design, flowcharts, and file layouts. |
|
► Provide ability for system administrator (or other authorized user) to
modify screen layouts and flow with minimal programming effort. |
|
► Provide future software releases and updates to all applications as part
of regular software maintenance fees. |
|
► Provided toll free customer support 24 hours, seven days per week. |
|
► Provide commitment to support HL7 (Health Level 7) healthcare industry
system integration standards. |
|
► More... |