36C26321Q0031 0002.docx

DOCX document 22 KB Posted

Attached to
7030--VISN 23-Pharmacy Antimicrobial Surveillance Software
Solicitation number
36C26321Q0031
Issued by

View the file

Other files

File Type Posted
36C26321Q0031 0001.docx DOCX document
36C26321Q0031.docx DOCX document

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

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) 10-26-2020 None Department of Veterans Affairs

NETWORK 23 CONTRACTING OFFICE

Contract Officer 4801 Veterans Drive St. Cloud

MN

56303 Same as Issued By

To all Offerors/Bidders

36C26321Q0031 10-19-2020

X X X

To be cited on delivery orders.

X one This amendment is to address the following:

1. Address questions asked by contractors, see attached responses.

2. All other terms and conditions remain unchanged.

The closing date/time is still 10/30/2020 at 10:00 AM Central Time.

Andrea Harter Contracting Officer

Solicitation 36C26321Q0031 questions

Many of the Salient Characteristics are written without specific requirements and/or can be read as reference to features/functions/terms specific for Theradoc, could you expand with specific requirements and/or use cases needed by VISN 23 users?

As this question does not call into any specific requirements, it is impossible to address each item in the Statement of Work/Salient Characteristics.

Can you provide a metric for determining “Large, Medium and Small” hospitals as referenced in the Item Information table?

The sizes reference the brand name product, and the brand name is broken out by hospital size, as indicated below, a response in a different format from the Price/Cost Schedule is acceptable.

Location
Complexity
Sta5a
Black Hills
2-Medium Complexity
568
Des Moines
1c-High Complexity
636A6
Fargo
2-Medium Complexity
437
Iowa City
1c-High Complexity
636A8
Minneapolis
1a-High Complexity
618
Omaha
1b-High Complexity
636
Sioux Falls
2-Medium Complexity
438
St. Cloud
3-Low Complexity
656

Will pricing submitted in a different format than the Item Information table be acceptable?

Yes.

In Section B.3, the first paragraph - “Each facility requires a unique instance of the software to interface with each facility’s electronic health record (CPRS)”. Is the requirement here to have separate installations and servers for each facility? Would a single installation that can interface with all VistA data, reduce the need for servers, and provide a uniform VISN level view for management in addition to providing all required functionalities be acceptable?

To our knowledge each facility will require a unique instance, as stated in the Statement of Work. If it is possible to provide accurate data with a single interface with all VistA systems, then that will be acceptable.

Is access via web browser only necessary for the Minneapolis VA as stated under Requirements?

This was an error, “The interface must be able to be accessed through a web browser for easier access across each VISN 23 facility”

Regarding the need for Radiology data, can you describe the specific requirements and/or use cases for which that data would be used?

This would be significant for Radiology Reports, an example would be a chest x-ray report-significant findings for case review to determine VAE/IVAC/VAP.

Under what context would the “Problem List” be used? Can you describe the requirement and how it would be utilized?

This would be used as a quick review to assess patient’s overall health (e.g. diabetes, immunocompromising conditions etc.).

Are “Allergy clarification” and “notification of Outpatient Medication Refills, Renewals and Dose optimization” related? If so, how? Can you provide a more specific requirement for this?

The Allergy clarification is a standard data point for any medication process.

For “Medication Reconciliation”, is the requirement simply a matter of documentation that reconciliation has been done (workload tracking), or is there another specific need?

All active medication orders need to be displayed for the user to be able to assess for duplication of therapy etc. Medication reconciliation documentation is not a required element of the system.

Please define “flag” as well as “identifier”. What are the requirements for “flags”, and how would they be used (e.g. to trigger workflows or actions automatically)?

The system must be able to flag/alert the provider or user to specific predefined criteria and identify what the flag/alert pertains to (e.g. drug-bug mismatch).

Regarding “Enhance therapy for difficult-to-treat pathogens”, can you define “enhance” or provide specific use cases?

An example of which is the ability to identify multi drug resistant infections for review.

Can virtual servers be provided by VA OIT or is the preference or expectation for vendors to provide the hardware?

This depends on the VA capabilities, the contractor’s requirements and how the software interfaces with VA systems.

What value would VISN 23 place on having 3-5 years of historical data for all facilities, and the VISN, available at Go-Live for trending of antibiotic resistance or for lookback investigations for infection prevention (drug recalls or contaminated devices, for example)?

Please refer to FAR 52.212-2 as this states the evaluation criteria for this solicitation.

How would VISN 23 prioritize a Go-Live in 90 days or less vs. the typical implementation timeline of 6+ months?

Please refer to FAR 52.212-2 as this states the evaluation criteria for this solicitation.

For patients treated at multiple facilities in the VISN, how valuable is the ability to see data collected at multiple VA facilities for each patient?

Please refer to FAR 52.212-2 as this states the evaluation criteria for this solicitation.

How would VISN 23 value the ability to include data from additional sources (i.e. PeriOp CIS/ARK software) to enable the VA hospitals and the VISN to:

-monitor and track the incidence of VAP for analysis against NHSN criteria?

-monitor and track compliance of prevention bundles for CAUTI and CLABSI?

-automate IPEC reporting?

-monitor and track surgical antibiotic prophylaxis practices vs. recommendations?

Please refer to FAR 52.212-2 as this states the evaluation criteria for this solicitation.

Will the deadline be extended should the VISN not be able to respond to these questions in a timely manner that allows for updating proposals accordingly?

If the deadline is extended, it will be extended by an amendment to solicitation on the Contract Opportunities portion of beta.SAM.gov

In order to determine required resources, what are the implementation goals and timelines to kick-off and go live per site?

The goal is to have this software up and running as soon as possible due to the intended usage to aid in the VA’s effort to combat COVID-19.

When is the Cerner conversion date per site? This info will assist in understanding post host conversion requirements.

This is still being determined

Can we be provided most recent and accurate bed counts per site?

There are 8 facilities in VISN23 with the above listed complexity levels.

Can the number of software end-users per facility be confirmed?

The usage of the system will be maximized but will be restricted to those who have been designated (e.g. antimicrobial stewardship, infection prevention, anticoagulation).

Will access be granted to the VA Enterprise Cloud?

No. There should not be a need for VA to provide this. Contractor will only have access to their own server. It will be up to the contractor to obtain access/clearance/background checks to VA servers.

Can separate instances all live in one central location or is a “data center” in each separate location required?

Yes, as long as contractor can provide accurate data, the data center may have one central location.

If we are setting up individual instances, will there be a separate tech lead for each site or will the VISN IT lead be facilitating each implementation instance?

There will be a centralized IT lead (COTS IT) for all VISN23 sites.

If the expectation is separate instances, is there an expectation as to implementation timeline and prioritization of sites?

This is up to the contractor to determine and should be submitted as part of proposal.

Can the government provide the technical reference model?

The TRM technical reference model is provided by the vendor to get their software approved by VA. CPRS/VistA technical manuals are publicly available.

Are outpatient patient records using the same VISTA instance?

Yes

Consistent with FAR requirements and GAO precedents, will the government be providing offerors a “reasonable” time to prepare a quote based on answers provided to the questions asked?”

This is commercial item for which contracting officer may allow fewer than 30 days response time IAW FAR Part 12.205. As it is the government’s intent to utilize this software in their response to the COVID-19 epidemic this shortened timeline is appropriate.

File details come from the government source that posted it. Updated .