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

ACDEDE1.m

Go to the documentation of this file. 
  1. ACDEDE1 ;IHS/ADC/EDE/KML - DOCUMENTATION ON V4;
  1.  ;;4.1;CHEMICAL DEPENDENCY MIS;;MAY 11, 1998
  1.  ;
  1. 0 ;Met with Wilbur Woodis for two days and discussed what needed to be
  1.  ;done to CDMS.
  1.  ;
  1. 1 ;Wrote a driver routine for data entry add mode which preasks for key
  1.  ;pieces of information such as component code/type, primary provider,
  1.  ;type contact, and patient, then generates the appropriate visit by
  1.  ;calling FILE^DICN.  Entries are generated in subordinate files by
  1.  ;input templates using file shifts.  The routines does logical checks
  1.  ;such as insuring there is an INITIAL prior to entering other types
  1.  ;of services.  There are other logical checks.  The sequence the items
  1.  ;are asked for is based on the normal mode of processing forms.  Forms
  1.  ;are grouped by component code/type, then by primary provider, then
  1.  ;by type contact and patient if appropriate.
  1.  ;
  1. 2 ;Display the visit history for a patient if an illogical entry is
  1.  ;attempted.
  1.  ;
  1. 3 ;Display the client service history when a client service visit is
  1.  ;generated or selected.
  1.  ;
  1. 4 ;Deleted the option to add additional client services.  This is no
  1.  ;longer needed because of the driver in 1 above.  If there is no
  1.  ;client service one is generated.  If one already exists the new
  1.  ;client services are attached to the existing visit.
  1.  ;
  1. 5 ;Modified the data entry routine for client categories to use the
  1.  ;patient demographic logic developed in the driver in 1 above.  Also
  1.  ;added component code/type to the client category dictionary so the
  1.  ;patients being added could be checked for the existence of an INITIAL
  1.  ;type contact.
  1.  ;
  1. 6 ;Changed the way the autoduplication of client services works.  It
  1.  ;will now duplicate a new client service visit with or without any
  1.  ;associated client services.  It will now duplicate additional cleint
  1.  ;services added to a visit at a later time.
  1.  ;
  1. 7 ;Added a new option to display the visit history of selected patients.
  1.  ;
  1. 8 ;Developed a technique to keep track of patients who are temporarily
  1.  ;absent without requiring a transfer or discharge.  Added TP and RTP
  1.  ;to CDMIS SERVICE file.
  1.  ;
  1. 9 ;Added OTHER to CDMIS SERVICE file.
  1.  ;
  1. 10 ;Deleted 10 NOT IN USE FOR NOW from CDMIS LOCATION file.  This will
  1.  ;require a post-init for the next install.
  1.  ;
  1. 11 ;Changed 30 PHYSICAL ABUSE SPOUSE to 30 DOMESTIC VIOLENCE in the CDMIS
  1.  ;PROBLEM file.
  1.  ;
  1. 12 ;Deleted 1 NOT USED, 98 NO DRUGS, 99 NO ALCOHOL, and N NOT USED from
  1.  ;CDMIS DRUG TABLE.  This will require a post-init for the next
  1.  ;install.
  1.  ;Add 20 ALCOHOL to above list.
  1.  ;
  1. 13 ;Changed VAA to VA & Veterans Admin in the CDMIS COMPONENT file.
  1.  ;
  1. 14 ;Changed set in file 9002171 field 19 from
  1.  ;NO FURTHER SVCS REQUIRED,THIS COMP/PROG to
  1.  ;NO FURTHER SVCS REQUIRED/COMPLETED TREATMENT
  1.  ;
  1. 15 ;Deleted 1 1 and 10 (NOT TO BE USED) from the CDMIS PREVENTION
  1.  ;ACTIVITIES file.  This will require a post-init for the next install.
  1.  ;
  1. 16 ;Add 18 TRANSPORTATION to the CDMIS PREVENTION ACTIVITIES file.
  1.  ;
  1. 17 ;Standardized all component type sets to be:
  1.  ; A = ADULT
  1.  ; Y = YOUTH
  1.  ; M = MIXED (ADULT&YOUTH)
  1.  ; F = FAMILY
  1.  ; E = ELDERLY ONLY
  1.  ; W = WOMEN ONLY
  1.  ; S = STAFF
  1.  ;
  1. 170 ;Modified ^ACDAGRG (the routine that computes the age range) and all
  1.  ;appropriate dictionaries to: 0-13=1, 14-18=2, 19-24=3, 25-34=4,
  1.  ;                            35-44=5, 45-54=6, 55-64=7, 65-74=8, 75+
  1.  ;This will require a recomputation during the v4 postinit.
  1.  ;
  1. 18 ;Resolved problem at PIMC where CDMIS operator could not select the
  1.  ;appropriate patient because he was an employee of PIMC.
  1.  ;
  1. 19 ;Resolved problem with Terry Nix in Alaska where he could not do an
  1.  ;extract of version 4 CDMIS data.
  1.  ;
  1. 20 ;Added functionality to allow user to edit records just generated.
  1.  ;Can edit init/info/fu, trans/disc/close, and client svcs.