Attachment 3: VA DIRECTIVE 6550 V3 - Appendix A Fillable 1
Updated
A PDF document (273 KB) attached to Radiology and Cardiology Foundational Enterprise Imaging System, from the Department of Veterans Affairs. Due Dec 9, 2026, 10:00 AM (UTC-5).
File name: Attachment 3 20190620_VA DIRECTIVE 6550 V3 - Appendix A_Fillable 1.pdf
The full file is for paid members, or buy this bid alone.
Preview
VA DIRECTIVE 6550 Appendix A – To be completed for all procurements of network-connected medical devices and non-network-connected medical devices that store sensitive information. For client/server systems, a separate 6550 Appendix A is required for each the client and the medical server. 1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12
1.13
Equipment Category (VA-MDNS)
Manufacturer
Model
Application Name and Software Version #
Requesting Service
VISN
Facility Name
Facility Number
Manufacturer Point of Contact
Phone Number
E-mail address
Biomedical Engineering Point of Contact
Phone Number
E-mail address
Responsible Service if Biomedical Engineering is NOT the Primary System Manager for system maintenance, support and lifecycle management
Medical Device Type
Equipment Description (i.e. equipment function and systems it communicates with)
☐ Discrete device ☐ Software
☐ Client
☐ Application server
1.14
1.15
1.16
MDIA VLAN Number for installation (if known)
Installation Location (Room, Building, Division)
Is there an existing Enterprise Risk Analysis (ERA) for this ☐ Yes
☐ No
device/system?
If yes, what is the ERA number?
**Note that the ERA must be for the same make, model, and application software version to apply to the requested system. A new ERA is required for major software or operating system updates (e.g. version 2.0 to 3.0) but is not required for minor updates (e.g. version 2.0 to version 2.1). If an ERA exists for the requested system, completion of the 6550 Appendix A is not required beyond this point. Please sign to certify that an existing ERA is available for the requested system and forward the document to either the Area Manager or ISSO for signature, as appropriate.
2.1
Device Operating System (OS)
Can the OS be automatically patched?
☐ Yes
☐ No
**Note that systems that do not support automated patching via the VHA MD Update Server or via vendor channels impose a significantly higher risk to the VA network.
If patching is not automated, what is the patching process and/or limitations?
Procurement of systems with unsupported operating systems is prohibited. Unsupported operating systems are OSs that are not supported by the manufacturer and have reached the end of the OS lifecycle as published by the OS manufacturer (i.e. no further security patches will be released for the OS by the manufacturer after the OS end-of-life nor will be available by
The beginning of the document. Download the full file to read on.