INCIDENT REPORTING (141)    PACKAGE (9.4)

Name Value
NAME INCIDENT REPORTING
PREFIX QAN
DEVELOPER (PERSON/SITE) Gregory J. Cebelinski @Hines ISC
*LOWEST FILE NUMBER 513.72
*HIGHEST FILE NUMBER 742.9
DEVELOPMENT ISC Hines ISC
CLASS National
CURRENT VERSION 2.0
SHORT DESCRIPTION This package is designed to track a hospital incident.
VERSION
  1. VERSION:   2.0
    DATE DISTRIBUTED:   2005-11-19 00:00:00
    PATCH APPLICATION HISTORY:
    1. PATCH APPLICATION HISTORY:   24
      DATE APPLIED:   1997-10-28 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Delete obsolete Incident Reporting files.  Files in 742 file number range
      now being used.
      
    2. PATCH APPLICATION HISTORY:   33 SEQ #33
      DATE APPLIED:   2013-05-31 10:18:46
      APPLIED BY:   USER,SEVENTEEN
      DESCRIPTION:   
       This patch addresses 2 issues:
      a list of existing open cases by 'Case Number', 'Date of Incident' or 
      'Patient'.
       
      1.  A subscript error appears when scheduled auto email options are 
      run and entries in the QA INCIDENT REPORT (#742.4) file with a LOCAL CASE 
      STATUS (#.09) of "CLOSED", "DELETED, or "QUICK" have no value for the 
      INCIDENT (#.02). 
       
      2.  A subscript error occurs when accessing the 'Full Incident Edit' [QAN 
      INCIDENT FOLLOW-UP] option and then using a question mark '?' to view a 
      
    3. PATCH APPLICATION HISTORY:   34 SEQ #34
      DATE APPLIED:   2018-11-02 15:52:15
      APPLIED BY:   USER,FIFTYFOUR
      DESCRIPTION:   
      This patch marks MENU options "Disabled-USE Joint Patient Safety 
      Reporting-JPSR" as requested by the VHANCPS JPSR TEAM.
      
    4. PATCH APPLICATION HISTORY:   25
      DATE APPLIED:   1998-03-18 00:00:00
      APPLIED BY:   USER,ONE
    5. PATCH APPLICATION HISTORY:   27 SEQ #26
      DATE APPLIED:   1999-08-03 00:00:00
      APPLIED BY:   USER,ONE
    6. PATCH APPLICATION HISTORY:   26 SEQ #27
      DATE APPLIED:   1999-12-10 00:00:00
      APPLIED BY:   USER,ONE
    7. PATCH APPLICATION HISTORY:   28 SEQ #28
      DATE APPLIED:   2000-02-04 00:00:00
      APPLIED BY:   USER,ONE
    8. PATCH APPLICATION HISTORY:   29 SEQ #29
      DATE APPLIED:   2000-10-04 00:00:00
      APPLIED BY:   USER,ONE
    9. PATCH APPLICATION HISTORY:   30 SEQ #30
      DATE APPLIED:   2003-09-24 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      PROBLEM ADDING SECOND PATIENT
      
    10. PATCH APPLICATION HISTORY:   31 SEQ #31
      DATE APPLIED:   2003-12-31 00:00:00
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Incident reports not printing.
      
    11. PATCH APPLICATION HISTORY:   32 SEQ #32
      DATE APPLIED:   2007-09-05 00:58:03
      APPLIED BY:   USER,ONE
      DESCRIPTION:   
      Patient ID fix
      
    DATE INSTALLED AT THIS SITE:   1996-09-25 00:00:00
FILE
  1. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  2. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  3. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    SCREEN TO DETERMINE DD UPDATE:   I $D(^PRMQ(513.72,0))
  4. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
    SCREEN TO DETERMINE DD UPDATE:   I $D(^PRMQ(513.941,0))
  5. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  6. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  7. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
  8. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   NO
  9. UPDATE THE DATA DICTIONARY:   YES
    ASSIGN A VERSION NUMBER:   YES
    MAY USER OVERRIDE DD UPDATE:   NO
    DATA COMES WITH FILE:   YES
    MERGE OR OVERWRITE SITE'S DATA:   OVERWRITE
    MAY USER OVERRIDE DATA UPDATE:   NO
ENVIRONMENT CHECK ROUTINE QANIPRE
ENVIRONMENT CHECK DONE DATE 1992-10-16 10:30:36
POST-INITIALIZATION ROUTINE QANPST3
POST-INIT COMPLETION DATE 1992-10-16 10:32:13