S06 - RFQ 36C10A23Q0074 Questions and Answers Community Image Sharing Platform.xlsx
XLSX spreadsheet 13 KB Posted
- Attached to
- DA10--Request for Quote 36C10A23Q0074 Amendment 0001 Community Image Sharing Platform for VISN 15
- Solicitation number
- 36C10A23Q0074
About this file
This document contains questions and answers regarding Request for Quote 36C10A23Q0074 for a Community Image Sharing Platform for Veterans Integrated Service Network 15. The platform must be compatible with the shared Department of Defense/Department of Veterans Affairs Cerner Millennium electronic health record system. Technical references are requested demonstrating previous implementations of similar image sharing platforms, including deployment details and a technical point of contact. Proposals are due by email to Tiffany.Brown4@va.gov by the response date stated in the solicitation. Submissions must include completed security forms, a Cerner compatibility statement from the original equipment manufacturer, and technical references, and be clearly indexed across five volumes as specified in the Request for Quote.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10A23Q0074_3.docx | DOCX document | |
| S06 - Request for Quote 36C10A23Q0074 AMENDMENT 0001.pdf | ||
| S02 - Request for Quote 36C10A23Q0074 FINAL.pdf | ||
| Attachment 3 - MD ERA Network Topological Diagram Template.pptx | PPTX presentation | |
| Attachment 1 - VA Directive 6550 Appendix A.pdf | ||
| Attachment 2 - HIMSS_NEMA Standard HN 1-2013 MDS2.xlsx | XLSX spreadsheet | |
| 36C10A23Q0074_2.docx | DOCX document | |
| Attachment 4 - MD ERA Inventory Template.xlsx | XLSX spreadsheet | |
| Attachment 5 - MD ERA Ports Protocols Services Template.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Request for Quote 36C10A23Q0074 - Community Image Sharing Platform for VISN 15 | |||
| Questions and Answers | |||
| Question | Answer | ||
| 1. We would like to know if this is a brand new contract OR if there is (was) an incumbent performing these services. | |||
| If not brand new, could you please provide the current / previous contract number? | 1. This is a new requirement. There is not an incumbent. | ||
| 2. Could you please provide information on the exact Cerner EHR system that VISN is using? For | |||
| example, Cerner has various EHR offerings such as Millennium, CommunityWorks, Power Chart, etc. | 2. VA will use the shared DOD/VA Cerner Millennium EHRM instance. VISN 15 is seeking a platform compatible with that system. | ||
| 3. In the RFQ section 1.8 ‘Technical Experience’ #4 and #7 mention needing “technical references”. Could |
you please clarify what the government would like to see as a technical reference? Would that mean you’d like the Contractor to simply include/point out previous technical implementations for that feature,
| or do you mean you’d like someone to vouch and attest to the capability of having built that feature? | 3. VISN 15 is requesting documentation outlining deployments of the proposed platform in similar instances/use cases. We would like to see the technical details of deployment (I.E. number of sites on the instance, usage volume, etc.) and be provided a technical POC who can comment on the system's usage by the organization. | |
| 4. Page 31 of S02 RFQ says “System shall be configured so that data sent between VA Community |
Partners and the VA is sent through a secure conduit using a Federal Information Processing Standards (FIPS) 140-2 validated connection with the data is not stored or processed in a cloud or hosted environment.”
a. The word “with” appears to be a typo. Could you please clarify what it’s intending to say? 4. The statement should read:
“System shall be configured so that data sent between VA Community Partners and the VA is sent through a secure conduit using a Federal Information Processing Standards (FIPS) 140-2 validated connection where the data is not stored or processed in a cloud or hosted environment.”
5. Offerors are encouraged to register for the Vendor Portal in order to ensure timely transmission of their proposals to the Government. WARNING: Please do not wait until the last minute to submit your proposals! Late proposals will not be accepted for evaluation. To avoid submission of late proposals, we recommend the transmission of your proposal file 24 hours prior to the required proposal due date and time.
| We are registered in Sam.gov. Is there another different Vendor Portal link that we need to register with and submit our proposal.zip file to? | 5. All offerors must be registered in www.SAM.gov prior to submitting a quote in response to this Request for Quote. There are no additional vendor portals that offerors must be registered with. All quotes must be submitted via e-mail to Tiffany.Brown4@va.gov by the response due date and time stated in the Request for Quote. | |
| NOTE TO ALL OFFERORS: All responses shall be submitted in accordance with the Request for Quote section E.1 , Instructions to Offerors - Quote Submissions. Five (5) volumes are required in your submission, as identified in section E.1. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. Proposal page limitations are applicable to this procurement. The following documents shall be submitted with Volume I: 1) All five (5) completed security form attachments; 2) A Cerner compatibility statement from the Original Equipment Manufacturer (OEM) for the equipment that you are proposing to VISN 15; and 3) Technical References. Please see section E.1 for detailed information on the submission requirements for the five (5) volumes, five (5) security forms, Cerner compatibility statement and technical references. |
File details come from the government source that posted it. Updated .