| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| IA # | Name | Type | Custodial Package | Date Created | DBIC Approval Status | Status | Usage | File # | General Description | Remote Procedure | Routine | Date Activated |
| 153 | DBIA153-A | File | QUALITY ASSURANCE INTEGRATION | 1992/04/20 | APPROVED | Active | Private | 741 | Read access to find patients who have had a QA occurrence which was refered to peer review associated with a particular admission. File 741 QA OCCURRENCE SCREEN The B cross reference Field 1 DATE REVIEWER (MULTIPLE) Field .01 REVIEW LEVEL Field 11 STATUS |
|||
| 620 | DBIA153-B | File | QUALITY ASSURANCE INTEGRATION | 1992/04/20 | APPROVED | Active | Private | 741.2 | Read access to find patients who have had a QA occurrence which was refered to peer review associated with a particular admission. FILE 741.2 QA OCCURRENCE REVIEW LEVEL Field 1 REVIEW LEVEL NUMBER |
|||
| 1106 | EEO/PAID - QAQ ADHOC REPORT | Routine | QUALITY ASSURANCE INTEGRATION | 1995/01/09 | APPROVED | Active | Controlled Subscription | Equal Employment Opportunity Complaint Tracking version 2.0 (EEO) will be referencing the routine ^QAQAHOC0 from within the routine ^EEOEAHOC. The neccessary QAQ* variables will be set for this call after establishing the existance of the routine ^QAQAHOC0. This reference will provide the EEO user with flexible report generation capabilities. PAID version 4.0 will be referencing the routine ^QAQAHOC0 from within routines PRSDAH1, PRSDAH2, PRSDAH3 and PRSDAH4. The neccessary QAQ* variables will be set for this call after establishing the existance of the routine ^QAQAHOC0. This reference will provide the PAID user with flexible report generation capabilities. |
QAQAHOC0 | |||
| 2073 | PATIENT REPRESENTATIVE | File | QUALITY ASSURANCE INTEGRATION | 1997/08/14 | Retired | Private | 740 |
The Patient Representation package needs to become multi-divisional. There is a QUALITY ASSURANCE SITE PARAMETER file (#740) that stores information for all the Quality Assurance packages. This file belongs to Quality Assurance Integration. Patient Representative would like to ask sites (in a pre-install patch routine) if they should be multi-divisional and if so, ensure that the hospital divisions are listed. There are existing fields to store this information. field #741.1 Multi-divisional Facility field #741.11 Hospital Division (multiple) |
||||
| 2163 | DBIA2163 | File | QUALITY ASSURANCE INTEGRATION | 1997/12/09 | APPROVED | Active | Private | 740 | Requesting permission to add two new fields in QA Site Paramter file (#740) to store whether or not the station is multi-divisional for the Incident Reporting package (namespace QAQ), and if yes, the names of the Medical Centers within the NDBI Integration Group. |
|||
| 2244 | PATIENT REPRESENTATIVE | File | QUALITY ASSURANCE INTEGRATION | 1997/12/04 | Retired | Private | 740 | I am the developer for the Quality Assurrance packages. I had previouly gotten an agreement to use two fields in the QA Site Parameter file (#740) to keep multi-divisional information fot the Patient Representative package. The Integration agreement is #2073. File 740 is part of the Integration Module. Both of these packages are in the Quality Assurrance group, the agreements are to keep a documentation trail. It turns out that the two fields in the agreement (741.1 and 741.11) are on the "OS" nodes, which are still being used by some stations for Occurrance Screening. I have decided to create comparable fields on the "QAC" nodes to provide the same functionality. The new fields are #749 MULTI-DIVISIONAL PAT REP FACILITY #750 PAT REP HOSPITAL DIVISION |
||||
| 3061 | QAC ROLLUP FIELDS | File | QUALITY ASSURANCE INTEGRATION | 2000/03/09 | Withdrawn | Private | 740 | QAC Last Record field is being created to allow the Patient Representative package (QAC) to keep track of the last record sent to the national database. It is field #753. QAC Rollup Task field is being created to hold the task number, at a site, of the currently scheduled run of the QAC Data Rollup. The code will check, before re-tasking the job, that the task has not already been scheduled. It is field #754. |