Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF JUNE 02, 2017 FBO #5670
DOCUMENT

54 -- OR Management System Response to vendor questions - Attachment

Notice Date

5/31/2017
 

Notice Type

Attachment
 

NAICS

541519 — Other Computer Related Services
 

Contracting Office

Department of Veterans Affairs;Network Contracting Office 6;100 Emancipation Drive;Hampton VA 23667
 

ZIP Code

23667
 

Solicitation Number

VA24617Q0806
 

Response Due

6/7/2017
 

Archive Date

7/7/2017
 

Point of Contact

Audrey Wooten
 

E-Mail Address

audrey.wooten@va.gov
(audrey.wooten@va.gov)
 

Small Business Set-Aside

Service-Disabled Veteran-Owned Small Business
 

Description

The purpose of this Amendment is to give the response to the question received and to extend the response date to 06/7/2017 for RFQ VA246-17-Q-0806 Combined Solicitation. All bid of RFQ shall be email to Audrey.wooten@va.gov by 2pm 6/6/2017. Response to questions Does the solution have to be FISMA compliant? Answer: Yes Does the solution have to be cleared by VA Software Assurance Team for source code scanning using Fortify? Answer: Unable to provide at this time. Does VA require source code to be submitted for security clearance for this project? Answers: No Does the solution have to be cleared by Nessus scans? Answer: Unable to provide at this time Does the solution have to be part of VA Risk Vision system and have an approved ATO? Answer: Unknown at this time. Will VA provide the interface for read and write to VistA using VistA exchange or directly to VistA? As far as it is known yes Will VA provide the interface to ARK using HL7 or proprietary Philips interface to Compurecord? Answer: HL7 Does the SAFE Software License brand name or equal need to be OI&T TRM Approved? Answer: yes Does the SAFE Application brand name or equal need to be OI&T TRM Approved? Answer: yes Does the Real View Software License brand name or equal need to be OI&T TRM Approved? Answer: yes Does the Real View Command Center Software License brand name or equal need to be OI&T TRM Approved? Answer: yes Does the Real View Command Center Software brand name or equal need to be OI&T TRM Approved? Answer: yes Does the Sonitor RTLS Software Engine License brand name or equal need to be OI&T TRM Approved? Answers: yes Will the Sonitor RTLS Software Engine License brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC? Answers: N/A Does the Sonitor Wireless Patient CareTag S-Tag G2 brand name or equal need to be OI&T TRM Approved? Answers: yes Will the Sonitor Wireless Patient CareTag S-Tag G2 brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC? Answers: N/A Does the Sonitor HDR Wireless Gateway Receiver (REC-A150) brand name or equal need to be OI&T TRM Approved? Answers: yes Will the Sonitor HDR Wireless Gateway Receiver (REC-A150) brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC? Answers: N/A Does the Dell Small Form Factor PC brand name or equal need to be OI&T TRM Approved? Answers: no Does the IP Camera for each OR brand name or equal need to be OI&T TRM Approved? Answers: no If all of the commercial items do not need to be OI&T TRM Approved, will the Salisbury VA medical center be securing waivers to use the commercial items requested? Answers: no Does the VA require successful completion of VistA integration testing in the VA SandBox and EHMP programs for HL7 interfaces? Answers: yes Will the VA be providing VistA interface hostnames and port designations? Answers: yes Can you provide the brand name for CLIN 0016? Answers: Sonitor Is CLIN 0026 a requirement? Answers: yes Can a brand name or equal solution leverage the existing VA wireless network? Answers: no Is the Physician mobile app described in the Scope required to be OI&T TRM approved? Answers: yes Is the Physician mobile app described in the Scope required to be MASA scanned? Answers unknown Is the Physician mobile app described in the Scope required to be approved by VHA software assurance team after source code scanning by Fortify? Answers: unknown What mobile devices will the Physician mobile app described in the Scope run on? Answers: Android and Iphone How many mobile devices will the Physician mobile app run on? Answers: approximately 50 Will the VA be providing the mobile devices running the Physician mobile application? Answer: no Will the mobile devices running the Physician mobile app be FIPS 140-2 certified? Answers: If pt. info is included Will the mobile devices running the Physician mobile app be OI&T MASA scanned, fortify scanned and OI&T TRM approved? Answer: TRM Will the mobile devices running the Physician mobile app be on the VA wireless network? Answer: no Is the OR charge mobile tablet described in the Scope required to be OI&T TRM approved, OI&T MASA scanned, VHA Software Assurance Fortify scanned? Answer: unknown What is manufacture and model will the OR charge mobile tablet described in the Scope? Answer: Vendor to provide How many OR charge mobile tablets are required? Answer: approximately 1 Will the OR charge mobile tablet be FIPS 140-2 certified, Answer: yes Will the OR charge mobile tablet be OI&T MASA scanned, VHA Software Assurance Fortify scanned and OI&T TRM approved? Answers: TRM Will the OR charge mobile tablet be on the VA wireless network? Answer: yes Will the bedside PCs described in Scope 2.0 be VA issued PCs? Answer: yes Does Instant web-based visibility at bedside PC require PIV compatibility? yes Is there a requirement for staff to authenticate to the system when using Instant web-based visibility at bedside PC? Answers: yes Can the Pre/Post Op care-boards us the VA wireless network? Answer: Yes with TRM approval Who is the current integration provider referenced in #12 of the application requirements? Steris Are the HCC locations going to be leveraging this solution, or just the 7 ORs in the Salisbury VA Medical Center? Answer: This solicitation is just for SBY at this time Is the proposed solution allowed to leverage a direct integration to VistA/CPRS without leveraging a KITS package? Answer: unknown Second group of questions 1) What current OR management system is currently being used at the Salisbury VA Medical Center? none 2) In reference to the system's reporting requirements, is there a required format of these reports? i.e..pdf,.xslx,.docx, etc Answer: PDF 3) In reference to the server requirements, are the current systems requiring integration into the new OR management system SQL based? Answer: Unable to provide information 4) In reference to the server requirements the vendor is asked to provide the capability to store reports for 5 years.   Are these reports to be stored on site?   Answer: Yes Additionally the item description doesn t reference a long-term storage capability, are we to assume the VA has a storage solution in place? No Third group of questions 1) Would the government consider revising the solicitation to facilitate more than one compliant bidder and thereby allowing evaluation of a solution that, in the opinion of our team, offers a more viable and cost effective solution for the VA and delivers on the core business requirements as depicted in this solicitation? Answer: The solicitation requirement is Brand name or equal to and all vendor must meet what is required in SOW for the need of the facility. No duplication of enterprise systems (RTLS, VistA Imaging, and Anesthesia Record Keeping). Simplified interface with legacy systems reducing complexity, start-up and maintenance costs. Immediate adoption by staff through avoidance in change of clinical practices and need for retraining. Reduced project risk removing the government as responsible for a complex multi system integration. 2) Can the government clarify requirement under Section "3.0 Technical Requirements", "a. Application Requirement", Answer: Must be compatible with the current integration provider at the Salisbury location and both HCC locations." Answer: Steris integration 3) Can the government clarify requirement under Section "3.0 Technical Requirements", "F. Analytics Package configuration requirements", "ii. Configure analytic cube to host data for above reports." Answer: Configure data to provide required reports
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/VA/HaVAMC/VAMCCO80220/VA24617Q0806/listing.html)
 

Document(s)

Attachment
 

File Name: VA246-17-Q-0806 VA246-17-Q-0806_3.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3541427&FileName=VA246-17-Q-0806-003.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3541427&FileName=VA246-17-Q-0806-003.docx

 

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

Record

SN04526793-W 20170602/170531234853-069f65b71ab430d10bc7c605926aab6f (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 |