VoiceOver Pathology Reporting Optimized (PRO)

General Information

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

Website:	Go to site
Description:	VoiceOver Pathology Reporting Optimized (PRO) is a speech recognition software-based reporting solution that is designed for pathology dictation. This technology provides users with multiple dictation options including downtime reporting and digital recording for front-end capture and third-party editing. Customizable templates allow users to speed through the reporting process with discrete data fields that auto-advance to avoid unnecessary commands. This technology is available in four editions, Basic, Generic Speech, Transcription, and Premium. This entry covers all four editions. This technology utilizes a Microsoft Structured Query Language (SQL) Server database.
Technology/Standard Usage Requirements:	Users must ensure their use 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 use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office 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 Information:	This technology has not been assessed by the Section 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 assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.4
Decision Date:	04/04/2024 at 03:11:18 UTC
Introduced By:	TRM Request
Vendor Name:	Voicebrook

Vendor Release Information

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

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
Summer 2018 R.x	05/16/2018
Spring 2019 R.x
Fall 2019 R.x
Spring 2020 R.x	09/20/2020
Winter 2021 R.x	01/26/2021
Spring 2021 R.x	04/06/2021
Winter 2022 R.x	03/16/2022
Fall 2022 R.x	01/12/2023
Winter 2023 R.x	02/23/2023
Spring 2023 R.x	05/23/2023
Summer 2023 R.x	08/18/2023
Fall 2023 R.x	11/21/2023
Spring 2024 R.x	03/24/2024

Current Decision Matrix (04/01/2024)

Users must ensure their use 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 use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent 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 information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any 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 be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by 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 organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x 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 but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2021

CY2022

CY2023

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Summer 2018 R.x

Unapproved

Spring 2019 R.x

Divest
[2, 4, 5, 6]

Divest
[2, 5, 6, 7]

Unapproved

Fall 2019 R.x

Divest
[2, 4, 5, 6]

Divest
[2, 5, 6, 7]

Unapproved

Spring 2020 R.x

Approved w/Constraints
[2, 4, 5, 6]

Divest
[2, 5, 6, 7]

Divest
[2, 5, 6, 8]

Unapproved

Winter 2021 R.x

Unapproved

Approved w/Constraints
[2, 5, 6, 7]

Divest
[2, 5, 6, 8]

Divest
[2, 9, 10, 11]

Unapproved

Spring 2021 R.x

Unapproved

Approved w/Constraints
[2, 5, 6, 7]

Divest
[2, 5, 6, 8]

Divest
[2, 9, 10, 11]

Unapproved

Winter 2022 R.x

Unapproved

Approved w/Constraints
[2, 5, 6, 8]

Divest
[2, 9, 10, 11]

Divest
[2, 10, 12, 13]

Fall 2022 R.x

Unapproved

Divest
[2, 9, 10, 11]

Divest
[2, 10, 12, 13]

Winter 2023 R.x

Unapproved

Approved w/Constraints
[2, 9, 10, 11]

Divest
[2, 10, 12, 13]

Spring 2023 R.x

Unapproved

Divest
[2, 10, 12, 13]

Summer 2023 R.x

Unapproved

Approved w/Constraints
[2, 10, 12, 13]

Fall 2023 R.x

Unapproved

Spring 2024 R.x

Unapproved

Decision Constraints


[1]	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 be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

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

[3]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest 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 information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (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).

[4]	Users must ensure that Microsoft Word, Microsoft Structured Query Language (SQL) Server, and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[5]	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 be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest 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 information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (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).

[7]	Users must ensure that Microsoft Word, Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Service (IIS), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[8]	Users must ensure that Microsoft Word, Microsoft Structured Query Language (SQL) Server, Microsoft Internet Information Service (IIS), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.

[9]	Users must ensure that Microsoft Internet Information Service (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Per the Security Policy Product Review, users must abide by the following constraints: The latest version of this product is VoiceOver PRO Basic which was released on November 24, 2021. Voicebrook announced an expansion of its suite of pathology reporting solutions with the launch of VoiceOver PRO Basic. VoiceOver PRO Basic is a slimmed-down version of the company’s revolutionary reporting solution, VoiceOver PRO Premium. The difference between Basic and Premium is as following: Basic is a budget-friendly version of PRO that features the essential reporting tools labs need, like Report Builder (Classic), CAP eCC, and standardized templated content to create traditional narrative reports. Basic builds reports using a combination of free-text and templates. There is a level of “self-service” that users can opt to use in Basic, which offers flexibility in how they wish to use the software. Premium comes with all the foundational features of Basic, plus a full suite of synoptic reporting tools and role-based templates. With Premium’s Report Builder, all data in the report is discrete, not just simple text. That results in more smart behaviors like automatically calculating fields, changing plurality, and picklists. Operating Systems supported by VoiceOver PRO include: Windows 8 Windows 10 Windows 7 is not supported by VoiceOver PRO as Microsoft announced to discontinue their support for it. The vendor was non-responsive in the information gathering process; unable to determine 508 compliancy.

[10]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest 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 information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) 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).

[11]	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 be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[12]	Users must ensure that Firefox, Google Chrome, Microsoft Word, Microsoft Internet Information Service (IIS) and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Per the Security Policy Product Review, users must abide by the following constraints: The latest version of this product is VoiceOver PRO Basic which was released on November 24, 2021. Voicebrook announced an expansion of its suite of pathology reporting solutions with the launch of VoiceOver PRO Basic. VoiceOver PRO Basic is a slimmed-down version of the company’s revolutionary reporting solution, VoiceOver PRO Premium. The difference between Basic and Premium is as following: Basic is a budget-friendly version of PRO that features the essential reporting tools labs need, like Report Builder (Classic), CAP eCC, and standardized templated content to create traditional narrative reports. Basic builds reports using a combination of free-text and templates. There is a level of “self-service” that users can opt to use in Basic, which offers flexibility in how they wish to use the software. Premium comes with all the foundational features of Basic, plus a full suite of synoptic reporting tools and role-based templates. With Premium’s Report Builder, all data in the report is discrete, not just simple text. That results in more smart behaviors like automatically calculating fields, changing plurality, and picklists. Operating Systems supported by VoiceOver PRO include: Windows 8 Windows 10 Windows 7 is not supported by VoiceOver PRO as Microsoft announced to discontinue their support for it. The vendor was non-responsive in the information gathering process; unable to determine 508 compliancy.

[13]	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 be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

Note:

At the time of writing, version Spring 2024 is the most current version, released 03/24/2024.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
PRO Assistant	PRO Assistant is an intelligent reporting utility designed to aid speech pathologists to report a correct diagnosis with supporting evidence accurately.
PRO Report Builder	PRO Report Builder offers users gross and microscopic templates with smart behaviors along with synoptic reporting and structured data collection options.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Health Care
Health Care Administrative	Health Delivery Support
Health Care Health Services	Pathology and Laboratory Medicine Services

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

Microsoft .NET Framework
Microsoft Edge.
Microsoft Internet Explorer (IE) - (required for some configurations)
Microsoft Internet Information Services (IIS)
Microsoft Structured Query Language (SQL) Server
Microsoft Word
PowerShell
Windows Media Player

Comparable Technologies:

VoiceOver Enterprise.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This technology may improve productivity for specific staff whose responsibilities include exchange of medical data.
This product supports role-based authentication and authorization capabilities.
The vendor asserts this technology supports Health Insurance Portability and Accountability Act (HIPAA) regulations and protects patient security and confidentiality.
This technology may create efficiencies in clinical environments by decreasing the time required for pathology dictation, which may result in faster diagnosis and time to treatment.
There is no known security related vulnerability listed for this product at this time.

Adoption Risks

This technology involves the use Universal Serial Bus (USB) connections and proper security precautions must be taken when used.
Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There is limited publicly available technical documentation for this technology.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology can integrate with and alter database technologies.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology supports AES Encryption.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/01/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (04/01/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES