Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All
Print Page as PDF
Global: ^DG(48

Package: Registration

Global: ^DG(48


Information

FileMan FileNo FileMan Filename Package
48 MAS RELEASE NOTES Registration

Description

Directly Accessed By Routines, Total: 3

Package Total Routines
Registration 3 DGNOTE    DGVPP    DPTVPT    

Accessed By FileMan Db Calls, Total: 2

Package Total Routines
Registration 2 DGNOTE    DPTVPT    

Pointed To By FileMan Files, Total: 1

Package Total FileMan Files
Registration 1 MAS RELEASE NOTES(#48)[#48.08(.02)]    

Pointer To FileMan Files, Total: 2

Package Total FileMan Files
Registration 2 MAS RELEASE NOTES(#48)[#48.08(.02)]    MAS MODULE(#48.5)[#48.016(.02)#48.02(.02)#48.04(.02)#48.06(.02)]    

Fields, Total: 49

Field # Name Loc Type Details
.01 VERSION NUMBER 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$S($L(X)>6:1,$L(X)<1:1,'+$E(X):1,1:0) X I $D(X) S DINUM=X
  • LAST EDITED:  JUN 25, 1988
  • HELP-PROMPT:  ENTER ADT VERSION NUMBER
  • DESCRIPTION:  
    This is the MAS Version number being distributed.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  48^B
    1)= S ^DG(48,"B",$E(X,1,30),DA)=""
    2)= K ^DG(48,"B",$E(X,1,30),DA)
2 NOTIFICATION MESSAGE SENT 0;2 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 03, 1987
  • DESCRIPTION:  
    If a message was sent to the ISC the date last sent.
3 TRANSMISSION METHOD 0;3 SET
************************REQUIRED FIELD************************
  • 'L' FOR LETTER;
  • 'M' FOR MAILMAN MESSAGE;

  • LAST EDITED:  JUN 04, 1987
  • DESCRIPTION:  
    Was notification made via LETTER or MAILMAN message.
4 SCHEDULING RELEASE TOO 0;4 SET
************************REQUIRED FIELD************************
  • '1' FOR YES;
  • '0' FOR NO;

  • LAST EDITED:  JUN 05, 1987
  • DESCRIPTION:  
    Was the scheduling package released with this version.
5 SCHEDULING VERSION 0;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999)!(X<1)!(X?.E1"."5N.N) X
  • LAST EDITED:  JUN 05, 1987
  • HELP-PROMPT:  TYPE A NUMBER BETWEEN 1 AND 999
  • DESCRIPTION:  
    If a scheduling release was included with this installation what was the version number?
6 VERSION REQUIRED TO INSTALL 0;6 NUMBER
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:+X'=X!(X>999)!(X<1)!(X?.E1"."5N.N) X
  • LAST EDITED:  JUN 05, 1987
  • HELP-PROMPT:  TYPE A NUMBER BETWEEN 1 AND 999
  • DESCRIPTION:  
    What version of MAS is required in order to install this version.
7 RELEASE DATE 0;7 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 05, 1987
  • DESCRIPTION:  
    Date of this release from the Albany ISC.
  • CROSS-REFERENCE:  48^AR^MUMPS
    1)= S ^DG(48,"AR",9999999-X,DA)=""
    2)= K ^DG(48,"AR",9999999-X,DA)
10 OPENING COMMENTS C;0 WORD-PROCESSING #48.01

  • DESCRIPTION:  
    Opending comments word-processing field to explain briefly what version of MAS Release Notes are for and any outstanding issues involved.
15 NEW OPTIONS NO;0 Multiple #48.02 48.02

  • DESCRIPTION:  
    This multiple contains all new MAS menu options associated with the Version noted.
16 NEW SECURITY KEYS NK;0 Multiple #48.016 48.016

  • DESCRIPTION:  
    A multiple containing any new Security Keys associated with Version number noted.
17 NEW MAIL GROUPS MG;0 Multiple #48.017 48.017

  • DESCRIPTION:  
    Multiple containing any new mail groups associated with Version number noted.
20 CHANGED OPTIONS CO;0 Multiple #48.04 48.04

  • DESCRIPTION:  
    Multiple containing any changed menu options associated with Version number noted.
25 DELETED OPTIONS DO;0 Multiple #48.06 48.06

  • DESCRIPTION:  
    Multiple containing any deleted menu options associated with Version number noted.
30 NEW ROUTINES NR;0 Multiple #48.07 48.07

  • DESCRIPTION:  
    Multiple containing any new routines associated with Version number noted.
35 OBSOLETE ROUTINE DR;0 Multiple #48.08 48.08

  • DESCRIPTION:  
    Multiple containing any obsolete routines that will be deleted as a result of changes in the current release.
40 SUGGEST MAPPING FOR ROUTINES M;0 Multiple #48.09 48.09

  • DESCRIPTION:  
    Multiple containing routines that it is recommended/suggested to map.
41 JOURNALLING RECOMMENDATIONS J;0 Multiple #48.041 48.041

  • DESCRIPTION:  
    Multiple containing information of journalling recommendations/ instructions associated with current release.
45 FILE (DD) CHANGES F;0 WORD-PROCESSING #48.045

  • DESCRIPTION:  
    Word processing field explaining and MAS File Data Dictionary changes that have occurred as a result of changes associated with the current release.
46 PTF COMMENTS P;0 WORD-PROCESSING #48.046

  • DESCRIPTION:  
    Word processing field containing comments/instructions/special items of interest/new legislation, etc. associated with the Patient Treatment File (PTF) portion of the MAS software.
47 RUG COMMENTS RU;0 WORD-PROCESSING #48.047

  • DESCRIPTION:  
    Word processing field containing comments/instructions/special items of interest/new legislation, etc. associated with the Resource Utilization Grouper (RUG) portion of the MAS software.
48 LOOKUP COMMENTS L;0 WORD-PROCESSING #48.048

  • DESCRIPTION:  
    Word processing field containing comments/instructions/related changes, etc. to the Patient (^DPT) look up.
49 BILLING COMMENTS BILL;0 WORD-PROCESSING #48.049

  • DESCRIPTION:  Word processing field containing comments/instructions/special items of interest/new legislation, etc. associated with the Billing portion of the MAS software. In a future release, all billing options, etc. will be
    transferred to the Integrated Billing package.
49.5 SCHEDULING COMMENTS SCH;0 WORD-PROCESSING #48.0495

  • DESCRIPTION:  
    Word processing field containing comments/instructions/special items of interest/new legislation, etc. associated with the Scheduling portion of the MAS software.
49.7 DISC. WORKLOAD COMMENTS DW;0 WORD-PROCESSING #48.0497

  • DESCRIPTION:  
    This field will be *'d for deletion in the MAS V5.2 release. Discretionary workload reports/options, etc. are not longer required by VACO for use in the field.
49.8 IRT COMMENTS 49.8;0 WORD-PROCESSING #48.13

  • DESCRIPTION:  
    This is a word-processing field that contains comments on new or changed functionality or special notes on the Incomplete Record Tracking Menu in the MAS package with new releases.
50 CLOSING COMMENTS C1;0 WORD-PROCESSING #48.1

  • DESCRIPTION:  
    Word processing containing any closing comments (summary) of any outstanding issues/new functionality, etc. related to the current release.
100 DG PRE-INIT START R;1 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DG namespaced pre-initialization started.
101 DG INIT START R;2 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DG namespaced intialization started.
102 DG POST-INIT START R;3 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DG namespaced post-intialization started.
103 DG INIT END R;4 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DG namespaced intialization ended.
104 DPT PRE-INIT START R;5 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DPT pre-initialization started.
105 DPT INIT START R;6 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DPT intialization started
106 DPT POST-INIT START R;7 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DPT post-initialization started.
107 DPT INIT END R;8 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the DPT initialization ended.
108 SD PRE-INIT START R;9 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 05, 1987
  • DESCRIPTION:  
    Date/time the SD namespaced pre-initialization started.
109 SD INIT START R;10 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time SD namespaced initialization started
110 SD POST-INIT START R;11 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time SD post-initialization started.
111 SD INIT END R;12 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time the SD initialization ended.
115 SPECIAL JOB STARTED R;16 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUN 18, 1987
  • DESCRIPTION:  
    Date/time any special job was started. This may not be related to all releases, just special cases.
116 SPECIAL JOB ENDED R;17 DATE
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • DESCRIPTION:  
    Date/time any special job ended. This may not be related to all releases, just special cases.
117 SPECIAL JOB2 DONE R;18 SET
************************REQUIRED FIELD************************
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  AUG 03, 1987
  • DESCRIPTION:  
    Date/time a second special job was completed.
120 MAY I INCLUDE YOUR FILE SIZES? S;1 SET
************************REQUIRED FIELD************************
  • '1' FOR YES;
  • '0' FOR NO;

  • DESCRIPTION:  
    Does user wish to have program include the sizes of their files in the output received as a result of running initializations?
121 DOCUMENTATION QUALITY S;2 SET
************************REQUIRED FIELD************************
  • '0' FOR NONE INCLUDED;
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  
    User enters the range of quality they felt the documentation sent with the package release fell into (i.e. poor, fair, good, etc.)
122 INSTALLATION GUIDE S;3 SET
************************REQUIRED FIELD************************
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  
    Quality of the installation guide received with the release, i.e. good, poor, fair, etc.
123 RELEASE NOTES S;4 SET
************************REQUIRED FIELD************************
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  
    Quality of the release notes received with the release, i.e. good, poor, fair, etc.
124 INITIALIZATION SATISFACTION S;5 SET
************************REQUIRED FIELD************************
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  How was the quality of the initialization as related to IRM. Was it poor?, fair?, etc. Did the initialization run smoothly? Were there major problems encountered? Items that may effect the quality of the initialization
    quality.
125 USER SATISFACTION S;6 SET
************************REQUIRED FIELD************************
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  
    The quality of user satisfaction. How did the users react to the installation/results of updated software? Were they pleased? Did they find many items they felt uncomfortable with? etc.
126 OVERALL SATISFACTION S;7 SET
************************REQUIRED FIELD************************
  • '1' FOR POOR;
  • '2' FOR FAIR;
  • '3' FOR GOOD;
  • '4' FOR VERY GOOD;
  • '5' FOR EXCELLENT;

  • DESCRIPTION:  
    Rank the overall satisfaction of the release, including all documentation, initializations, functionality, etc.
150 USER COMMENTS/SUGGESTIONS UC;0 WORD-PROCESSING #48.12

  • DESCRIPTION:  
    Word processing field for users to express their concerns, comments, findings, reactions to the release as a whole. Any recommendations they may have, etc.

Found Entries, Total: 1

VERSION NUMBER: 5.3    
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Found Entries  | All