36C26020Q0765 0001.docx

36C26020Q0765 0001 Continuation Page

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) 08-24-2020 101-20-4-6010-0163 none 36C260 Department of Veterans Affairs Network Contracting Office 20 8524 N. Wall St.

Spokane

WA

99208

To all Offerors/Bidders

36C26020Q0765 08-18-2020

X x x

The purpose of this modification is to answer submitted questions.

See continuation page.

A signed copy of this modification must be returned with your offer submission in order to be considered.

The due date/time is NOT extended.

Karen Rhodes Contracting Officer

VA-VHA-RPOW-2019-82DDA0AA

The following questions and answers are submitted for this solicitation:

Q1. Number of pumps at each location?

Government Answer: Portland: 2; Seattle: 2; American Lake: 1

Q2. Number of users, named not concurrent?

Government Answer: Portland: 12; Seattle: 12; American Lake: 6

Q3. Will they be sending out claims to Medicaid and or Medicare?

Government answer: No for all locations.

Q4. Information, fields, that will be sent to Cerner?

Government Answer: See attached DFT HLY transaction information.

Q5. Will this run on their servers or on a commercial cloud?

Government Answer: No, this will be on VA internal servers.

Q6. Will all EHR functions outside of dispensing reside with Cerner?

Government Answer: Yes, all patient care functions, ordering patient medication does, documenting administration of that dose will reside in Cerner.

Q7. The number of pumps?

Government Answer: 5, see Q1 above.

Q8. The Manufacturer & model number of pumps?

Government Answer: Portland: IVEK Accu Vert Dispenser (Accu 132315-Revk); Puget Sound/American Lake: SciLog M-3400-P-1308917-134538.

Q9. Your current workflow process, if possible.

Government Answer: No existing integration; manual data entry at all locations.

Q10. How many licensed users does the Govt anticipate?

Government Answer: 30 total

Q11. Virtual and on-premise servers are mentioned in the PWS. Is the vendor solution being proposed permitted to be a cloud based HL7 approved software that integrates with the CERNER OpenLink API and meets FedRAMP and other HIPAA regulations?

Government Answer: VA intends to provide a virtual server on which the software can be run; a cloud solution is not requested.

Q12. Is the Netsmart AMS system going away?

Government Answer: The proposed solution would replace the Netsmart AMS system.

Interface Operation: Send DFT Data to Cerner EHR (OmniCenter Only) Interface Operation Overview The DFT message describes a financial transaction that is sent to a billing system and is used for patient accounting purposes Interface Operation Transaction.

DFT messages OmniCenter Only Interface Operation Transactions The following table outlines the transactions that comprise this interface operation.

Transaction Step

Charge messages

Table 56 – DIV-1/2/3: Data Models – Send DFT Data Transactions The following sequence diagram illustrates the message flow for this interface operation.

Figure 11 – Send DFT Data Sequence Diagram Send DFT Data to Cerner EHR Details Outbound Message Type Details: HL7 V2.3 DFT Message Message Structure:

Table 57 – DIV-1/2/3: Data Models – HL7 DFT Transaction Segment Definition Segments surrounded by “[ ]” are optional to the transaction.

Segments surrounded by “{ }” may repeat individually or within the indicated grouping.

Message Details:

Fields for each segment are defined below. The description for each column can be found in Section 4.1.4. Descriptions for each data type listed can be found in Section 4.1.5.

The title of each segment indicates the three-letter HL7 segment identifier, the segment description, whether it is required or optional, and whether it may repeat on its own or as part of a repeating group.

Fields that are not used are grayed out.

MSH – Message Header Segment – Required – No repeat Seq

Type

Optional Comments

Receiving Facility

CERNER

Security

9.1

9.2

e.g., Q5745747372372727233

Table 58 – DIV-1/2/3: Data Models – HL7 DFT Transaction MSH Segment Definition PID – Patient Identification Segment – Required – No repeat

External Patient ID

3.2

Check Digit

3.3

Check Digit Scheme

3.4

Alternate Patient ID

5.1

5.2

Mother’s Maiden Name

Patient Alias

Race

Patient Address

Country Code

Patient Phone Number

Business Phone Number

Primary Language

Marital Status

Religion

Table 59 – DIV-1/2/3: Data Models – HL7 DFT Transaction PID Segment Definition PV1 Patient Visit Segment – Required – may repeat

Table 60 – DIV-1/2/3: Data Models – HL7 DFT Transaction PV1 Segment Definition FT1 - Detail Charge Segment – Required – may repeat

Transaction Batch ID

7.1

ST

7.2

ST

7.3

STG

7.4

Alt Code

7.5

Alt Description

7.6

Alt Coding System

Transaction Description

Transaction Amount - Extended

11.1

Price

11.2

Price Type

11.3

From Value

11.4

To Value

11.5

Range Units

11.6

Range Type

Transaction Amount - Unit

12.1

Price

12.2

Price Type

12.3

From Value

12.4

To Value

12.5

Range Units

12.6

Range Type

Department Code

Insurance Plan ID

Insurance Amount

Assigned Patient Location

16.1

Point of Care

16.2

Room

16.3

Bed

16.4

Facility ID

16.5

Location Status

16.6

Patient Location Type

16.7

Building

16.8

Floor

Fee Schedule

Patient Type

Diagnosis Code

19.1

Identifier

19.2

Description

19.3

Name of Coding System

19.4

Alternate Identifier

19.5

Alternate Description

19.6

Alternate Coding System

Ordered By Code

Table 61 – DIV-1/2/3: Data Models – HL7 DFT Transaction FT1 Segment Definition ZPM- Pocket Activity - Required – No Repeat

Witness ID

Witness name

Alt item id

Alt item ID2

Nursing unit

Table 62 – DIV-1/2/3: Data Models – HL7 DFT Transaction FT1 Segment Definition Message Examples:

MSH|^~\&|VAPHARMIP|668|CERNER|CERNER|20200415091318|SECURE|DFT^P03|RXC-0001474749|P|2.3

PID|||1706496000001||ZZTEST^BRIDGESIX||19800909|M||||||||||1720972

PV1||I|668 5 ICU

FT1|1|3898691||20200415082946|20200415091318|V|14038675||375808615|1||||||||||Miller^Sean(omnicell) ZPM|C|OMNIRX|668-VSRXTEST||65533|14038675|Lisinopril|6|||1|DUCK|Lname, Fname(omnicell)|||8.00||||668 5 ICU||0||20200415082946 image1.jpeg