SOURCES SOUGHT
D -- Consult Evaluation System
- Notice Date
- 6/13/2002
- Notice Type
- Sources Sought
- Contracting Office
- Department of Health and Human Services, National Institutes of Health, Clinical Center/Office of Purchasing & Contracts, 10 Center Drive, RM 1N262, MSC 1189, Bethesda, MD, 20892-1189
- ZIP Code
- 20892-1189
- Solicitation Number
- 061302
- Response Due
- 7/8/2002
- Archive Date
- 7/23/2002
- Point of Contact
- Andrea McGee, Purchasing Agent, Phone 301-402-0735, Fax 301-435-8675, - Andrea McGee, Purchasing Agent, Phone 301-402-0735, Fax 301-435-8675,
- E-Mail Address
-
andrea_mcgee@nih.gov, andrea_mcgee@nih.gov
- Description
- Statement of Work Consult Evaluation System Background The mission of the National Institutes of Health is to uncover new knowledge that will lead to better health for everyone. The NIH accomplishes that mission by: conducting research in its own laboratories; supporting the research of non-Federal scientists in universities, medical schools, hospitals, and research institutions throughout the country and abroad; helping in the training of research investigators; and fostering communication of biomedical information. As an organization, the NIH is unique. Management is intentionally decentralized into 24 Institutes and Centers, which cooperate and collaborate in the management and conduct of research. This decentralized environment fosters a broad range of investigator-initiated research. The Warren Grant Magnuson Clinical Center, a 240-bed biomedical research hospital, is part of the NIH campus in Bethesda, Maryland. The Clinical Center is the setting in which most NIH intramural clinical trials are carried out, and it accounts for about half the NIH-funded dedicated clinical research beds in the country. About 7,000 patients per year are admitted to the inpatient services, and 70,000 per year are seen as outpatients. Care for inpatients and outpatients in the Clinical Center is provided by staff physicians who, in general, are employed by the 17 Institutes that have clinical programs on the NIH intramural campus in Bethesda. The hospital is organized into floors and clinics, with each floor or clinic typically serving one or a small number of Institute programs. For example, the National Cancer Institute (NCI) cares for patients admitted on NCI protocols on two floors and one clinic in the hospital. General guidelines to establish the standard of care in the hospital are established by the Medical Executive Committee (MEC), a body composed of the Director of the Clinical Center and the Clinical Directors of all the Institutes with clinical programs. The MEC is responsible for patient safety and quality of care throughout the Clinical Center. The Consult Review Committee is a chartered subcommittee of the MEC that is responsible for assuring that consults performed within the Clinical Center meet the hospital's standards for quality and safety. Subspecialty consults are not performed by hospital staff, but rather by staff belonging to the Institute that covers that particular subspecialty within its mission. Oncology consults are provided by NCI, ophthalmology consults are provided by the National Eye Institute (NEI), Dental Consults by the National Institute of Dental and Craniofacial Research (NIDCR), etc. Because of the relative autonomy of the Institutes, it is difficult to capture information on consult quality for use by the Consult Review Committee or for feedback to the Institute providing the consult service. The consult process starts when a provider enters an order for a consult into the Medical Information System (MIS) and is completed when the consultant files a consult on an NIH form M513 in the patient's chart. This form is printed by the MIS when the consultant logs into the system and completes the consult order. The detailed operations of the consult service between these two processes are left largely up to the Institute that runs the consult service. This Statement of Work is for the development of an ancillary Consult Evaluation System (CES) that will automatically generate electronic evaluation questionnaires for both the consult requestor and the consultant, that will securely collect the information on these forms, and that will make the contents of these evaluations available both individually and as aggregated data in reports. Volumes There are currently 39 consult services, although this number is expected to increase. These are: Adult auditory assessment Allergy and immunology Anesthesiology Cardiology Children's hospital pediatric consult Critical care medicine Dental Dermatology Endocrinology Gastroenterology Genetics Gynecology Hematology Hepatology Infectious disease Internal medicine Nephrology Neurology Neurosurgery Nutrition Opthalmology Orthopedics Otolaryngology Pain and palliative care Pediatric auditory assessment Pediatric rheumatology Podiatry Psychiatry Radiation therapy Surgery, general Therapeutic phlebotomy Thoracic surgery Transfusion medicine Urology Vascular access device Vestibular assessment Wound, ostomy, continence Annual consult volumes, based on six months of data ending 3/02, range from 4 consults per service to 1706 consults per service. Total consult volume, based on six months of data ending 3/02, is 10,140 consults per year. Requirements Infrastructure 1. The system shall use an established SQL compliant relational database management system (DBMS) to store evaluation data. This DBMS shall be one already in use in the NIH Clinical Center (e.g. Oracle, Sybase). 2. The DBMS shall run under an operating system (OS) already in use in the NIH Clinical Center (e.g. Windows 2000, Windows XP, Mac OS X, Sun Solaris, IBM AIX). 3. The application server, if one is used, shall run under an operating system (OS) already in use in the NIH Clinical Center (e.g. Windows 2000, Windows XP, Mac OS X, Sun Solaris, IBM AIX). 4. The system user interface shall be World Wide Web based. 5. The web-based interface shall run in a functionally equivalent manner on the following client platforms: Windows 98, Windows 2000, Windows NT 4, Windows XP, Mac OS 8.x, Mac OS 9.x, Mac OS 10.x. 6. The web-based interface shall run in a functionally equivalent manner in the following web browsers: Microsoft Internet Explorer version 5.1 or higher (Mac OS), Microsoft Internet Explorer version 5.5 or higher (Windows). 7. The web-based interface shall require no installation of software on client computers other than a standard installation of the OS and web browser software. 8. All data transmitted by the application over the NIH intranet or the public Intranet that contains patient identification shall be encrypted. A solution that requires servers to reside behind a firewall for communication between the application server, DBMS server, and web server, is acceptable. 9. The system shall not require a real-time interface to the MIS. The MIS is able to send reports to a virtual printer; these reports can be collected in a file system. A solution that requires electronic parsing of information from these reports is acceptable. Functional See attachment 1 - proposed process flowchart. See attachment 2 - proposed consultant and requestor evaluation forms. See attachment 3 - NIH Form M513. 1. The system shall collect consult ordering information from the MIS within 24 hours of the time that the consult order is entered in the MIS.. This information shall include, at a minimum, date of consult request, patient identification, reason for the consult, requestor identification, consult service requested, MIS order number, patient location, patient service, and patient diagnosis. 2. The system shall send notification requesting evaluation of the consult process to the consultant within 24 hours of completion of the consult in the MIS. Note that the notification and the subsequent evaluation can be separate processes. 3. The system shall send notification requesting evaluation of the consult process to the requesting provider 24 hours after the Consult Evaluation System is notified that the consult is completed in the MIS. Note that the notification and the subsequent evaluation can be separate processes. 4. The system shall send reminders to the consultant and requestor at weekly intervals until the evaluations are completed or until an established number of weeks have passed without an evaluation. 5. The system shall have the ability to flag an evaluation as not returned, and to forego further reminders. 6. The system shall collect the data entered on the consultant and requestor evaluation forms in a relational database. 7. This relational database shall, at a minimum, include the following information: date of consult request, patient identification, reason for the consult, requestor identification, consult service requested, MIS order number, patient diagnosis, patient location, patient service, all fields from the evaluation forms, date of evaluation, and evaluator identification. The system may populate provider and patient tables through an interface or view into another system (e.g. the Clinical Data Repository, the MIS User Database). 8. The system shall send notification to the Consult Review Committee upon the following events: completion of consultant evaluation, completion of requestor evaluation, flagging of an evaluation as not returned. 9. The system shall send notification to the Consult Review Committee based on the content of the evaluation forms. For example, a consult process rated unsatisfactory or unsafe by either the requestor or the consultant shall result in immediate notification of the Consult Review Committee. 10. The system shall provide, at a minimum, the following reports: number of consults performed aggregated by consultant, number of consults performed aggregated by consult service, number of consults performed aggregated by requesting service or location, summary evaluation statistics on consults performed aggregated by consultant, summary evaluation statistics on consults performed aggregated by consult service, and summary evaluation statistics on consults performed aggregated by requesting service or location 11. The system shall provide the ability to make ad hoc queries of the consult review database using third party tools (e.g. Crystal Reports) or directly through the Consult Evaluation Application. Documentation 1. The contractor shall provide full documentation of the database data model and data dictionary. 2. The contractor shall provide full documentation of mappings from MIS or Clinical Data Repository data fields to the Consult Evaluation System data fields. 3. The contractor shall provide sufficient documentation of the user interface and application server so that the government can modify evaluation forms or database tables without contractor intervention after the system is "live." 4. The contractor shall provide a computer-based training module on the use of the system. 5. The contractor shall provide full documentation on the use of the system. Maintenance 1. The system shall be designed so that maintenance of the application server, DBMS, database, data dictionary, and interfaces can be performed by the government at completion of the contract. Reporting 2. The contractor shall provide at the time of award a detailed timeline and project plan. This project plan shall include all anticipated activities, and should clearly identify the project's critical path. The project plan shall also include identification of resources associated with each identified task. 3. The contractor shall provide bi-weekly status reports that shall include, at a minimum: activities planned for the reporting period, work completed during the reporting period, status of ongoing activities, problems or issues projected or identified, recommended and alternative solutions for identified or projected problems or issues, resource (staff and funding) status. The bi-weekly status report shall also include any updates or modifications to the project plan or timeline, with projected impact of these updates on project completion date or projected resources required. 4. The contractor's Project Manager and other necessary staff shall participate in weekly management meetings and be prepared to present and discuss, at a minimum, the items identified in the requirements for the bi-weekly status report. 5. The contractor shall maintain an electronic problem-tracking database which contains, at a minimum: problem description, problem status, date problem was identified, date problem was resolved, individual or contact responsible for resolving problem, problem priority.
- Place of Performance
- Address: 9000 Rockville Pike, 10 Center Drive, Bldg. 10 Rm. 2C146, Bethesda, MD
- Zip Code: 20892
- Country: USA
- Zip Code: 20892
- Record
- SN00092928-W 20020615/020613213118 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |