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 21.8

PainCAS (Clinical Assessment System)
PainCAS (Clinical Assessment System) 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: PainCAS (Clinical Assessment System) is an application that assesses pain and opioid risk in chronic pain patients. PainCAS is designed to minimize provider variability and the likelihood of miscommunication or deficits in care by facilitating a streamlined patient assessment process. This software creates patient assessments and reports using initial and follow-up questionnaires that capture the patient`s pain condition, treatment history, and changes over time.

Although, PainCAS can be implemented as a cloud-based Software as a Service (SaaS) when it is hosted on external (vendor) servers, there is an option for the application to be deployed on VA premises.

This application is served through Microsoft Internet Information Services (IIS) and any request to the server is secured using Transport Layer Security (TLS). PainCAS is developed on Microsoft .NET technology and hosted on Microsoft Windows Server, which connects to Microsoft Structured Query Language (SQL) Server relational database for storing patient Protected Health Information (PHI) and assessment-related data. The database is encrypted using Transparent Data Encryption (TDE) and field/column-level encryption is also supported for PHI data.

This technology comes in three different editions: PainCAS Free, PainCAS Premium, and PainCAS Enterprise. This entry covers all three versions.

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: https://dvagov.sharepoint.com/sites/OITEPMOECSO

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
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.8
Decision Date: 08/03/2020
Introduced By: TRM Request
Vendor Name: Allscripts
- The information contained on this page is accurate as of the Decision Date (08/03/2020).