Pats 0 Systems Management Guide

4.5 Remote Procedure Calls

Name	Description
QACI DELETE ALL LISTS	Used in data migration (PATSDM), this is called when user selects the option to delete all of the data from the Oracle side to completely restart the data migration process. This deletes all lists of Patient Rep items that have been migrated into PATS from the ^XTMP global.
QACI LOAD REFERENCE TABLES	Used in data migration (PATSDM), this loads reference table data from the ^XTMP global into the ^TMP global to send back to the calling program.
QACI LOAD ROC	Used in data migration (PATSDM), this loads ROC data from the ^XTMP global into the ^TMP global to send back to the calling program.

Name	Description
QACI NATL INSTITUTION LIST	Used in application to download list of national divisions (PATSDV). Retrieves a list of station numbers from the Standard Data Services institution table std_institution. The list contains all station numbers that begin with the 3-character computing facility station number (default institution). The list is stored in the ^XTMP array and is used in the pre-migration data cleanup option to make sure that any data references only valid station numbers.
QACV KEY HOLDERS VLH	Used when running PATS, this returns lists of employees who hold one or more security keys. This takes as input an array of security key names, a number ‘n’ indicating how many rows to return, and optionally a ‘previous name returned’ and ‘previous IEN returned’. If the ‘last name’ and ‘last IEN’ are input, they are used to find the starting point for the search. The RPC returns the next ‘n’ entries from the NEW PERSON file that holds one or more of the keys in the input list. The output list includes the person name, Title and Mail Code. The RPC also returns a flag indicating whether there are more entries.
QACV PERSON LOOKUP VLH	Used when running PATS, this returns lists of employees, matching on first and last name. This takes as input a name in the format ‘last,first’, a number ‘n’ indicating how many rows to return, and optionally a ‘previous name returned’ and ‘previous IEN returned’. If the ‘last name’ and ‘last IEN’ are input, they are used to find the starting point for the search. The RPC returns the next ‘n’ entries from the NEW PERSON file whose name matches the input parameter. The output list includes the person name, Title and Mail Code. The RPC also returns a flag indicating whether there are more entries.

4.6 External Relations

KAAJEE: PATS uses the Kernel Authentication Authorization Java Enterprise Environment, a Security service located on VistA for use by reengineered web applications, for authenticating users during sign on, and for allowing them access to various PATS options based on roles. KAAJEE has a VistA component that must be installed in order to run PATS. The roles-based access is controlled by the use of new security keys created for PATS. See ‘Security Key’ section below for details. The list of accessible divisions’ data is retrieved by KAAJEE from the DIVISION multiple on the VistA NEW PERSON file.
VistALink: PATS uses VistALink, a communications bridge between VistA and J2EE application Servers, to retrieve data. VistALink has a VistA component that must be installed in order to run PATS.
Person Service Lookup: PATS uses Person Service Lookup service when the user needs to add a patient to a ROC. The service includes a User Interface (UI) that is incorporated within PATS. The UI prompts for patient information and displays a list of matching patients. When a patient is selected, any patient related warnings and additional information are displayed. The identifier for the patient is then returned to the PATS application and stored in a local PATS table. Person Service Lookup has a VistA component that must be installed in order to run PATS.
Patient Service Construct: After a patient has been selected for a ROC, PATS calls Patient Service Construct service to get patient demographics information for the patient. This information is stored on a local PATS table to support reporting and rollup to Austin. Patient Service Construct has a VistA component that must be installed in order to run PATS.
VistA Data used in PATS: During data migration each site will use new VistA options to check for errors in their legacy data and a web-based application to migrate the clean data from VistA into the PATS Oracle tables. This includes some Patient demographics and data from the NEW PERSON file (#200). HOSPITAL LOCATION file (#44) entries referenced by ROCs in VistA are migrated to the hospital_location table within PATS. From that point forward, the table is maintained entirely by the PATS users and has no remaining ties to the VistA HOSPITAL LOCATION table.
Patient and Person demographic data cannot be altered by the PATS application. Patient data is refreshed from VistA when a patient is selected on a ROC using the Patient Service Construct methods. Remote Procedure Calls written for the PATS application are used to retrieve some demographic data from the VistA NEW PERSON file when an Employee Involved is added to a ROC, or when a Notification is sent to an Employee.
Note: None of the new VistA routines, options or remote procedure calls brought in with the PATS installation should be called by any application outside of PATS.