Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.4

csCoder Technology

General InformationGeneral Information help

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: csCoder is a medical coding technology that assists users in the coding of terminology and pharmaceutical drug names. Users can match pieces of the date to publicly available coding dictionaries. This technology is able to export the matched data in machine-readable formats for further processing and analysis.

csCoder servers are housed and physically maintained/secured by Limestone Networks in Dallas, Texas. Crucial Data Solutions does not physically house them, but does have full remote control of dedicated stacks. Data is stored on the server database in a PostgreSQL database; no data is stored locally on clients. The client operating system connects directly to the server via a web browser. Data reaches the server via a HyperText Transfer Protocol Secure (HTTPS) connection using standardized Secure Sockets Layer (SSL)/RSA keys. Additionally, all users are authenticated via tokenization on every page load.

csCoder is a web-based application that is currently hosted externally (outside of VA`s own server infrastructure). However, per the vendor, VA can opt to install and host the software on VA premises.

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:

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
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 been assessed by the Section 508 Office and found non-conformant. 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 Please see reference tab for more information concerning product versions.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v21.4
Decision Date: 04/01/2021 at 08:07:16 UTC
Aliases: Clinical Studio Medical Coding
Introduced By: TRM Request
Vendor Name: Crucial Life Sciences Data Solutions, Inc.
- The information contained on this page is accurate as of the Decision Date (04/01/2021 at 08:07:16 UTC).