| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | version number(+) | 0;1 | FREE TEXT | B | This is the MAS Version number being distributed. | |
| 2 | notification message sent(+) | 0;2 | DATE-TIME | If a message was sent to the ISC the date last sent. | ||
| 3 | transmission method(+) | 0;3 | SET OF CODES | L:LETTER M:MAILMAN MESSAGE | Was notification made via LETTER or MAILMAN message. | |
| 4 | scheduling release too(+) | 0;4 | BOOLEAN | 1:YES 0:NO | Was the scheduling package released with this version. | |
| 5 | scheduling version | 0;5 | NUMERIC | If a scheduling release was included with this installation what was the version number? | ||
| 6 | version required to install(+) | 0;6 | NUMERIC | What version of MAS is required in order to install this version. | ||
| 7 | release date(+) | 0;7 | DATE-TIME | Date of this release from the Albany ISC. | ||
| 10 | opening comments | C;0 | WORD-PROCESSING | 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 | This multiple contains all new MAS menu options associated with the Version noted. | |
| 16 | new security keys | NK;0 | MULTIPLE | 48.016 | A multiple containing any new Security Keys associated with Version number noted. | |
| 17 | new mail groups | MG;0 | MULTIPLE | 48.017 | Multiple containing any new mail groups associated with Version number noted. | |
| 20 | changed options | CO;0 | MULTIPLE | 48.04 | Multiple containing any changed menu options associated with Version number noted. | |
| 25 | deleted options | DO;0 | MULTIPLE | 48.06 | Multiple containing any deleted menu options associated with Version number noted. | |
| 30 | new routines | NR;0 | MULTIPLE | 48.07 | Multiple containing any new routines associated with Version number noted. | |
| 35 | obsolete routine | DR;0 | MULTIPLE | 48.08 | 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 | Multiple containing routines that it is recommended/suggested to map. | |
| 41 | journalling recommendations | J;0 | MULTIPLE | 48.041 | Multiple containing information of journalling recommendations/ instructions associated with current release. | |
| 45 | file (dd) changes | F;0 | WORD-PROCESSING | 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 | 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 | 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 | Word processing field containing comments/instructions/related changes, etc. to the Patient (^DPT) look up. | ||
| 49 | billing comments | BILL;0 | WORD-PROCESSING | 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 | 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 | 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 | 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 | 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-TIME | Date/time the DG namespaced pre-initialization started. | ||
| 101 | dg init start(+) | R;2 | DATE-TIME | Date/time the DG namespaced intialization started. | ||
| 102 | dg post-init start(+) | R;3 | DATE-TIME | Date/time the DG namespaced post-intialization started. | ||
| 103 | dg init end(+) | R;4 | DATE-TIME | Date/time the DG namespaced intialization ended. | ||
| 104 | dpt pre-init start(+) | R;5 | DATE-TIME | Date/time the DPT pre-initialization started. | ||
| 105 | dpt init start(+) | R;6 | DATE-TIME | Date/time the DPT intialization started | ||
| 106 | dpt post-init start(+) | R;7 | DATE-TIME | Date/time the DPT post-initialization started. | ||
| 107 | dpt init end(+) | R;8 | DATE-TIME | Date/time the DPT initialization ended. | ||
| 108 | sd pre-init start(+) | R;9 | DATE-TIME | Date/time the SD namespaced pre-initialization started. | ||
| 109 | sd init start(+) | R;10 | DATE-TIME | Date/time SD namespaced initialization started | ||
| 110 | sd post-init start(+) | R;11 | DATE-TIME | Date/time SD post-initialization started. | ||
| 111 | sd init end(+) | R;12 | DATE-TIME | Date/time the SD initialization ended. | ||
| 115 | special job started(+) | R;16 | DATE-TIME | 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-TIME | Date/time any special job ended. This may not be related to all releases, just special cases. | ||
| 117 | special job2 done(+) | R;18 | BOOLEAN | 0:NO 1:YES | Date/time a second special job was completed. | |
| 120 | may i include your file sizes?(+) | S;1 | BOOLEAN | 1:YES 0:NO | 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 OF CODES | 0:NONE INCLUDED 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | 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 OF CODES | 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | Quality of the installation guide received with the release, i.e. good, poor, fair, etc. | |
| 123 | release notes(+) | S;4 | SET OF CODES | 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | Quality of the release notes received with the release, i.e. good, poor, fair, etc. | |
| 124 | initialization satisfaction(+) | S;5 | SET OF CODES | 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | 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 OF CODES | 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | 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 OF CODES | 1:POOR 2:FAIR 3:GOOD 4:VERY GOOD 5:EXCELLENT | Rank the overall satisfaction of the release, including all documentation, initializations, functionality, etc. | |
| 150 | user comments/suggestions | UC;0 | WORD-PROCESSING | Word processing field for users to express their concerns, comments, findings, reactions to the release as a whole. Any recommendations they may have, etc. |
Not Referenced