Pats 0 Systems Management Guide



Yüklə 0,55 Mb.
səhifə11/18
tarix24.02.2018
ölçüsü0,55 Mb.
#27941
1   ...   7   8   9   10   11   12   13   14   ...   18

4.8 Online Documentation


The PATS options used for data migration use standard FileMan conventions for online help.

4.9 Check Sum Values for Routines


Using CHECK1^XTSUMBLD. There are 17 routines:


Routine

Value

QACI0

1984508

QACI1

23422676

QACI1A

6784447

QACI2

15898410

QACI20

56932032

QACI2A

18512192

QACI2B

36187753

QACI2C

34183381

QACI2D

68859293

QACI2E

22678389

QACI3

8458772

QACI4

3186113

QACI5

43902138

QACIENV

2063143

QACVDEM

35412405

QACVEMPX

18632980

QACVKHLD

5032982



4.10 Security and Keys


PATS uses the Kernel Authentication Authorization Java Enterprise Environment (KAAJEE), 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. The same access and verify codes used for VistA are also used to sign on to PATS.
Security Keys stored in the VistA system are used to control access to various options within the PATS system.


Keys

Access Level

QACV_ADUSH

Assistant Deputy Undersecretary for Health (later changed in PATS documentation to Central Office user). Has access only to the National Patient Report.

QACV_DMGR

Data Migration Manager –The person assigned the VistA option to move legacy Patient Representative data into the staging area prior to migration to PATS is given this key. This person is also responsible for using the PATS Data Migration application to do the migration of the legacy data into PATS.

QACV_NPO

National Program Office – The person given this key has access to maintain national tables within the PATS system. This includes the Issue Category, Issue Code, Contacting Entity, Method of Contact, Treatment Status, and National PATS Parameters. Also has access to the National Patient Report.

QACV_SIT

Site Information Taker – This is an administrative person at a medical center. The person given this key is allowed to enter or update ROCs in the PATS system, but is not allowed to perform maintenance tasks, such as entering boilerplate resolution information or close the ROCs.

QACV_SRCU

Site Record Control User – This is a Patient Advocate. The person given this key is allowed to enter, edit, resolve and close Reports of Contact. This person also maintains the locally controlled reference tables: Hospital Location, Congressional Contacts, Boilerplate Resolution Text and Comps.

QACV_VU

VISN User – The person given this key maintains the Facility Service or Section table in the PATS system for their VISN.


5.0 Database - Oracle

The PATS persistent data is stored in Oracle tables maintained on a central server. The version at the time of PATS initial installation is Oracle 11g.


5.1 Database

The name of the production database at the HSI’s Data Center is VPFSPRD.med.vha.va.gov.



5.2 Schemas


Schema

Description

PATS

Owns all of the tables and procedures for the main PATS application.

PATSRPTS

Owns all of the tables and procedures that will be used to support both standard and ad hoc reporting.



5.3 Users


User

Description

PATS

Owns all of the tables and procedures for the main PATS application. No external database connections are made directly as the PATS user.

PATSRPTS

Owns all of the tables and procedures that will be used to support both standard and ad hoc reporting. The only external database connection made as PATSRPTS is when making a connection to the database in order to run standard reports (Crystal Reports) or to access the PATS Universe for creating ad hoc reports.

PATSUSER

Owns no Oracle objects. All database connections from the PATS application user interface, with the exception of reporting, are made as PATSUSER. The patsuser_role is assigned to this user and controls access to Oracle objects.

PATSHOST

Owns no Oracle objects. All database connections from the PATS Data Migration application are made as PATSHOST. The patshost_role is assigned to this user and controls access to Oracle objects.

PATSROLLUP

The VSSC will connect as this user when fetching the weekly rollup data for the VSSC reports. This user has SELECT access ONLY to the pats_rollup_natl_data table.

Yüklə 0,55 Mb.

Dostları ilə paylaş:
1   ...   7   8   9   10   11   12   13   14   ...   18




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©genderi.org 2024
rəhbərliyinə müraciət

    Ana səhifə