Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF DECEMBER 06, 2014 FBO #4760
DOCUMENT

70 -- NEW ACTION: RTLS Patient Elopement and Wandering Pilot - Attachment

Notice Date

12/4/2014
 

Notice Type

Attachment
 

NAICS

541512 — Computer Systems Design Services
 

Contracting Office

Department of Veterans Affairs;Office of Acquisition Operations;Technology Acquisition Center - Austin;1701 Directors Blvd, Suite 600;Austin TX 78744
 

ZIP Code

78744
 

Solicitation Number

VA118A15N0031
 

Response Due

12/29/2014
 

Archive Date

1/13/2015
 

Point of Contact

Reuben A Zepeda
 

E-Mail Address

1-4467<br
 

Small Business Set-Aside

N/A
 

Description

Real Time Location System (RTLS) Patient Elopement and Wandering (PEW) Request for information (RFI) December 4, 2015 This is a RFI only. The purpose of this RFI is to determine sources capable of providing a RTLS-based Patient Elopement and Wandering (PEW) solution and services in accordance with the attached Requirements Specification Document (RSD) (reference Appendix A). This RFI is for planning purposes only and shall not be considered an Invitation for Bids, Request for Task Execution Plan, Request for Quotation or a Request for Proposal. In accordance with Federal Acquisition Regulation (FAR) 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Additionally, there is no obligation on the part of the Government to acquire any products or services described in this RFI nor does it restrict the Government as to the ultimate acquisition approach. Respondents will not be entitled to payment for direct or indirect costs that are incurred in responding to this RFI. The information provided may be used by the VA in developing its acquisition strategy and Performance Work Statement. Interested parties are responsible for adequately marking proprietary, restricted or competition sensitive information contained in their response. The contract period of performance is undetermined at this time. An award is forecasted during the 3rd or 4th quarters of fiscal year 2015. The Government is seeking industry feedback. Please respond with any questions or concerns regarding the attached RSD to enable the Government to consider and or implement industry best practices and procedures. The responses to this RFI may be used to better define the Government's final requirement. 1.BACKGROUND RTLS is an umbrella term that includes multiple technologies for locating and tracking items. It includes Wi-Fi based location finding, active and passive Radio Frequency Identification (RFID), and a number of other location technologies, including low frequency and infrared. Within VA, the RTLS refers to a collection of applications, including Asset Tracking, automated Temperature Monitoring, Cardiac catheterization lab supply monitoring, sterile processing workflow, and surgical instrument tracking, loosely integrated with Intelligent InSites. In addition, VA is evaluating options to expand RTLS to include automated tracking of Hand Hygiene compliance, prevention of Patient Elopement and Wandering, and applications for Emergency Room and Operating Room Workflow. The potential uses and benefits of this technology throughout VA are significant, and include improvement of quality of patient care, improved patient satisfaction, reduction of health care asset management costs, improvement of capacity/resource planning, improvement of employee and patient safety, as well as improvement of general asset management and inventory. The Government is seeking capability statements that include a brief analysis of each of the requirements within the RSD. The analysis shall provide a comparison to the functional and technical capabilities of the proposed solution. The responses shall identify which RSD requirements are met with existing capabilities and which requirements would require custom development in order to achieve the performance requirement. The following scope of work is to provide interested sources a level of context to what will be pursued after the RFI process. Government is seeking sources to design, install, configure, and test an RTLS-based PEW solution. The solution shall be designed to meet the needs of a specific VA Facility (To Be Determined) based on their current PEW business. The services shall include project management to oversee the implementation of the RTLS-based PEW solution and the delivery of associated training services for the selected VA Facility. The solution shall include hardware and software components that fulfill the VA-approved design. This effort may require services to conduct site surveys, update facility drawings and system configuration documentation for the PEW solutions. Additionally, transition services will be required during the end of any resultant contract. 2.PATIENT ELOPEMENT AND WANDERING USE CASE VA Database Interfaces Required "VISTA - Patient File "VISTA - CPRS Technology Considerations "Software oSolution must integrate with Intelligent Insites "Hardware oActive tagging "Solution must integrate with existing Centrak wireless sensing infrastructure "Solution must work with Centrak staff badges oExisting Honeywell Notifier Alarm system System Functionality "Room level coverage "Egress protection so that doors lock when there is an elopement risk "Egress coverage for elopement notification "Active play back modes for retracing patient movement and interactions The goal of the elopement system is mission critical to patient safety and should provide a fault tolerant design with minimal latency requirements. Delays beyond 2-3 seconds for communication and alarming within the system and to external sources are maximum requirement. The elopement system should have the flexibility to have rules based on individual patients to freely move within the boundaries set for them. System integration with elevators, door locks, and security cameras should be patient specific and provide a fault tolerant design promoting patient safety. As patients approach doors or elevators an escalating system of alerts and security measures should prevent elopement including disabling of elevators and locking of doors; escalation should be transparent to the patient. Again the goal of the elopement system should allow configuration of permissions to be patient specific and provide freedom of movement within specified boundaries while maintaining a fault tolerant design and promoting the safety of the patient. High level requirements - please see the RSD for further details 1.The system shall allow users the capability to run reports that show events indicating frequency of patient elopement. 2.The system shall allow users to be able run reports that identify the location prior to patient elopement. 3.The system shall provide active play back modes for retracing patient movement and interactions. 4.The system shall allow users the capability to run reports to identify sites prior to most frequent and least frequent patient elopement. 5.The system shall allow hospital staff to generate reports identifying the number of eloped patients stopped because of the RTLS device outside their designated area but still in the safety of the building. Reports shall include at a minimum, patient id, location, staff, distance from designated area, total time of elopement. 6.The system shall allow hospital staff to generate reports identify the number of eloped patients stopped because of the RTLS device outside their designated area but still on the hospital grounds. Reports shall include at a minimum, patient id, location, staff, distance from designated are, root cause of elopement, total time of elopement, locations eloped patient entered (e.g. male patient in female patient room). 7.The system shall allow hospital staff to generate reports identify the number of eloped patients making it outside the facility or its grounds. Reports shall include at a minimum, patient id, location staff, distance from designated are, root cause of elopement, total time of elopement. 8.The system shall allow hospital staff to generate reports identifying the number of eloped patients injured as a result of an elopement. Reports shall include at a minimum, patient id, location staff, distance from designated are, root cause of elopement, elopement injuries, and total time of elopement. 9.The system shall allow hospital staff to generate reports identifying the number of eloped patients dying as a result of an elopement. Reports shall include at a minimum, patient id, location, staff, distance from designated are, root cause of elopement, elopement cause of death, and total time of elopement. 10.The system shall be capable of generating reports quantify the number alarms, warning, alerts generated by the system and categorizing them (e.g. nurse response, police called). 11.The system shall allow hospital staff to generate reports providing a Pareto chart of the causes of elopements. 3.SAMPLE MEDICAL CENTER "Quantity of reusable patient tags = 40 "Quantity of doors that need to have locking mechanisms controlled by RTLS = 31 "Quantity of elevators that need to have locking mechanisms controlled by RTLS = 0 "Quantity of choke points controlled by RTLS = 34 "Number of in person training sessions required = 10 "Period of performance = 12 months "Place of performance = Palo Alto, CA 4.RESPONSES REQUESTED In addition to the aforementioned response requirement, Please address the following questions in your capability statement: 1.Name of Company: a.DUNS Number: b.Address: c.Point of Contact: d.Phone Number: e.Fax Numbers: f.Email Address: g.Any applicable schedules or existing Federal contracts (General Services Administration (GSA), Mission Oriented Business Integrated Services (MOBIS), Veterans Technology Services (VETS) Government wide Acquisition Contract (GWAC), etc.) 2.Could your company independently provide the entire range of services required to implement the requirements called for in the RSD? ____ YES ____ NO a.If you answered NO to question (2), what requirements or services called for in the RSD could your company provide? 3.Does your company plan to be the prime contractor or subcontractor for this effort? 4.Please provide details regarding proposed joint ventures, teaming arrangements, strategic alliances or other business arrangements to satisfy requirements of the entire PWS. Small businesses are encouraged to identify teams whereby each team member is considered small business based upon the proposed North American Industrial Classification System (NAICS) code of 541512. 5.Is your company currently providing similar services to another Government agency or other non-Government customer? If so, please identify the agency or non-Government customer. If you are unwilling to share your customers' identity, please address whether your company offers the same or similar services commercially (outside the Federal Government). 6.Please identify your company's Small Business size status based upon the applicable (NAICS) code of 541512. For more information, refer to http://www.sba.gov/. 7.Please provide positive or negative feedback regarding the RSD such as recommended changes, noted exceptions, ambiguities, etc. 8.Provide any other pertinent information as deemed necessary to demonstrate your and any proposed team member's capabilities and prior experience as it relates to the requirements set forth in the PWS. 9.Is your firm currently registered in VA's Vendor Information Pages (VIP) database? Yes ____ No ____ 10.Describe the capabilities/qualifications/skills your company possesses to perform the work, to include but not limited to the following: a.Description of your experience deploying RTLS-based PEW solutions in dementia and psychiatric wards. b.Description of your experience developing business rules for RTLS-based PEW solutions. c.Description of your knowledgeable of software development lifecycle stages. d.Description of your knowledgeable of HIT standards and references. e.Description of your experience using and integrating RTLS-based PEW solutions with Intelligent InSites software f.Description of your experience providing solutions that are compliant with health information technology safety guidelines and best practices g.Description of your experience with developing functionality for the RTLS-based PEW solutions. h.Description of your RTLS-based PEW solution - system description, types of hardware, system requirements, configuration requirements, standard functionality, and all available functionality. i.Description of available RTLS-based PEW solution. j.Describe your experience with VA security and privacy policies and requirements? k.Describe how your RTLS-based PEW solution can be integrated with other systems i.VistA Patient File ii.Alarm systems l.Description of integration efforts, timeframes, dependencies, outcomes, working with other stakeholders and vendors. m.Describe your experience with installing and maintaining RTLS-based PEW solution in a nationwide, hospital health system. n.Describe your experience with RTLS-based PEW solution performance measures and monitoring o.Describe your experience and capability to rapidly deploy RTLS-based PEW solution in a nationwide, hospital health system. p.Describe your support structure for RTLS-based PEW solution in a nationwide, hospital health system. 11.Please provide a Rough Order of Magnitude (ROM) cost estimate based on Sections 2 and 3 above, PATIENT ELOPEMENT AND WANDERING USE CASE and SAMPLE MEDICAL CENTER. 5.SUBMITTAL INFORMATION Interested sources are encouraged to initiate advance contact with contract specialist Reuben A. Zepeda, via phone at 512-981-4467, or by email at reuben.zepeda@va.gov Responses to questions one through seven shall be limited to a total of 20 pages. There is no page limitation for the capability statement that includes comments on bullets contained in the RSD. Submit questions in writing to reuben.zepeda@va.gov by December 17, 2014. Final responses are due by December 29, 2014. Please submit responses via email to reuben.zepeda@va.gov All responsible sources may submit a response which shall be considered by the agency. End Document
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/notices/d4ce62512b0053022b1ee585f441c304)
 

Document(s)

Attachment
 

File Name: VA118A-15-N-0031 VA118A-15-N-0031.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1757756&FileName=VA118A-15-N-0031-000.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1757756&FileName=VA118A-15-N-0031-000.docx

 

File Name: VA118A-15-N-0031 PEW PWS RSD Appendix A 2014Nov24.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1757758&FileName=VA118A-15-N-0031-001.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=1757758&FileName=VA118A-15-N-0031-001.docx

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN03587297-W 20141206/141204234714-d4ce62512b0053022b1ee585f441c304 (fbodaily.com)
 

Source

FedBizOpps Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |