Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Routine: DGYPSDE1

DGYPSDE1.m

Go to the documentation of this file.
  1. DGYPSDE1 ;ALB/MJK/LSM - DGYP Global Estimator ; 03/19/2004
  1. ;;5.3;REGISTRATION;**568**;Aug 13, 1993
  1. ;
  1. INTRO ; -- display text
  1. W @IOF
  1. F I=1:1 S X=$P($T(TEXT+I),";;",2) Q:X="END" W X,! I $Y>20 S DIR(0)="E" D ^DIR K DIR Q:'Y W @IOF
  1. Q
  1. ;
  1. MAIL ; -- put in mm
  1. W !
  1. S DIR(0)="Y",DIR("A")="Place above text in a Mailman Message",DIR("B")="No"
  1. D ^DIR K DIR G MAILQ:'Y
  1. K ^UTILITY("DGYPEST",$J)
  1. F I=1:1 S X=$P($T(TEXT+I),";;",2) Q:X="END" S ^UTILITY("DGYPEST",$J,I,0)=X
  1. S XMSUB="SCE Global Estimator",XMDUZ=.5,XMY(DUZ)="",XMTEXT="^UTILITY(""DGYPEST"",$J,"
  1. D ^XMD W !,"...mailed"
  1. MAILQ K XMY,XMDUZ,XMTEXT,XMSUB,^UTILITY("DGYPEST",$J)
  1. Q
  1. ;
  1. TEXT ;
  1. ;; *** ^SCE & ^SDD(409.42) Global Estimators ***
  1. ;;
  1. ;;Purpose:
  1. ;;--------
  1. ;;In previous versions of PIMS, a patient's outpatient information has
  1. ;;been stored in various files in the VistA database. With the
  1. ;;requirement to check out all outpatient encounters, it was necessary
  1. ;;to consolidate much of the common outpatient information into one
  1. ;;outpatient encounter file.
  1. ;;
  1. ;;In PIMS v5.3, the data will reside in the new OUTPATIENT
  1. ;;ENCOUNTER(#409.68) file as well as in the old data structures.
  1. ;;This file will hold encounter data for all checked out encounters.
  1. ;;This will include information from the following:
  1. ;; o appointments: SDAPI - Scheduling API
  1. ;; o add/edits: ^SDV
  1. ;; o dispositions: ^DPT(patient,"DIS",date/time)
  1. ;;
  1. ;;The MUMPS global for this file is ^SCE.
  1. ;;
  1. ;;
  1. ;;Also, as part of the check out process, questions regarding
  1. ;;whether the encounter was related to a service connected disability,
  1. ;;agent orange, ionization or environmental contaminants from the
  1. ;;Persian Gulf war, will be asked when appropriate.
  1. ;;
  1. ;;This data will be stored in the new OUTPATIENT CLASSIFICATION(#409.42)
  1. ;;file in the ^SDD(409.42) global.
  1. ;;
  1. ;;
  1. ;;The purpose of this utility is the following:
  1. ;; 1. estimate a one year rate of growth for
  1. ;; ^SCE using as a base the encounter data
  1. ;; for the previous 365 days
  1. ;;
  1. ;; 2. estimate a one year rate of growth for
  1. ;; ^SDD(409.42) using as a base the encounter data
  1. ;; for the previous 365 and the patient demographic
  1. ;; information
  1. ;;
  1. ;;Using these estimates, you can make a better determination
  1. ;;as to where to place this new ^SCE global and how large the
  1. ;;existing ^SDD global will grow.
  1. ;;
  1. ;;
  1. ;;
  1. ;;Algorithms:
  1. ;;-----------
  1. ;;1. Outpatient Encounters - ^SCE:
  1. ;;
  1. ;;This utility will scan your site's encounter database for
  1. ;;the previous 365 days. It will count the number of appointments,
  1. ;;add/edits and dispositions.
  1. ;;
  1. ;;Appointments that were cancelled or no-showed are not included
  1. ;;in the calculations. Dispositions with a status of 'APPLICATION
  1. ;;WITHOUT EXAM' are also not included.
  1. ;;
  1. ;;After obtaining these counts, they will be applied against
  1. ;;the estimated block size needed for each type of encounter.
  1. ;;Each type of encounter is estimated to use .16 1K blocks.
  1. ;;
  1. ;;
  1. ;;2. Outpatient Classifications - ^SDD(409.42):
  1. ;;The classifications estimate looks at the patient's demographic
  1. ;;data as it scans the outpatient encounter database in #1 above.
  1. ;;If the demographic data indicates a classification question
  1. ;;would have been required for the encounter then a counter for the
  1. ;;specific classification is incremented.
  1. ;;
  1. ;;For example, if the patient is a service connected veteran, the
  1. ;;SC counter will be incremented.
  1. ;;
  1. ;;After obtaining these counts, they will be applied against
  1. ;;the estimated block size needed for each type of classification.
  1. ;;Each type of classification is estimated to use .08 1K blocks.
  1. ;;
  1. ;;NOTE: Encounters with stop codes 104 thru 170 do not, at this time,
  1. ;; require any classification questions to be asked. As a result,
  1. ;; they are not included in the classification counts.
  1. ;;
  1. ;;
  1. ;;3. The estimation algorithm takes into account the following factors:
  1. ;; o pointer blocks needed
  1. ;; o blocks needed for actual data
  1. ;; o blocks needed for cross references
  1. ;;
  1. ;; Also, the algorithm is based on a global efficiency of 74%.
  1. ;;
  1. ;;
  1. ;;
  1. ;;Results Reporting:
  1. ;;------------------
  1. ;;After the estimations are calculated, the results will be
  1. ;;reported to the user via a MailMan message.
  1. ;;END