SOURCES SOUGHT
70 -- Patient Safety Program Data Mgt. System
- Notice Date
- 9/16/2002
- Notice Type
- Sources Sought
- Contracting Office
- General Services Administration, Federal Technology Service (FTS), FTS, 7T-6 Southwest Texas, 727 E. Durango, Rm A105, San Antonio, TX, 78206-1283
- ZIP Code
- 78206-1283
- Solicitation Number
- TaskFE212618T6
- Point of Contact
- Joe Eason, Contracting Officer, Phone (210) 472-5050, Fax (210) 472-5054, - Clifford Trowbridge, Contracting Officer, Phone 210-472-5042, Fax 210-472-5054,
- E-Mail Address
-
joe.eason@gsa.gov, clifford.trowbridge@gsa.gov
- Description
- The General Services Administration (GSA) Federal Technology Services (FTS) is seeking sources for the United States Army Medical Command, for a Patient Safety Program Data Management System. Interested vendors must have a GSA Federal Supply Service (FSS) contract or the ability to team with a FSS contract holder. The Request for Proposal will be released (via GSA's web based ordering system ITSS)once comments have been received from this Notice. Briefly describe your corporate capabilities to support this requirment. 1.0 SUBJECT There is a requirement for a Patient Safety Program Data Management System for the US Army Medical Command, Patient Safety Center (MEDCOM, PSC) at Fort Sam Houston, TX. This requirement is established by: 1. DoD Instruction 6025.17, Military Health System Patient Safety Program, 16 August 2001 2. MEDCOM Regulation 40-41, The Patient Safety Program, 14 January 2002 2.0 DESCRIPTION The US Army Medical Command requires an information management system whose components support the business processes of the MEDCOM, PSC. The purpose of the system is to capture, aggregate, analyze and report Patient Safety Program data from thirty-seven, worldwide Medical Treatment Facilities (MTF?s) and their associated clinics. The system shall be capable of importing identified data from each MTF into a central database for analysis and reporting. The data that is captured in the central database will be aggregated data or program specific data and not single incident specific data. The system shall import data from either Microsoft Access, Microsoft Excel, comma delimited files, etc. It shall provide the capability to perform analysis of the aggregate data in the centralized database in a standardized report format. Additionally it will provide for long-term storage and provide a centralized record retrieval process. The system shall have the capability for the MEDCOM, PSC to transmit information either up or down its reporting chain such as to the MEDCOM senior staff, to the Army Regional Medical Commands, to the Armed Forces Institute of Pathology (AFIP), Patient Safety Center and/or to the local MTF Commanders. 3.0 FUNCTIONAL REQUIREMENTS This section enumerates the high-level functional requirements of the system. The system will include the following major components. a. Safety Alert Tracking: Broadly communicate to the MTF?s and track safety alerts generated from various sources (for example, JCAHO, CDC, FDA, MEDCOM, AFIP, etc). Provide the ability to track the MTF?s implementation plans and their compliance related to safety alerts. b. Sentinel Event Alerts: Provide MTF personnel with the ability to easily input, track and trend sentinel event data. Include the ability to transmit sentinel event data to JCAHO and the MEDCOM, PSC. c. Patient Safety Program Implementation Plan: Provide a capability that will track and trend Patient Safety Program level activities at each MTF following a standardized MEDCOM, PSC format. d. Patient Safety Program Progress Report: Provide for the ability to generate a recurring, consolidated MTF Patient Safety Program progress report to track and trend program activities from all the MTF?s. e. Incident Reporting: Import identified incident reporting data from each MTF into a centralized database. Provide for aggregated analysis of the imported data by MTF, Region and MEDCOM levels to identify trends. The MTF data for import may be stored either in Microsoft Access databases or in Microsoft Excel files. Imported data will be statistical in nature rather than patient specific. f. Healthcare Failure Mode Effect Analysis (HFMEA): Support the ability to capture the data when performing a prospective analysis following the Veterans Affairs HFMEA format. Allow for analysis of data captured with all HFMEA?s done within each MTF and across all MTF?s. g. Risk Assessments: Support the ability to conduct surveys for multiple high-risk areas. Generate a report of all captured data. Perform an analysis and display data in a graphical format or whatever format best displays the results. h. Climate/Culture Survey: Support the ability to create and administer anonymous, web-based Patient Safety Climate/Culture Surveys. Allow for update of surveys, audit and tracking of changes and analysis of data at the MTF and corporate levels. i. Aggregate Data Analysis: Support the ability to perform multiple aggregate data analyses such as analysis of medication and fall incidents, contributing causes, lessons learned, etc. Perform analysis at the MTF, Regional and MEDCOM levels. j. Safe/Best Practice: Document, communicate and track process improvement activities or identified lessons learned that could be incorporated into a safe/best practice. k. Root Cause Analysis: Allow each MTF to enter Root Cause Analysis data following the DoD format that meets JCAHO requirements. Electronically submit this data to JCAHO, MEDCOM and AFIP. Support the ability to perform corporate analysis and generate a report using graphic displays of all captured data. l. Healthcare Team Coordination: Support the ability to track MTF participation in all Med Team programs (such as, ER, L&D, OR) and or Med Team Management (MTM) training programs and monitor MTF progress in training all MTF and clinic staff in program concepts. m. JCAHO Patient Safety Goals: Support the ability to track and trend compliance to JCAHO Patient Safety goals effective January 2003. 4.0 GENERAL SYSTEM REQUIREMENTS a. The information management system must be web-based. b. The system must provide a relational database, which supports the ability to capture and store data from thirty-seven MTF?s and their associated ambulatory clinics. c. Provide for the establishment of an information portal to share information and collaborate as appropriate. d. Establish a library of resources that can be updated on a regular basis. e. Support and permit multiple levels of system access and data entry. Provide for user logins, security passwords and administrative rights with permission grants. f. Provide for standard reports and a capability to produce ad hoc reports. Perform data analysis associated with each module and create a MEDCOM level summary report of all Patient Safety Program activities. g. Allow the ability to display data graphically as well as other methods. Also, allow the ability to drill down from within a graphical display. h. Provide the flexibility to easily incorporate changes in regulatory guidelines (DoD, JCAHO, AFIP, MEDCOM). i. The bandwidth requirements for the solution shall not adversely affect communication of current mission critical systems. j. System shall serve as a collection tool for question and answer data. k. System shall comply with all applicable DoD, Army, and MEDCOM regulations and policies, such as, DII COE, JTA, HIPAA, and Section 508. l. Tracking and trending of individual medical incident data is not a priority in this system, although a plus, if available. 5.0 OTHER CONSIDERATIONS Your response and cost estimate should address the items enumerated above and it should discuss the following considerations. a. The use of commercial of-the-shelf (COTS) components b. Other software requirements such as plug-ins and support utilities c. Software license fees structure. Include fees for server software and client licenses if applicable d. Available maintenance coverage with associated fees e. Installations services and support f. Training support g. Hardware configuration requirements h. Time and schedule estimates for implementation i. Technical architecture j. Software customization policies and approach
- Place of Performance
- Address: 2050 Worth Rd Suite 26, San Antonio, Texas
- Zip Code: 78234
- Country: USA
- Zip Code: 78234
- Record
- SN00168112-W 20020918/020916213843 (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 |