Pats 0 Systems Management Guide

2.4 Services

The following VA services are deployed locally in a development WebLogic server:

Dependency	Version Used
Standard Data Services (SDS)	Standard Data Services 18
Vista Link	Vista Link Java 1.5.2
Kernel Authentication Authorization Java Enterprise (KAAJEE)	Kernel Authentication Authorization Java Enterprise Environment 1.0
Person Service Lookup (PSL)	Person Service Lookup 4.0
Patient Service Construct (PSC)	Patient Service Construct R2

3.0 Business Rules Implementation

3.1 Web Security

The security constraints placed on the URLs that a user may access are located in web.xml. Programmatic security is used for hiding invalid options.

3.2 Ejb Method Permission Security

EJB declarative security in ejb-jar.xml is used to define method permissions in the business layer. Programmatic security is not used in the business layer.

3.3 Transactions

PATS does not use Java transactions. PATS uses Oracle transactions in stored procedures.

3.4 ROC

The business rules for reports of contact are in the class gov.va.med.pats.ejb.policy.RocRule.

3.5 Notification

The business rules for sending notifications are in gov.va.med.pats.ejb.policy.NotificationRule.

3.6 Table Maintenance

The table maintenance subsystem of PATS is isolated in two EJBs: NationalMaintenance and VISNMaintenance.

3.7 Concurrency

PATS uses optimistic concurrency. In the Java tier of PATS this means all value objects extend the abstract class gov.va.med.pats.value.ValueObject. The field rowVersion is passed to each update stored procedure transaction.

3.8 Application Design Parameters

3.8.1 Timeout Parameters

• 
  PATS times out after 20 minutes of inactivity.
  
• 
  When users select the Ad hoc reporting option, PATS launches a separate application, BOEXI Web Intelligence. It appears as if users are still in the PATS application though they’re actually in Web Intelligence. Users may stay in the ad hoc reports application designing reports for longer than 20 minutes. For that reason, when PATS launches Web Intelligence, the timeout for the PATS application running in the background is temporarily changed to 60 minutes. The timeout is temporarily changed so that PATS won’t timeout in the background while the user is in ad hoc reporting. When the user returns to the PATS application, the timeout reverts to 20 minutes.
  

3.8.2 Date Parameters

• 
  PATS currently maintains all data migrated from Patient Rep. The age of the oldest data can vary from site to site, depending on how long a site used the Patient Rep application before migrating to PATS, and whether they ever archived and purged their Patient Rep data.
  
• 
  For standard and ad hoc reports PATS provides data only for the current fiscal year and two previous fiscal years.
  

3.8.3 Report Instance Limits

The number of report instances that can be stored is limited as described in the Instance Limits section of the Business Objects chapter. If the limit is exceeded, old report instances are automatically purged.

3.8.4 Text Field Length

• 
  The length of the Issue Text field is limited to 4000 characters.
  
• 
  The length of the Resolution Text is limited to 8000 characters. This is stored in two 4000-character fields in the Oracle database but appears to the end user to be a continuous 8000-character text string.
  

4.0 M VistA

Prior to using the PATS application at a given site, the site must install a KIDS build. The KIDS build brings in routines, options, remote procedure calls (RPCs), and security keys. No new data files are brought in with this installation, and the existing Patient Representative files, routines, options and security keys are not changed by this installation. See the Patient Advocate Tracking System (PATS) Installation Guide for IRM Staff for instructions on the installation and setup.

Legacy data from the Patient Representative system must be cleaned then migrated into the PATS Oracle database prior to using the PATS application. See the Patient Advocate Tracking System (PATS) Data Migration Guide for instructions.

The PATS application retrieves some patient and employee demographic data from the VistA system where the current user is logged on. This data is stored for use in reporting, but cannot be edited from within the PATS system. When a patient is selected for inclusion on a Report of Contact, PATS uses the Patient Service Lookup and Patient Service Construct services to find and retrieve patient information. This data currently comes from VistA. In addition, PATS retrieves person demographics from the VistA NEW PERSON file. This occurs when a patient advocate is selected as either the information taker or entered by person on a ROC, when an employee is selected as the employee involved in a ROC, or when an employee is sent a notification from PATS.

4.1 Namespace

Routines, options, and remote procedures beginning with QACI are used to migrate legacy data into PATS. Routines, remote procedures and security keys beginning with QACV are used during normal operation of the PATS application.