6515--Cardiac (Telemetry and Bedside Monitoring) Documentation and Reporting Digital Solution for VISN 12 VA Medical Centers

Questions in Blue

Answers in red

In regards to Section B.1 Purchase Order Administration Data, Part 9 SECURITY & PRIVACY CONTROL:

All contractor employees are subject to the same level of investigation as VA employees who have access to VA Sensitive Information. The level of background investigation commensurate with the level of access needed to perform in accordance with the statement of work is: Special Agreement Check (SAC) & National Agency Check with Inquiries (NACI). This requirement is applicable to all subcontractor personnel requiring the same access.

Please define VA Sensitive Information levels for this project.

Special Agreement Check (SAC) and Tier 1 National Agency Check with Inquiries (NACI) are the levels required for this project. Pricing is defined for these levels on page 4 and 5 of the solicitation.

In regards to B.2 SOW, Part 3 Standards/Requirements:

3.1. Integration Requirements

Patient Monitoring

o Integrate to all patient monitoring systems in VISN 12 to the patient monitoring vendors current software and current version

Spacelabs Patient Monitoring is currently installed at VA Illiana Health Care System, but currently under contract for migration to GE

Does vendor need to scope both GE and Spacelabs for VA Illiana?

No, vendor only needs to scope to GE for Danville.

In regards to B.2 SOW, Part 3 3. Standards/Requirements:

3.1. Integration Requirements

Patient Monitoring

o Integrate to all patient monitoring systems in VISN 12 to the patient monitoring vendors current software and current version

Vendor must specifically highlight if additional procurements shall be needed for their integration

For example, what servers, software, and/or licensing shall be required to make the integration functional

Please confirm VA will provide virtual servers. Please confirm Microsoft Licensing OS and SQL will be provided by VA Servers.

Confirmed however the vendor shall provide documentation on server, OS, and SQL requirements to support their system within their response.

In regards to B.2 SOW, Part 3 3. Standards/Requirements:

3.1. Integration Requirements

Active Directory

o Integrate to Active Directory for single sign on in accordance with the Personal Identity Verification (PIV) Compliance Playbook see attachment AD-IWA in Section D

Solution must be Single Sign On

Single Sign On must be achieved using Integrated Windows Authentication (IWA) - see attachment AD-IWA in Section D

o FHCC Department of Defense (DOD) employees have Common Access Card (CAC) cards rather than PIV cards

Additional testing may be required to accommodate this distinction

Would VA be willing to allow for validation testing for this requirement?

VA is willing to do validation testing on all integrations, including IWA Active Directory integration for PIV Compliance. It is expected that these activities will be built into the project schedule supplied by the successful contractor.

In regards to B.2 SOW, Part 3 3. Standards/Requirements:

3.3. Clinical Functionality Requirements

Single sign on via active directory integration functional requirements:

o Roles and access shall be based on membership to active directory group

i.e.) An Active Directory (AD) group in Milwaukee named VHAMIWTeleDocUsers, and a user must be part of that group to get User Level permissions in TeleDoc solution. Similar scenario for Admin Level role.

Please confirm TeleDocUsers an AD group versus a product?

Correct TeleDocUsers is an example of an Active Directory (AD) group. The purpose of this AD group is to contain users with a basic user level of permission. We can name the AD group whatever makes sense after go live.

In regards to B.2 SOW, Part 3 3. Standards/Requirements:

3.8. Training and education

24 hours of on-premise end-user support during implementation

Please confirm total of 24 hours vs 24 consecutive hours.

During implementation (go-live), we need vendor support staff available on prem during each shift for support. Not necessarily 24 consecutive hours, but 24 total hours during go live that will cover each shift (1st, 2nd, and 3rd shift).

Is it required to provide smartphone access for waveform, event, and trended vitals visualization on hospital provided or personal smartphones?

Smartphones were not part of the requirements. If that functionality is available, please describe. Indicate whether that is included in your proposal or considered an add-on feature.

In a hypothetical scenario, they would use hospital provided cell phones that could operate on the VA network. Bring Your Own Device (BYOD) or utilization of any cloud components is out of scope and not desired.