Here are some sample functional requirements for the CPR RFP template:
|
| ►
Master Person Index
|
| Support on-line enterprise-wide master person index (EMPI) consisting of patient demographic, insurance and visit history information for every patient identified to the health care enterprise. |
| Provide cross-reference indexes that link the universal patient EMPI number to facility-specific (e.g. home health, physician clinic systems) patient numbers. |
| Automatically share patient demographic and financial data among all individual facility patient information systems (e.g. home health, physician clinic systems) to streamline the patient registration |
| Provide ability to add new patients to the master person index via registration and scheduling processes from interfaces patient information systems. |
| Support suspected duplicate EMPI record reporting with tools to merge and delete records, if appropriate. |
| ►
CPR Data Access
|
| Provide on-line access to CPR data including: historical patient information such as medical history, previous test results and abstracts. |
| Provide ability to restrict views based on additional parameters, such as "need-to-know" basis. |
| Provide tools and ease-of-use features so that system administrator can tailor views of CPR data for clinicians, nurses, etc. (e.g. without vendor assistance). |
| Utilize self-learning technologies and knowledge bases to facilitate the tailoring of individualized CPR views. |
| Support integration of knowledge databases, information services and clinical practice guidelines into the clinical decision-support services inherent in the system. |
| ►
Problem List
|
| Support detailed on-line patient problem list that includes: problem category (e.g. acute, chronic, recurring, lifelong, etc.). |
| Provide ability to enter and attach comments to problems in patient problem list. |
| Provide ability to automatically generate problem description text from physician's dictation. |
| Support automated linkages between patient problems and medical literature or other medical knowledge bases. |
| Automatically check all problems and codes against current regulations for RBRVS/E&M codes to ensure that adequate documentation is included. |
| ►
Problem Solving
|
| Provide access to diverse problem-solving aids (e.g. knowledge bases, analytical tools) including support for automatic tracking, documentation, and evidence showing the logic and rationale used. |
| Provide ability to easily incorporate and invoke new analytical and problem-solving tools which are designed to enhance the clinician's problem-solving skills. |
| Facilitate specialty- and sub-specialty-specific needs of clinical problem solving. |
| Automatically display timely reminders to clinicians just prior to each patient encounter. |
| Utilize key patient-specific parameters to automatically access appropriate analytical tools and knowledge bases (e.g. PDQ) to provide highly-targeted information for clinical problem solving. |
| ►
Health Measures
|
| Support use of at least one commonly accepted measure of functional level. |
| Automatically encourage systematic measurements of patient's health status and record in CPR. |
| Provide ability for the system administrator to add new health status measures to the system. |
| Support advanced versions of the SF-36, such as Paul Ellwood's (disease-specific) Types.. |
| Incorporate knowledge bases and outcomes tools to support direct monitoring and feedback of outcomes to clinicians. |
| ►
Documentation
|
| Provide specifically designated place in the CPR for storing information about why clinical decisions are or were made. |
| Provide ability to automatically capture decision-making rationale in documenting the decision-making processes. |
| Support services which facilitate documentation of individual clinician's thinking as well as that achieved through the interaction of all members of the healthcare teams. |
| Provide ability to link the rationale for clinical decision making with all clinical practice guidelines to show how and why deviations may have occurred. |
| Provide ability to display clinical decision-making rationale history to facilitate decision making by additional clinicians seeing the patient concurrently or in subsequent encounters. |
| ►
Security
|
| Provide security functions to limit access to authorized users. |
| Provide access to individual system functions (e.g. menu options) through a hierarchy of privileges definable by system administrator. |
| Provide security checks to control user access to patient information based on: user ID. |
| Provide ability to automatically log workstations off the system after a specific period of inactivity, definable by system manager. |
| Provide ability to prohibit unauthorized downloading of data to intelligent workstations and PC's. |
| ►
Confidentiality
|
| Provide computerized audit trail of all users who have accessed or updated a patient record, including date / time stamps and location of access. |
| Provide security checks to control user access to patient information based on patient / physician association. |
| Provide ability to limit physician access to patient information to admitting, attending, ordering and consulting physicians. |
| Provide ability for the patient and physician to establish the desired confidentiality level down to the data-element level in the CPR. |
| Support electronic signature for members of the healthcare team using accepted and evolving industry standards. |
| ►
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. |
| Provide mechanism for entity (e.g. unique individual) authentication such as: biometric (e.g. hand geometry, retinal/iris scan, fingerprint patterns, facial characteristics). |
| Create electronic claim files in ANSI X.12 version 4010 format for institutional and professional claims generated in Patient Accounting system. |
| Provide contractual guarantee to deliver software releases and updgrades to ensure HIPAA compliance for current regulations within 12 months after go-live at no additional cost. |
| ►
Technical & Support
|
| Support graphical user interface GUI (e.g. Windows, buttons, toolbars, mouse, etc.) and menu-driven user control and initiation of system functions. |
| Support ability to use web browser (e.g. Internet Explorer) to access system functions over Internet or internal intranet. |
| Support the use of "drag-and-drop" with mouse as option to visually initiate system functions (e.g. drag a file icon to printer icon to start printing a report, etc.) |
| Use RAID, disk mirroring, volume shadowing and/or other fault tolerant technology to increase reliability of disk storage and also minimize data loss due to hardware failure. |
| Provide commitment to support HL7 (Health Level 7) healthcare industry system integration standards. |
| ►More... |
Selecting a new Electronic Medical Records system?
will
help you create
your RFP for a new electronic medical records (computerized
patient
records ) system and automatically
evaluate vendors' responses.