Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Vocera Communications Platform

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:	The Vocera Communications Platform is a wireless network-based software solution that provides voice communication for mobile personnel in hospital, retail, government, manufacturing, and other in-building environments with a dispersed workforce. Note: This application requires isolation. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx This entry is the next generation or continuation of Vocera Communications System, after the versioning convention and technology name was changed.
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.7
Decision Date:	07/12/2024 at 02:55:59 UTC
Aliases:	Vocera Platform, Vocera Voice Server
Introduced By:	TRM Request
Vendor Name:	Stryker

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
6.0.x
6.1.x
6.2.x
6.3.x
6.4.x
6.5.x
6.6.x	12/21/2022

Current Decision Matrix (07/02/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

6.0.x

Unapproved

6.1.x

Unapproved

6.2.x

Divest
[1, 3, 5, 6, 7]

Divest
[3, 5, 6, 7, 8]

Unapproved

6.3.x

Approved w/Constraints
[1, 3, 5, 6, 7]

Approved w/Constraints
[3, 5, 6, 7, 8]

Divest
[5, 6, 7, 9, 10]

Unapproved

Divest
[5, 6, 7, 10, 11]

Divest
[5, 10, 12, 13, 14]

Divest
[5, 10, 12, 14, 15]

6.4.x

Unapproved

Approved w/Constraints
[5, 6, 7, 9, 10]

Divest
[5, 6, 7, 10, 11]

Divest
[5, 10, 12, 13, 14]

Divest
[5, 10, 12, 14, 15]

6.5.x

Unapproved

Approved w/Constraints
[5, 6, 7, 10, 11]

Divest
[5, 10, 12, 13, 14]

Divest
[5, 10, 12, 14, 15]

6.6.x

Unapproved

Approved w/Constraints
[5, 10, 12, 13, 14]

Approved w/Constraints
[5, 10, 12, 14, 15]

Decision Constraints


[1]	This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE) are implemented within VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: The Vocera Communications Platform must be configured for FIPS mode only. Only FIPS compliant client devices (badges and smartphones) must be used. The B3000n badge is the most current model available that is compliant with FIPS 140-2. Vocera V5000 Release Notes Versions 5.1.0 and 5.1.1 are currently on the “Under Test List” for FIPS 140-2 certification. Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized. Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only. This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers. System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled. For software listed as DIVEST on the VA TRM, the 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. For software listed as UNAPPROVED on the VA TRM, the VA utilizes the risk-based decision process defined in the VA POA&M Management Guide and Accreditation Requirement Guide in accordance with VA Handbook 6500 - Risk Management Framework for VA Information Systems - Tier 3: VA Information Security Program. Please reach out to your ISSO, ISO and SS for pre-existing systems to enter a high or higher POA&M for the “TRM Unapproved technology”. The Vocera Communications Platform will need to be isolated on a SDIA if any of the following apply: Requirements for isolation: Vocera servers cannot follow VA approved baselines. The servers cannot be managed in a SCCM environment Status of McAfee availability for systems. TRM approved status. The solution uses or requires external connections. The vendor offers a remote support option. A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system.

[2]	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.

[3]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[4]	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).

[5]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[6]	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.

[7]	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).

[8]	This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Users must ensure that Firefox, Google Chrome, Microsoft Internet Explorer (IE) are implemented within VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: The Vocera Communications Platform must be configured for FIPS mode only Only FIPS certified client devices (badges and smartphones) must be used. The Vocera V5000 Smartbadge has achieved FIPS certification # 3865. The B3000n FIPS module expired on 4/17/2021 but the replacement is in “review pending” status. The replacement module is listed athttps://csrc.nist.gov/Projects/cryptographic-module-validation-IPR – Vocera Communications Platform June 29, 2021 For Internal VA Use Only Page 6 of 10 program/modules-in-process/Modules-In-Process-List. Sites using the B3000n must complete a local POA&M to continue to use these devices and only procure the devices utilizing the Vocera Cryptographic Module 3.1 once the FIPS certification is finalized and certificate number is issued. Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized. Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only. This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers. System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled The Vocera Communications Platform will need to be isolated on a SDIA if any of the following apply: Requirements for isolation: Vocera servers cannot follow VA approved baselines. The servers cannot be managed in a SCCM environment Status of McAfee availability for systems TRM approved status The solution uses or requires external connections The vendor offers a remote support option. A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system.

[9]	This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system. This product can be configured with a MySQL Database which currently has TRM constraints for intranet use only due to its many known security issues. If MySQL is selected for use with this product, these factors should be considered especially when an instance of this product will be considered a Moderate or High Risk system. See the MySQL Database TRM entry for more details. Users must Divest the use of Internet Explorer with this technology. Other approved dependencies are available. Apache Tomcat currently lacks a required VA baseline. In order to reduce costs, risk and overhead in many areas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment. The Apache Tomcat Secure Configuration Baseline is currently being developed by the Solution Delivery Baseline Configuration Management Team. All technologies must comply with the Apache Tomcat baseline when completed and approved. Until the baseline has been completed, Apache Tomcat will remain in Divest status. See Category Tab for details. Users must ensure that Firefox and Google Chrome are implemented within VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: The Vocera Communications Platform must be configured for FIPS mode only. Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized. Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only. This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers. System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled. The Vocera Communications Platform will need to be isolated on a SDIA if any of the following apply: Requirements for isolation: Vocera servers cannot follow VA approved baselines. The servers cannot be managed in a SCCM environment Status of McAfee availability for systems TRM approved status The solution uses or requires external connections The vendor offers a remote support option. A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system.

[10]	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.

[11]	This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. Users must ensure that Microsoft Internet Explorer (IE), Firefox, Apache Tomcat and Google Chrome are implemented within VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: The Vocera Communications Platform must be configured for FIPS mode only. Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized. Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only. This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers. System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled. The Vocera Communications Platform will need to be isolated on a SDIA if any of the following apply: Requirements for isolation: Vocera servers cannot follow VA approved baselines. The servers cannot be managed in a SCCM environment Status of McAfee availability for systems TRM approved status The solution uses or requires external connections The vendor offers a remote support option. A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system.

[12]	This technology is only authorized for use as a secondary communications system and CANNOT be a primary life safety communications system. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details. Users must ensure that Apache Tomcat is implemented within VA-approved baselines. Per the Initial Product Review, users must abide by the following constraints: The Vocera Communications Platform must be configured for FIPS mode only. Vocera recommends the use of Advanced Encryption Standards (AES) based WIFI-Protected Access 2- Pre-Shared Key (WPA2-PSK) with FIPS 140-2 deployed in an enclave on its own Virtual Local Area Network (VLAN) and protected by firewalls, Access Control Lists (ACLs) and other network boundary traffic controls. With this network isolation implemented and the use of industry standard components, the risk of not having a finalized threat model is minimized. Standard network application monitoring tools can be used to monitor the system (Windows) and the specific resource usage of the application. Vocera does provide an e-mail alert system for system events and this can be configured to send e-mails for significant system events and should be utilized. Upgrade to Apache Tomcat version 8.5 / 9.x or later. Vocera will provide an Apache Tomcat update in the next maintenance release. Additional mitigation is to deploy the Vocera solution behind site firewall and VLAN. This will limit access to Vocera Server resources to only individual allowed to be on the site network. Further mitigation is to limit (via official assignment) access to the Vocera servers and web consoles to Vocera administrators only. This issue is resolved in Vocera Platform 6. System owners must up upgrade to the latest version of Vocera to ensure the use of secure ciphers. System owners should use the most up to date version of Apache Spark on the Vocera Analytic Server as the older versions (2.3.3 and earlier) can allow data to be written to disk unencrypted when encryption is enabled. The Vocera Communications Platform will need to be isolated on a SDIA if any of the following apply: Requirements for isolation: Vocera servers cannot follow VA approved baselines. The servers cannot be managed in a SCCM environment Status of McAfee availability for systems TRM approved status The solution uses or requires external connections The vendor offers a remote support option. A SNOW ticket must be submitted to the Specialized Device Security Division and ACL COMM Profile assigned to the system.

[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 VA Handbook 6500.

[14]	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).

[15]	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 6.6.1 is the most current version, released 5/16/2024.

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.

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
My Structured Query Language (MySQL) Database	My Structured Query Language (MySQL) Database is an open source Relational Database Management System (RDBMS). The edition that works with Vocera Communications Platform is a managed component.
Vocera Engage Platform	The Engage Platform is designed to manage patient event alarm and alert notifications and to ease care team communication in response to patient events. The alarm management and event response solution helps nurses and other caregivers prioritize patient needs and better collaborate with care team members. In the Legacy Communications System, this technology was an individually installed technology. However, in new 6.x Communications Platform, this technology was absorbed and is now deployed as a component.
Vocera Messaging Platform (VMP)	The Vocera Messaging Platform (VMP) provides an enterprise messaging and alerting solution designed to address the unique communication challenges of healthcare. Users leverage the communication features from the smartphone client, a Web Console, and the Vocera badge. <br><br> In the Legacy Communications System, this technology was an individually installed technology. However, in new 6.x Communications Platform, this technology was absorbed and is now deployed as a component.
Vocera Voice Server (VVS)	The Vocera Voice Server (VVS) is the centerpiece of the Vocera products ecosystem. It enables hands-free wireless voice communication that users control through natural spoken commands, provides voice workflow capabilities, and provides APIs to interface with common third-party clinical systems. <br><br> In the Legacy Communications System, this technology was an individually installed technology. However, in new 6.x Communications Platform, this technology was absorbed and is now deployed as a component.


Collaboration and Electronic Workplace Collaboration Software	Unified Messaging

- The information contained on this page is accurate as of the Decision Date (07/12/2024 at 02:55:59 UTC).

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 (07/02/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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (07/02/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

EMAIL UPDATES