source: WorldVistAEHR/trunk/r/REGISTRATION-DGQE-DG-DPT-GRPX-VAD-VAF-VAS-VAT-VAU--VA-VIC--DGBT--DGJ--DGYA--VALM/DGYPSDE1.m@ 1259

Last change on this file since 1259 was 613, checked in by George Lilly, 15 years ago

initial load of WorldVistAEHR

File size: 4.3 KB
Line 
1DGYPSDE1 ;ALB/MJK/LSM - DGYP Global Estimator ; 03/19/2004
2 ;;5.3;REGISTRATION;**568**;Aug 13, 1993
3 ;
4INTRO ; -- display text
5 W @IOF
6 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
7 Q
8 ;
9MAIL ; -- put in mm
10 W !
11 S DIR(0)="Y",DIR("A")="Place above text in a Mailman Message",DIR("B")="No"
12 D ^DIR K DIR G MAILQ:'Y
13 K ^UTILITY("DGYPEST",$J)
14 F I=1:1 S X=$P($T(TEXT+I),";;",2) Q:X="END" S ^UTILITY("DGYPEST",$J,I,0)=X
15 S XMSUB="SCE Global Estimator",XMDUZ=.5,XMY(DUZ)="",XMTEXT="^UTILITY(""DGYPEST"",$J,"
16 D ^XMD W !,"...mailed"
17MAILQ K XMY,XMDUZ,XMTEXT,XMSUB,^UTILITY("DGYPEST",$J)
18 Q
19 ;
20TEXT ;
21 ;; *** ^SCE & ^SDD(409.42) Global Estimators ***
22 ;;
23 ;;Purpose:
24 ;;--------
25 ;;In previous versions of PIMS, a patient's outpatient information has
26 ;;been stored in various files in the VistA database. With the
27 ;;requirement to check out all outpatient encounters, it was necessary
28 ;;to consolidate much of the common outpatient information into one
29 ;;outpatient encounter file.
30 ;;
31 ;;In PIMS v5.3, the data will reside in the new OUTPATIENT
32 ;;ENCOUNTER(#409.68) file as well as in the old data structures.
33 ;;This file will hold encounter data for all checked out encounters.
34 ;;This will include information from the following:
35 ;; o appointments: SDAPI - Scheduling API
36 ;; o add/edits: ^SDV
37 ;; o dispositions: ^DPT(patient,"DIS",date/time)
38 ;;
39 ;;The MUMPS global for this file is ^SCE.
40 ;;
41 ;;
42 ;;Also, as part of the check out process, questions regarding
43 ;;whether the encounter was related to a service connected disability,
44 ;;agent orange, ionization or environmental contaminants from the
45 ;;Persian Gulf war, will be asked when appropriate.
46 ;;
47 ;;This data will be stored in the new OUTPATIENT CLASSIFICATION(#409.42)
48 ;;file in the ^SDD(409.42) global.
49 ;;
50 ;;
51 ;;The purpose of this utility is the following:
52 ;; 1. estimate a one year rate of growth for
53 ;; ^SCE using as a base the encounter data
54 ;; for the previous 365 days
55 ;;
56 ;; 2. estimate a one year rate of growth for
57 ;; ^SDD(409.42) using as a base the encounter data
58 ;; for the previous 365 and the patient demographic
59 ;; information
60 ;;
61 ;;Using these estimates, you can make a better determination
62 ;;as to where to place this new ^SCE global and how large the
63 ;;existing ^SDD global will grow.
64 ;;
65 ;;
66 ;;
67 ;;Algorithms:
68 ;;-----------
69 ;;1. Outpatient Encounters - ^SCE:
70 ;;
71 ;;This utility will scan your site's encounter database for
72 ;;the previous 365 days. It will count the number of appointments,
73 ;;add/edits and dispositions.
74 ;;
75 ;;Appointments that were cancelled or no-showed are not included
76 ;;in the calculations. Dispositions with a status of 'APPLICATION
77 ;;WITHOUT EXAM' are also not included.
78 ;;
79 ;;After obtaining these counts, they will be applied against
80 ;;the estimated block size needed for each type of encounter.
81 ;;Each type of encounter is estimated to use .16 1K blocks.
82 ;;
83 ;;
84 ;;2. Outpatient Classifications - ^SDD(409.42):
85 ;;The classifications estimate looks at the patient's demographic
86 ;;data as it scans the outpatient encounter database in #1 above.
87 ;;If the demographic data indicates a classification question
88 ;;would have been required for the encounter then a counter for the
89 ;;specific classification is incremented.
90 ;;
91 ;;For example, if the patient is a service connected veteran, the
92 ;;SC counter will be incremented.
93 ;;
94 ;;After obtaining these counts, they will be applied against
95 ;;the estimated block size needed for each type of classification.
96 ;;Each type of classification is estimated to use .08 1K blocks.
97 ;;
98 ;;NOTE: Encounters with stop codes 104 thru 170 do not, at this time,
99 ;; require any classification questions to be asked. As a result,
100 ;; they are not included in the classification counts.
101 ;;
102 ;;
103 ;;3. The estimation algorithm takes into account the following factors:
104 ;; o pointer blocks needed
105 ;; o blocks needed for actual data
106 ;; o blocks needed for cross references
107 ;;
108 ;; Also, the algorithm is based on a global efficiency of 74%.
109 ;;
110 ;;
111 ;;
112 ;;Results Reporting:
113 ;;------------------
114 ;;After the estimations are calculated, the results will be
115 ;;reported to the user via a MailMan message.
116 ;;END
Note: See TracBrowser for help on using the repository browser.