SOLICITATION NOTICE
70 -- Secure DICOM Image Sharing System
- Notice Date
- 8/4/2020 9:57:44 AM
- Notice Type
- Combined Synopsis/Solicitation
- NAICS
- 511210
— Software Publishers
- Contracting Office
- 256-NETWORK CONTRACT OFFICE 16 (36C256) RIDGELAND MS 39157 USA
- ZIP Code
- 39157
- Solicitation Number
- 36C25620Q1001
- Response Due
- 8/14/2020 1:00:00 PM
- Archive Date
- 08/24/2020
- Point of Contact
- Lakeisha White, Contracting Officer, Phone: 601-206-7046
- E-Mail Address
-
lakeisha.white@va.gov
(lakeisha.white@va.gov)
- Awardee
- null
- Description
- 5. PROJECT NUMBER (if applicable) CODE 7. ADMINISTERED BY 2. AMENDMENT/MODIFICATION NUMBER CODE 6. ISSUED BY 8. NAME AND ADDRESS OF CONTRACTOR 4. REQUISITION/PURCHASE REQ. NUMBER 3. EFFECTIVE DATE 9A. AMENDMENT OF SOLICITATION NUMBER 9B. DATED PAGE OF PAGES 10A. MODIFICATION OF CONTRACT/ORDER NUMBER 10B. DATED BPA NO. 1. CONTRACT ID CODE FACILITY CODE CODE Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods: The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers E. IMPORTANT: is extended, (a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended. 12. ACCOUNTING AND APPROPRIATION DATA (REV. 11/2016) is required to sign this document and return ___________ copies to the issuing office. is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A. 15C. DATE SIGNED B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b). RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified. C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF: D. OTHER Contractor 16C. DATE SIGNED 14. DESCRIPTION OF AMENDMENT/MODIFICATION 16B. UNITED STATES OF AMERICA Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect. 15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER 15B. CONTRACTOR/OFFEROR STANDARD FORM 30 PREVIOUS EDITION NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.243 (Type or print) (Type or print) (Organized by UCF section headings, including solicitation/contract subject matter where feasible.) (Number, street, county, State and ZIP Code) (If other than Item 6) (Specify type of modification and authority) (such as changes in paying office, appropriation date, etc.) (If required) (SEE ITEM 11) (SEE ITEM 13) (X) CHECK ONE 13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS, IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14. 11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT (Signature of person authorized to sign) (Signature of Contracting Officer) 1 1 0001 00586 Department of Veterans Affairs G.V. (Sonny) Montgomery VAMC 1500 E. Woodrow Wilson Dr. Jackson MS 39216 10N16 Department of Veterans Affairs G.V. (Sonny) Montgomery VAMC A&MM Service (90C) 715 South Pear Orchard Road Ridgeland MS 39157 To all Offerors/Bidders 36C25620Q1001 08-04-2020 X X X 1 AUGUST 14, 2020 3PM CST See CONTINUATION Page THE PURPOSE OF THIS AMENDMENT IS TO EXTEND THE RESPONSES DUE DATE. THE RESPONSE DATE IS HEREBY EXTENDED TO AUGUST 14, 2020 3PMCST. What is the expected scope of the interface between the image sharing solution and VistA imaging? No direct interface between the solution and VistA Imaging. Solution will be between V16 commercial PACS and community partner PACS. Images will be sent from V16 PACS to VistA Imaging for permanent record. The contract states the government will furnish all equipment for this solution. Does this include required hardware required for the software VPN endpoint gateway at the community partner locations? No. Participating community partners will have to provide their own hardware to host the VA/Contractor provided software interface. Is a VPN gateway required if the solution is capable of providing encryption for data in transit between VISN 16 centers and the community partners? Yes Question 15 The Contractor s solution shall not store or host any VA PHI or PII on its servers or in a cloud based network. Does the limitation of storing information on its (the contractors) servers include the solutions installed for the solution within the VISN 16 and community partners locations? No How many CD/DVDs are imported into PACS/VistA Imaging VISN wide annually? Estimate = 11,000 How many CD/DVDs are produced annually VISN wide and exported to outside referral sources? Estimate = 11,000 How many CD/DVDs are transported by Veterans to referral sources and back to the VA annually? Not sure if this happens at all but would be a subset of the totals given in Q5 and Q6. Would the VISN like to have reports included with all imaging studies bi-directionally, if so what format is preferred? Outside reports are not necessary Does the VISN have an eMPI that can be utilized for patient matching? Unsure if it can be utilized for this purpose Question 6 states that the contractor shall implement the system at all current and future community care partners. Please define the current and possible future community care partners by the table 1 listed sites. Each facility listed in table 1 has some number of designated and de facto community partners with which they routinely or occasionally share Veterans DICOM images. The precise number is unknown and subjectively defined, however we used 12-15 per facility for internal planning. Any or all of those partners who are willing to accept the solution will be included at no additional cost to them. In addition, any future community partner locations that are newly created or identified by any facility listed in Table 1 and who are willing to accept the solution at no cost to them are included in our consideration. Is it desired that this solution will work with the VA s new HealthShare referral management tool for community partners? Desired, not mandatory Is the VA s desire to work within the CommonWell or VHI/VLR networks? Not for this acquisition Is there are requirement to be integrated with joint legacy viewer (JLV)? No; JLV would show the images from VistA Imaging Are WADO images in the place of full DICOM image study sets were appropriate acceptable? Not sure what WADO images are. What is the VA s plan for non-DICOM images and documents? Do they need to be in native form. Unsure of question. Intended scope does not include non-DICOM images. We see a request for a quantity of 8 of the solution, which we assume is one for each of the named facilities in the RFQ. Given the software we plan to propose is based on user counts, can you please share how many people at each of the facilities would have access to the system who would need to be licensed? Estimate 3-4 per site; equal to the number of PACS Admins, ADPACS, & AO/BMs on the VA-side and an equal number per each on the partner side.
- Web Link
-
SAM.gov Permalink
(https://beta.sam.gov/opp/b20691df47c64841a897c52b84b6c2eb/view)
- Record
- SN05745096-F 20200806/200804230153 (samdaily.us)
- Source
-
SAM.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's SAM Daily Index Page |