Enterprise Web Developer (EWD).js

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:	EWD.js is a Node.js-based application framework and application server and container for use with Cache, GlobalsDB, GT.M, and MongoDB databases to develop web services, which utilize Massachusetts General Hospital Utility Multi-Programming System (MUMPS) environment application business logic. This technology acts as a web server for serving up static content and provides the WebSockets back-end tier. This technology projects a MUMPS database as a Native JavaScript Object Notation (JSON) Database, such that MUMPS data storage can be treated as persistent JSON storage. VA is moving towards adoption of Intersystems HealthShare as a standard interfacing solution between Veterans Health Information Systems and Technology Architecture (VISTA) and non-VISTA product technologies. Due to the vision of Electronic Health Record Management (eHRM), implementers of EWD need to plan for the migration to use of HealthShare as a best practice for interfacing VISTA products to non-VISTA products.
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 v20.12
Decision Date:	12/03/2020 at 22:38:30 UTC
Introduced By:	TRM Request
Vendor Name:	M/Gateway Developments Ltd

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
882	09/08/2011
910	08/01/2012
41 lite	06/01/2013
45 lite	08/01/2013
60	05/09/2014
70	07/25/2014
81	09/26/2014
90	11/17/2014
92.x	12/17/2014
96.x	02/09/2015
98.x	03/02/2015
99.x	05/01/2015
100.x	06/29/2015
101.x	08/19/2015
102.x	08/27/2015
103.x	09/01/2015
111.x	01/25/2016

Current Decision Matrix (12/03/2020)

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

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

45 lite

Unapproved

98.x

Unapproved

99.x

Unapproved

100.x

Unapproved

101.x

Unapproved

102.x

Unapproved

103.x

Unapproved

111.x

Unapproved

Decision Constraints


[1]	VA projects are required to seek a waiver from the Architecture and Engineering Review Board in order to obtain confirmation that the product is appropriate for use by their project.

[2]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

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

[4]	National VA software development projects are required to submit a design strategy to the Architecture and Engineering Review Board in order to obtain confirmation that the product is appropriate for use by their project.

[5]	Users should check with their supervisor, Information Security Office (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 primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[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]	VA OI&T Enterprise Program Management Office (EPMO) software development projects are required to instead use VISTA.js as the method of interfacing VISTA Class 1 data systems to non-Mumps systems due to additional controls applied by VISTA.js.

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

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

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

[11]	VA OIT Enterprise Program Management Office (EPMO) software development projects are required to instead use VISTA.js as the method of interfacing VISTA Class 1 data systems to non-MUMPS systems due to additional controls applied by VISTA.js.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
There are no references identified for this entry.

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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Development Frameworks

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

HealthShare

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology can be acquired without cost to the organization through open source licensing and supports VA`s open source initiative.
There are no known Common Vulnerabilities and Exposures (CVEs) for this technology at the time of writing.
This is a mature technology.

Adoption Risks

This technology has been deprecated by the vendor for an updated modularized version of the product.
This technology has the potential to collect, store, or transmit Personally Identifiable Information (PII)/Protected Health Information (PHI), and/or other sensitive VA data.

Architectural Benefits

This technology is portable across multiple VA-supported 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 (12/03/2020)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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 (12/03/2020)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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