Zoll Code Review There Was a Problem With This Installer Package

VA Technical Reference Model v 22.3

RescueNet Code Review

General
Decision
Reference
Component
Category
Assay

Technologies must be operated and maintained in accordance with Federal and Section security and privacy policies and guidelines. More information on the proper use of the TRM can exist establish on the TRM Proper Use Tab/Department.

Website:	Go to site
Clarification:	RescueNet Code Review software is designed to automate systematic quality comeback past electronically capturing and organizing resuscitation data. The product allows users to measure out and improve the reporting process past combining Utstein-style reports on cardiac arrests with Electrocardiography (ECG) and Vital-Signs data collected from defibrillators. RescueNet Code Review can likewise automate the commitment of diagnostic data, enabling remote physicians to give direction to onsite caregivers. RescueNet Code Review is available in 2 editions: Standard and Enterprise. This assessment covers both editions. RescueNet Code Review stores and opens apartment files (containing Extensible Markup Language (XML)) that are received past the server from wireless transmissions from defibrillators. The server employs Microsoft Internet Information Services (IIS). Code information is stored in a fundamental shared (network) directory as a flat file database that is not encrypted at rest. Protected Health Information (PHI) can be added to flat files but is not required. The defibrillator data contains no patient identifiers. Access to the application and storage tin can be administered via Active Directory.
Technology/Standard Usage Requirements:	Users must ensure their apply of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to employ of this applied science, users should check with their supervisor, Data Security Officer (ISO), Facility Principal Information Officer (CIO), or local Part of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Data:	This technology has not been assessed by the Department 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assist regarding Section 508, please contact the Department 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Determination Process:	1-VA TRM v20.four
Decision Date:	04/07/2020
Introduced Past:	TRM Request
Vendor Name:	ZOLL Data Direction

The Vendor Release tabular array provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Appointment	Vendor End of Life Date	Vendor Desupport Date
5.6.one	07/22/2014
v.7.x	01/22/2015
5.8.ten	06/09/2016
vi.v.x	08/14/2018

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, only not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Applied science (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to utilise of this technology, users should check with their supervisor, Information Security Officeholder (ISO), Facility Chief Information Officeholder (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consequent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best data available as of the most current date. The consumer of this information has the responsibleness to consult the organizations responsible for the desktop, testing, and/or product environments to ensure that the target version of the technology will be supported. Whatever major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can exist used inside the specified constraints located below the decision matrix in the footnote[1] and on the Full general tab.
Grey	Unapproved: This applied science or standard tin be used only if a POA&Thou review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated past the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or arrangement that wishes to use the applied science.
Orange	Divest: VA has decided to divest itself on the employ of the technology/standard. Every bit a consequence, all projects currently utilizing the technology/standard must program to eliminate their utilise of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Conclusion tab for the specific entry.
Black	Prohibited: The engineering science/standard is non (currently) permitted to be used under whatever circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Apply of this engineering science is strictly controlled and non bachelor for use within the general population. If a client would like to use this technology, please work with your local or Regional OI&T function and contact the appropriate evaluation role displayed in the notes beneath the decision matrix. The Local or Regional OI&T function should submit an enquiry to the TRM if they require farther help or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a '.ten' wildcard, which denotes a determination that pertains to a range of multiple versions.

For example, a engineering science approved with a conclusion for seven.x would cover whatever version of seven.(Anything) - seven.(Anything). Still, a 7.4.10 decision would embrace any version of 7.4.(Anything), but would not comprehend any version of 7.5.x or seven.6.ten on the TRM.

VA decisions for specific versions may include '+' symbols; which denotes that the decision for the version specified also includes versions greater than what is specified only is non to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.six.4+ would embrace any version that is greater than 12.6.four, but would not exceed the .6 decimal ie: 12.half dozen.401 is ok, 12.6.5 is ok, 12.6.ix is ok, however 12.7.0 or 13.0 is not.

<Past

CY2021

CY2022

CY2023

Time to come>

Release

v.6.1

Unapproved

5.seven.x

Unapproved

5.8.10

Unapproved

half dozen.v.10

Approved westward/Constraints
[v, 6, 9, 10]

Approved west/Constraints
[5, 6, ix, x]

Approved w/Constraints
[5, 6, 9, x]

Approved w/Constraints
[5, six, 9, 10]

Approved west/Constraints
[five, 6, 9, ten]

Approved w/Constraints
[5, six, 9, 10]

Approved westward/Constraints
[5, 6, nine, 10]

Approved westward/Constraints
[5, 6, 9, 10]

Approved w/Constraints
[v, 6, 9, 10]

Approved w/Constraints
[v, 6, 9, x]

Canonical w/Constraints
[five, half dozen, 9, 10]

Approved w/Constraints
[5, 6, nine, 10]

Decision Constraints


[1]	Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, FIPS 140-ii certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must exist documented in an approved Arrangement Security Program (SSP). In add-on, the applied science must exist implemented inside the VA production network (non in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this applied science should exist reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accord VA Directive 6004, VA Directive 6517 and VA Directive 6513.

[2]	If free trialware is utilized, the software must be purchased or removed at the end of the trial catamenia.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this engineering science should be reviewed by the local ISO (Information Security Officeholder) to ensure compliance with VA Handbook 6500.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Data Security Officer (CISO) FIPS 140-two Validate Full Disk Encryption (FOE) for Information at Balance in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database direction must apply Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the awarding level. If FIPS 140-2 encryption at the application level is non technically possible, FIPS 140-two compliant full disk encryption (FOE) must be implemented on the difficult drive where the DBMS resides. Appropriate access enforcement and physical security command must also be implemented. All instances of deployment using this engineering science should exist reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the organisation possessor to work with the local CIO (or designee) and Information Security Officeholder (ISO) to ensure that a compliant DBMS applied science is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[five]	Users should check with their supervisor, Information Security Function (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the main site that the creator of the software has advertised for public download and user or development community engagement. Users should note, whatsoever attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to refuse those installations.

[6]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and futurity security vulnerabilities.

[7]	Per the May fifth, 2015 memorandum from the VA Primary Information Security Officeholder (CISO) FIPS 140-2 Validate Total Disk Encryption (FOE) for Data at Residue in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA data at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-two compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must too be implemented. All instances of deployment using this engineering science should be reviewed to ensure compliance with VA Handbook 6500 and National Plant of Standards and Engineering (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[eight]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this engineering should be reviewed by the local ISO (Information Security Officeholder) to ensure compliance with VA Handbook 6500.

[9]	Users must ensure that Microsoft .NET Framework, Microsoft Net Information Services (IIS), and Microsoft Net Explorer are implemented with VA-approved baselines. (refer to the 'Category' tab under 'Runtime Dependencies')

[x]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should exist reviewed by the local ISO (Data Security Officeholder) to ensure compliance with VA Handbook 6500.

Annotation:

At the fourth dimension of writing, six.5.6.10 is the nearly current version.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Other	RescueNet Code Review Getting Started Guide	Vendor	This link provides access to guidance for using RescueNet Code Review.

Annotation: This listing may not be consummate. No component, listed or unlisted, may exist used outside of the applied science in which it is released. The usage decision for a component is plant in the Decision and Decision Constraints.
Name	Description
ZOLL Data Relay	This is available in the Enterprise Edition and enables users to transmit digital 12-lead and vital trends to a destination fax number or email accost.
ZOLL Data Retriever	This is available in both the Standard and Enterprise Editions and allows users to upload defibrillator records straight to a folder location, add patient data, and erase the card and then that the defibrillator can be immediately placed back in service.
ZOLL Data Retriever Service	This handles the transfer of cases uploaded to a central location. Information technology allows for the transfer of information in the background of the awarding.

Domain Area	Category	Customer Guidance	Category Locked By ELT Appointment
Collaboration and Electronic Workplace Productivity Software	Health Care

Windows Client - Canonical w/Constraints
Windows Server - Approved w/Constraints

Adoption Benefits

This engineering science may provide efficiencies to those who have clinical responsibilities assessing Electrocardiography (ECG) and vital signs data collected from defibrillators.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Network Security Operations Center (NSOC) bulletins had been issued for the latest versions of this applied science.
There is no licensing fee associated with the Standard Edition of the software.
The vendor asserts this engineering supports Wellness Insurance Portability and Accountability Act (HIPAA) regulations and protects patient security and confidentiality.
This is a mature, well-documented technology.

Adoption Risks

This product does not back up information encryption.
Due to the rapid release schedule of this engineering, the VA may exist unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
The potential exists to shop Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive information and proper security standards must be followed in these cases.

Architectural Benefits

This technology can export reports into Hyper Text Markup Language (HTML) and Portable Document Format (PDF).

Architectural Risks

This engineering is not portable.

- The data contained on this page is accurate equally of the Decision Engagement (04/07/2020).

mazincusithedeweese1.blogspot.com

Source: https://www.oit.va.gov/Services/TRM/ToolPage.aspx?tid=7733

Zoll Code Review There Was a Problem With This Installer Package