| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .001 | number | 11 | There is only one 'number' in the MAS Parameters File at this time, and that is the number 'one' denoting there is only on MAS Parameter. The labels are subfields of this one parameter. | |||
| .01 | one(+) | 0;1 | NUMERIC | B | 'One' designates the 'one' MAS Parameter. There can only be one set of parameters. | |
| 3 | hemodialysis ward | 0;4 | POINTER | 42 | Does your facility have a Hemodialysis Ward? | |
| 4 | system timeout | 0;5 | NUMERIC | Enter number of seconds to wait for user to respond to prompts (at least 10 seconds). Enter 99999 if you wish no system timeout. | ||
| 5.5 | days to maintain g&l corr | 0;29 | NUMERIC | Enter the number of days you want to save G&L corrections in the system (between 14 and 365); corrections older than this number are deleted by the system when G&L Auto-Recalculation runs. Leave blank if you wish to maintain the complete file. Up to 90 days is recommended. | ||
| 6 | time for late disposition(+) | 0;7 | NUMERIC | Enter the number of hours you want an active registration to remain open before the disposition is considered late (between 0 and 240). | ||
| 7 | supplemental 10/10 | 0;8 | SET OF CODES | 1:DO NOT PRINT WITH 10 10 0:PRINT WITH 10 10 | Do you wish Supplemental 10-10 to be printed wtih 10-10? | |
| 8 | print drug profiles with 10-10 | 0;17 | BOOLEAN | 0:NO 1:YES | Do you wish to have printing of drug profiles prompted with 10-10 printing? | |
| 9 | default ptf message printer | 0;19 | FREE TEXT | If you answered YES to the 'PRINT PTF MESSAGES?' prompt select the default device to which these message should print. This device will be used in cases where a specific device is not entered for the individual facility/division using the 'DEVICE SELECTION' option of the SYSTEM DEFINITION MENU. | ||
| 9.5 | print ptf messages? | 0;31 | BOOLEAN | 0:NO 1:YES | Enter '1' if you wish to print PTF messages upon admission, change of treating specialty or deletion of admission, treating specialty transfer, discharge or 501 movement. Enter '0' if you DO NOT wish PTF messages to print. | |
| 9.6 | automatic ptf messages? | 0;40 | BOOLEAN | 0:NO 1:YES | This field indicates whether the site wants to automatically generate PTF messages as part of normal ADT processing. If 'YES' than entries into the PTF MESSAGE file will occur. If 'NO' than no PTF messages will be generated during ADT activities. | |
| 10 | earliest date for g&l | GL;1 | DATE-TIME | Enter the earliest date for G&L to be run on. The day previous to this will be used for ward bed status data initialization. | ||
| 11 | multidivision med center?(+) | GL;2 | BOOLEAN | 0:NO 1:YES | Is your facility multi-divisional? | |
| 12 | medical center name(+) | GL;3 | POINTER | 40.8 | Enter name of primary facility for which you are defining parameters. | |
| 13 | affiliated(+) | GL;4 | SET OF CODES | 0:NO 1:YES 2:INTERMEDIATE | Is your facility affiliated with a teaching facility? | |
| 14 | *honeywell site | H;1 | BOOLEAN | Y:YES N:NO | This field is currently unused by the MAS package and will be deleted in a future release of MAS. It was previously used to determine whether the honeywell software should be utilized or not. | |
| 15 | nursing home wards? | 0;20 | BOOLEAN | 0:NO 1:YES | Does your site have nursing home wards? | |
| 16 | domiciliary wards? | 0;21 | BOOLEAN | 0:NO 1:YES | Does your medical center have domiciliary wards? | |
| 17 | use hinq inquiry? | 0;27 | BOOLEAN | 1:YES 0:NO | Determines if HINQ inquiry can be made on registration. | |
| 18 | embossers on-line | 0;28 | BOOLEAN | 1:YES 0:NO | Do you wish to have embossing of data card prompted during registration options? | |
| 19 | use closest printer | 0;30 | BOOLEAN | 1:YES 0:NO | Do you wish closest printer to be default for 10-10s, routing slips and pharmacy profiles? | |
| 25 | default code sheet printer | 0;25 | FREE TEXT | If a 'Default Code Sheet Printer' is defined, AMIS code sheets can be generated when AMIS(s) are generated. The Code Sheets created will be printed on the default printer. | ||
| 32 | view check out info default(+) | 0;32 | BOOLEAN | 0:NO 1:YES | During the editing of a disposition, should the user default answer be 'Yes' or 'No' to the following prompt: 'Do you wish to see the check out screen?' | |
| 33 | days to maintain sensitivity | 0;33 | NUMERIC | Enter number of days for which sensitivity data must be maintained on line before purging is permitted. | ||
| 34 | show status screen(+) | 0;34 | BOOLEAN | 0:NO 1:YES | Do you want the MAS Status Screen to be displayed to users upon entering the ADT Menu? | |
| 37 | consistency checker on? | 0;37 | BOOLEAN | 0:NO 1:YES | Do you wish to turn on the automatic Consistency Checker? If YES, data will be checked in accordance with parameters set through the Determine Consistencies to Check/Don't Check option of the Consistency Supervisor Menu. | |
| 38 | abbreviated patient inquiry? | 0;38 | BOOLEAN | 1:YES 0:NO | Do you wish an abbreviated patient inquiry to be displayed through the Patient Inquiry Option? An abbreviated inquiry will include the following: name, SSN, date of birth, address, temporary address, means test status, eligibility status, admission and appointment enrollment information. Items such as religion, claim number and period of service will be excluded. | |
| 39 | ask device in registration | 0;39 | BOOLEAN | 1:YES 0:NO | Answering YES will force the DEVICE: prompt at the beginning of registration the first time through and will set the 1010, routing sheet, and profile printer to this device. This takes precedence over all devices defined as default printers or closet printer. | |
| 41 | run co-pay software?(+) | 0;41 | BOOLEAN | 1:YES 0:NO | This will prevent the Co-Pay menus and routines from being invoked by the Registration software. | |
| 42 | print health summary? | 0;42 | BOOLEAN | 0:NO 1:YES | By answering 'YES' the user will be prompted to print a Health Summary at the end of the Registration process and during the 10/10 Print without New Registration option. NOTE: Unless HEALTH SUMMARY v2.5 patch #3 (or higher) has been loaded the user will not be prompted to print a Health Summary. | |
| 43 | default health summary | 0;43 | POINTER | 142 | When the user is prompted to print a Health Summary type in Registration, this field contains the default. NOTE: Unless the MAS PARAMETER, 'PRINT HEALTH SUMMARY?', has been answered 'YES', this has no effect. | |
| 44 | choice of drug profile type? | 0;44 | BOOLEAN | 1:YES 0:NO | If YES is entered for the PRINT DRUG PROFILES WITH 10-10 field, answering YES to this field will offer the user a choice between the Action and Informational Drug Profiles. Note: Unless the PRINT DRUG PROFILES WITH 10-10 has been answered 'YES', this field will have no effect. | |
| 45 | default type of drug profile | 0;45 | SET OF CODES | A:ACTION I:INFORMATIONAL | This field is irrelevant unless the PRINT DRUG PROFILES WITH 10-10 field has been answered 'YES'. If the user has a choice of Drug Profiles (when CHOICE OF DRUG PROFILE TYPE? is YES) this field defines the default. If the user does not have a choice of Drug Profiles, this field defines the type of Drug Profile (Action or Informational). | |
| 46 | days to update medicaid | 0;46 | NUMERIC | After this number of days without updating the DATE MEDICAID LAST ASKED field an inconsistency will be created. The default is 365 days. | ||
| 47 | print encounter form at reg. | 0;47 | BOOLEAN | 0:NO 1:YES | Answering "YES" will have the prompt Print Encounter Form be asked at Registration. If the encounter form is said to be printed, the clinic(s) to print the encounter forms will be asked. | |
| 48 | default ef printer | 0;48 | FREE TEXT | This field contains the name of the default printer that will print encounter forms at registration. | ||
| 50 | g&l started | GLS;1 | DATE-TIME | The date/time the Gains and Losses Sheet was started by a user through the ADT Outputs menu option. | ||
| 52 | recalc started | GLS;2 | DATE-TIME | The date/time G&L recalculation was started. A user would recalc a G&L for past dates normally. | ||
| 53 | recalc up to | GLS;3 | DATE-TIME | Date G&L recalculation has reached cleared when recalc is finished. | ||
| 54 | ztsk(recalc) | GLS;4 | NUMERIC | The task number of the G&L recalculation job running. | ||
| 55 | scheduled(recalc) | GLS;5 | DATE-TIME | The date/time the G&L recalculation is scheduled to run. It is a nightly background job usually set to run sometime after midnight each day. | ||
| 56 | cpu(recalc) | GLS;6 | FREE TEXT | CPU recalc was started from | ||
| 57 | auto recalc last started | GLS;7 | DATE-TIME | The date/time that Auto Recalc was last started for the G&L stats. | ||
| 58 | cpu(auto recalc) | GLS;8 | FREE TEXT | CPU which last ran auto recalc | ||
| 59 | auto recalc finished | GLS;9 | DATE-TIME | |||
| 60 | auto recalc back to | GLS;10 | DATE-TIME | When the G&L Auto Recalc last ran, this is the date it went back to for recalculation of the stats. | ||
| 61 | g&l last run | GLS;11 | DATE-TIME | Time G&L was run last. | ||
| 70 | registration template (local) | 0;35 | POINTER | .402 | A site may need to capture certain registration data in a format other than that of the distributed registration screens. It may do so by creating a local registration screen (through a FileMan template) specifying that data in the PATIENT file they wish to capture. The template name should be specified at this prompt. This screen will then be prompted during the registration or load/edit process at the end of the other registration screens. | |
| 76 | use high intensity on screens? | 0;36 | BOOLEAN | 1:YES 0:NO | Should high intensity be used for those options in MAS which allow it? This feature works in conjunction with the Registration and MCCR screens to signify to users that data which may/may not be edited. Under certain circumstances some screens or individual data groups may only be edited by selected users. When this feature is turned on, those screens and/or data group numbers which a specific user may edit will be 'highlighted' on their terminal but not 'highlighted' to those users who may not edit the screens/data groups. | |
| 77 | exclude which terminal types? | TERM;0 | MULTIPLE | 43.077 | If the USE HIGH INTENSITY ON SCREENS field has been set to YES, you may wish to exclude it from being used on certain terminal types. If so, at this prompt you should specify the terminal type(s) which should not use high intensity. This field allows you to specify multiple terminal types. You will be returned to it repeatedly until no more entries are made. | |
| 80 | consistency purge started | CON;1 | DATE-TIME | The date the purging of the INCONSISTENT DATA file was started. | ||
| 81 | consistency purge last ran | CON;2 | DATE-TIME | The date the INCONSISTENT DATA purge last completed. | ||
| 82 | consistency rebuild started | CON;3 | DATE-TIME | The date the INCONSISTENT DATA file was started rebuilding. | ||
| 83 | consistency rebuild last ran | CON;4 | DATE-TIME | The date the INCONSISTENT DATA file last completed rebuilding. | ||
| 84 | consistency update started | CON;5 | DATE-TIME | The date updating of existing data in the INCONSISTENT DATA file was last started. | ||
| 85 | consistency update last ran | CON;6 | DATE-TIME | The date updating of existing data in the INCONSISTENT DATA file last completed running. | ||
| 86 | overdue absence search date(+) | CON;7 | DATE-TIME | Date the overdue absence list was run. An overdue absence list produces those veterans who have been placed on either AA<96 hrs. or AA and have not returned on the date entered as their return date. | ||
| 90 | provider conversion | PCON;0 | MULTIPLE | 43.02 | This Multiple will contain parameters used for the conversion of MAS files from file 3, 6, and 16 to file 200. | |
| 91 | provider conversion log | PCL;0 | WORD-PROCESSING | This field contains a list of all entries that failed to be converted during the Provider Conversion. The contents of this field will be used to generate a Mailman message at the end of the | ||
| 205 | scheduling version | SCLR;5 | NUMERIC | This is the Version number of the currently loaded Scheduling DHCP software. | ||
| 210 | scheduling archive date | SDAR;0 | MULTIPLE | 43.05 | This field contains the dates, status, and summary information for the Scheduling archive process. | |
| 212 | appt search threshold | SCLR;12 | NUMERIC | Enter the number of days in the past that the 'Appointment Management' option should initially search for appointments. When the user selects a patient, this parameter will automatically be used to search that many days in the past for appointments. When a clinic is selected, this number will be used to calculate the default beginning date. The user is prompted for a beginning and ending date when a clinic is selected. If this field is not entered, then the system will use 2 days. | ||
| 213 | patient or clinic | SCLR;13 | VARIABLE-POINTER | 2, 44 | This field definition is used by the 'Appointment Management' option. The option obtains a patient or clinic when using the FileMan Reader. This field is specified in the Reader call. No data needs to be set in this field. | |
| 215 | appt. update mail group | SCLR;15 | POINTER | 3.8 | This is the name of the Mail Group which should be notified whenever the Appointment Status Update job has been completed. | |
| 216 | npcdb mail group | SCLR;16 | POINTER | 3.8 | This is the name of the Mail Group which should be notified whenever the nightly NPCDB job has been completed. | |
| 217 | late activity mail group | SCLR;17 | POINTER | 3.8 | This is the name of the Mail Group which should be notified whenever there is late entry/edit of NPCDB related information. 'Late entry' is defined as information entered after the workload close out date has passed. For example, if an appointment is made after the close out date has passed for the appointment date then the members of this mail group will receive a message. | |
| 223 | date check out required(+) | SCLR;23 | DATE-TIME | This field indicates the date the site must start checking out appointments, stop code additions (add/edits) and registrations (1010 and unscheduled). Once v5.3 is released then this date will be Oct. 1, 1993. However, for alpha and beta testing, this date needs to be set before 10/1/93. | ||
| 224 | allow up-arrow out of class. | SCLR;24 | BOOLEAN | 0:NO 1:YES | Enter 'YES' to allow users to up-arrow out of the classification questions. The classification questions are required for workload credit. Allowing the user to exit without answering these questions could result in additional work at a later time to track down the record and determine the answer to these questions. | |
| 226 | api errors mail group | SCLR;26 | POINTER | 3.8 | This field is used to indicate which Mail Group should receive any notifications produced by the Outpatient API. Field 'API NOTIFICATIONS TO PROCESS (#227)' indicates the type of notifications should result in a MailMan message. | |
| 227 | api notifications to process | SCLR;27 | SET OF CODES | E:ERRORS ONLY WE:WARNINGS & ERRORS N:NONE | This field indicates which notification messages from the Outpatient API should be sent to the appropriate Mail Group. The Mail Group is specified in the 'API ERROR MAIL GROUP (#226)' field. Possible answers are the following: ERRORS - send just error notifications WARNINGS & ERRORS - send warning and error notifications NONE - do not send any notifications Error Definition: ----------------- Before an event is processed, the data passed to the API is analyzed. If any problems are found that cause the event processing not to occur then the problem is reported back to the calling application as 'errors'. An example of an 'error' would be an invalid DFN number for a patient. Warning Definition: ------------------- During the processing of an event, certain data passed to the API can be found to be inappropriate or inaccurate but was not crucial to the processing of the event. These types of problems are reported back to the calling application as 'warnings'. An example of a 'warning' would be Agent Orange(AO) exposure information passed for an encounter that did not require AO information. | |
| 250 | means test data | MT;0 | MULTIPLE | 43.03 | Enter in this field the year of the means test income category thresholds, property threshold and child income exclusion. These figures are released annually. They are effective on January 1st and are applied to the previous year income. | |
| 251 | *care costs | MT1;0 | MULTIPLE | 43.01 | This data is now stored in Integrated Billing. This field to be deleted with the next release of MAS after 5.2. Costs by treating Service charged by the VA for care received at a VA facility. | |
| 300 | fiscal year | FY;0 | MULTIPLE | 43.06 | Fiscal Year that inpatient and outpatient costs at a VA facility are in effect. | |
| 391.701 | current pivot entry(+) | HL7;1 | NUMERIC | This is the current entry number in the ADT/HL7 Pivot file. Only the application should edit this field. | ||
| 391.7012 | send pims hl7 v2.2 messages | HL7;2 | SET OF CODES | 1:SEND 0:STOP | This field tells the software whether to stop sending the PIMS HL7 messages. If set to 0 or stop no PIMS HL7 messages will be fired from the event drivers, DDs, or registration options. | |
| 391.7013 | send pims hl7 v2.3 messages | HL7;3 | SET OF CODES | 1:SEND 0:STOP 2:SUSPEND | This field tells the software whether to stop sending the PIMS HL7 v2.3 messages. If set to 0 or stop no PIMS HL7 v2.3 messages will be fired from the event drivers, DDs, or registration options. | |
| 391.7014 | create mfu for rai mds | HL7;4 | BOOLEAN | 1:YES | ||
| 391.702 | pivot file days to retain | HL7;6 | NUMERIC | The number of days worth of data to retain in the ADT/HL7 PIVOT file (#391.71) when the Purge PIMS HL7 PIVOT File option [VAFH PIVOT PURGE] is run. Example: If this field is set to 100, then entries in file #391.71 which are older than TODAY-100 days will be purged. If nothing is entered in this field, then a default value of 547 days will be used. (547 days is approximately 18 months.) | ||
| 391.705 | rai integrated site | HL7;5 | SET OF CODES | 0:NOT INTEGRATED 1:INTEGRATED, SINGLE DB 2:INTEGRATED, MULTIPLE DB | This field will indicate whether the site has integrated it's RAI/MDS COTS databases or not and to what level. If the field is null, then the site has not integrated. | |
| 401 | irt background job last run | IRT;1 | DATE-TIME | This field contains the date/time of the last run of the IRT Background Job. | ||
| 500 | death group | NOT;1 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever a patient expires. If no mailgroup is selected no bulletin will be generated. | |
| 501 | new patient group | NOT;2 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever a new patient is added to the patient file. If no mailgroup is selected no bulletin will be generated. | |
| 502 | name change group | NOT;3 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever the spelling of an existing patients name is changed. If no mailgroup is selected no bulletin will be generated. | |
| 503 | ssn change group | NOT;4 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever the social security number of an existing patient is changed. If no mailgroup is selected no bulletin will be generated. | |
| 504 | unverified admit group | NOT;5 | POINTER | 3.8 | Select the name of the mailgroup to be notified along with the user, whenever a veteran is admitted for whom eligibility has not been verified, or for patients admitted with verified eligibility who have either future scheduled admissions or waiting list entries. If no mailgroup is selected no bulletin will be generated. | |
| 505 | inconsistency edit group | NOT;6 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever inconsistencies are found in a patients database that can not be corrected by the user because of edit restrictions, i.e., not holding the 'DG ELIGIBILITY' security key for verified data. If no mailgroup is selected no bulletin will be generated. | |
| 506 | non-veteran admit group | NOT;7 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever a non-veteran is admitted to the facility. If no mailgroup is selected no bulletin will be generated. | |
| 507 | overdue absences group | NOT;8 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever the G&L is run and the user elects to search for patients who are overdue from returning from Authorized/Unauthorized absence and pass. If no mailgroup is select no bulletin will be generated. | |
| 508 | patient deleted group | NOT;9 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever a patient is DELETED from the database (PATIENT file). If no local mailgroup is selected no bulletin will be generated. | |
| 509 | sensitive rec accessed group | NOT;10 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever a sensitive record is accessed. If no mailgroup is selected no notification will be made however the access will still be recorded. | |
| 510 | sensitivity removed group | NOT;11 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever the status of a previously identified sensitive record is changed to non-sensitive. If no mailgroup is selected no notification will be made. | |
| 511 | auto recalc group | NOT;12 | POINTER | 3.8 | ||
| 512 | means test required group | NOT;13 | POINTER | 3.8 | Enter the name of the mail group that will receive the message stating a means test is required when an appointment is made. | |
| 513 | irt short form list group | NOT;14 | POINTER | 3.8 | Select the name of the mailgroup which should be notified whenever the IRT Background Job is run, options: (IRT Update Std. Deficiencies and IRT Update Std. Def. Background Job), to receive a list of patients that have been discharged less than 48 hours from their admission (Short Form).. If no mailgroup is selected no bulletin will be generated. | |
| 600 | amis 420 started | AMIS;1 | DATE-TIME | Date/time generation was started for the AMIS 420. | ||
| 601 | amis 420 last completed | AMIS;2 | DATE-TIME | Date/time AMIS 420 generation was last completed. | ||
| 602 | amis 420 task number(+) | AMIS;3 | NUMERIC | System task number assigned to the job for the AMIS 420 generation. | ||
| 603 | amis 420 started by(+) | AMIS;4 | POINTER | 200 | Person/user that ran the generation for the AMIS 420. | |
| 604 | amis 420 running(+) | AMIS;5 | BOOLEAN | 0:NO 1:YES | Date/time the AMIS 420 is currently running. | |
| 605 | period checked(+) | AMIS;6 | FREE TEXT | Month and year the MAS Parameters file was checked/edited. | ||
| 700 | rug background job last run(+) | RUG;1 | DATE-TIME | Date/time Resource Utilization Grouper (RUG) background job was last run. | ||
| 701 | rug17 conversion date | RUG;2 | DATE-TIME | Date the RUGs were converted to RUG17 methodology. | ||
| 720 | bt certifying official | BT;1 | POINTER | 200 | This will be used to print on the 70-3542d form, if the site decides that they want to have a set name printed all the time. If it is left blank then the user's name, followed by DESIGNEE OF CERTIFYING OFFICIAL will be printed instead of the set name of the certifying official. | |
| 721 | bt other expenses asked(+) | BT;2 | BOOLEAN | 0:NO 1:YES | This field will be used to determine whether the "MEALS & LODGING" and "FERRY, BRIDGES, ETC." questions are asked in the Beneficiary Travel Claim Enter/Edit Option. | |
| 722 | use temporary address | BT;3 | BOOLEAN | 0:NO 1:YES | Do you want the patient's temporary address to be used on scheduling letters if one is provided in the PATIENT file? | |
| 723 | corefls active | BT;4 | BOOLEAN | 1:YES 0:NO | This entry determines whether the Bene Travel package prompts for coreFLS vendor (ACTIVE - YES) or FMS vendor (ACTIVE - NO). | |
| 800 | routine | ROU;0 | MULTIPLE | 43.07 | A list of all routines distributed with the MAS DHCP software package. | |
| 900 | *name of ub82 signer | UB82;1 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 901 | *title of ub82 signer | UB82;2 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 902 | *can reviewer authorize? | UB82;3 | BOOLEAN | 0:NO 1:YES | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 903 | *remark to appear on each ub82 | UB82;4 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 904 | *federal tax number(+) | UB82;5 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 905 | *blue cross/shield provider #(+) | UB82;6 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 906 | *ub82 cancellation mailgroup | UB82;7 | POINTER | 3.8 | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 907 | *billing supervisor name(+) | UB82;8 | POINTER | 200 | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 908 | *ub82 disapproved mailgroup | UB82;9 | POINTER | 3.8 | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 909 | *print '001' for total charges | UB82;10 | BOOLEAN | 0:NO 1:YES | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 910 | *can initiator review? | UB82;11 | BOOLEAN | 0:NO 1:YES | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 911 | *agent cashier mail symbol | UB82-1;1 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 912 | *agent cashier street address | UB82-1;2 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 913 | *agent cashier city | UB82-1;3 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 914 | *agent cashier state | UB82-1;4 | POINTER | 5 | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 915 | *agent cashier zip code | UB82-1;5 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 916 | *agent cashier phone number | UB82-1;6 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 917 | *ub-82 initialization number(+) | UB82;12 | FREE TEXT | This field is no longer used in determining bill numbers. | ||
| 918 | *ub-82 bill number assignment | UB82;13 | FREE TEXT | Obsolete field no longer used. | ||
| 919 | *mas service pointer(+) | UB82;14 | POINTER | 49 | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 920 | *cancellation remark for fisca(+) | UB82-1;7 | FREE TEXT | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | ||
| 921 | *can clerk enter non-ptf codes | UB82;15 | BOOLEAN | 0:NO 1:YES | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release of MAS after 5.2. Answering Yes to this parameter will also allow billing clerks to enter CPT and HCPCS codes into the billing record as well as ICD Diagnosis and Procedure codes that are not in the corresponding PTF record. | |
| 922 | *ask hinq in mccr | UB82;16 | BOOLEAN | 1:YES 0:NO | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 923 | *use op cpt screen | UB82;17 | BOOLEAN | 1:YES 0:NO | This field has been moved to the IB SITE PARAMETER file. To be deleted with the next release after MAS 5.2. | |
| 926 | *last means test converted | MTC;1 | NUMERIC | Restartable entry point for means test conversion; last patient converted This is a temporary field used during the means test conversion, only. Field will be deleted in the following release, MAS 5.3. | ||
| 927 | *date mt conversion started | MTC;2 | DATE-TIME | Date means test conversion started. This is a temporary field used during the means test conversion, only. Field will be deleted in the following release, MAS 5.3. | ||
| 928 | *date mt conversion completed | MTC;3 | DATE-TIME | Date means test conversion completed. This is a temporary field used during the means test conversion, only. Field will be deleted in the following release, MAS 5.3. | ||
| 999 | version | VERSION;1 | NUMERIC | The version number assigned to the MAS software package currently installed in the system. | ||
| 1000.01 | g&l initialization date(+) | G;1 | DATE-TIME | Please enter the date on which you wish to initialize your Gains & Losses Sheet and Bed Status Report. The date selected must be on or after October 1, 1990. Bed Status statistics will be calculated from this date only. | ||
| 1000.02 | ssn format(+) | G;2 | SET OF CODES | 1:WHOLE SSN 6:LAST FOUR | The Gains & Losses Sheet allows printing only the last four numbers of the patient's Social Security Number or the entire number. Please determine how you'd like this number to appear on your G&L. | |
| 1000.03 | means test display(+) | G;3 | BOOLEAN | 1:YES 0:NO | This G&L is designed to display current Means Test Status (where applicable) if you wish. Simply respond YES to this prompt in order to display this data on your daily Gains and Losses Sheet. | |
| 1000.04 | patient's treating specialty(+) | G;4 | SET OF CODES | 1:SHOW 0:DON'T SHOW | The This field is used for the purpose of determining whether or not you wish for the exact Treating Specialty to which a patient is assigned to display on the G&L whenever a movement is displayed. The information will appear immediately to the right of the assigned ward location. | |
| 1000.05 | two/three column display(+) | G;5 | SET OF CODES | 2:TWO 3:THREE | Please select whether you wish the patient listing (G&L) to display names in a two or three column format. Certain transaction types, i.e., Transfers in/out, will always appear as a single column output regardless, however, this feature may reduce the amount of paper required to generate this listing. | |
| 1000.06 | show non-movements on g&l(+) | G;6 | BOOLEAN | 1:YES 0:NO | Answer YES should you wish for non-movements, i.e., Treating Specialty Change to appear on the G&L otherwise answer NO. | |
| 1000.07 | recalculate from(+) | G;7 | DATE-TIME | Please enter the date from which you wish to recalculate totals which must be on or after the G&L Initialization Date. The purpose of this parameter is to allow you the flexibility to maintain an "old" initialization date without the worry that a correction entered say, for five years ago, cause a recalculation process to commence which may take days to complete. It is strongly suggested that recalculation always be accomplished for, at a minumum, the current fiscal reporting year. | ||
| 1000.08 | count vietnam vets remaining(+) | G;8 | BOOLEAN | 1:YES 0:NO | Answer YES if you wish to calculate vietnam era veteran's remaining at the end of each day. If you choose to do so the length of processing time may be increased up to 20 minutes per day. Please note that this information is no longer reported on any AMIS Segment. | |
| 1000.09 | count over 65's remaining(+) | G;9 | BOOLEAN | 1:YES 0:NO | Answer YES to the following prompt if you wish to calculate patient's over 65 years in age remaining at the end of each census date. If you choose to do so processing time for recalculation may be increased up to 30 minutes per date. Please note that this information is no longer reported on any AMIS Segment. | |
| 1000.1 | default treating specialty(+) | G;10 | POINTER | 45.7 | Once the system starts collecting Treating Specialty statistics it will be necessary to capture those data where a Treating Specialty may not have been assigned to a particular patient. Please respond to to this field with the DEFAULT Treating Specialty to which you want these statistical data associated. Perhaps one might want to create a Treating Specialty called UNKNOWN, UNDEFINED, etc., and utilize this. | |
| 1000.11 | tsr initialization date | G;11 | DATE-TIME | Enter the date on which you wish to initialize your Treating Specialty Report. The date selected must be on or after October 1, 1992. The Treating Specialty Report census statistics will be calculated from this date. | ||
| 1100.01 | pre-registration sort | DGPRE;1 | SET OF CODES | P:PATIENT NAME S:MEDICAL SERVICE | This entry determines the sort order of the call list display | |
| 1100.02 | days between calls | DGPRE;2 | NUMERIC | This field will be used to determine how many days from the latest DATE CHANGED Field, #1, in PRE-REGISTRATION AUDIT File, #41.41, before the patient will be added to the call list again. If the patient has another appointment within x number of days of the date in the DATE CHANGED field, he will not be added. | ||
| 1100.03 | background job function | DGPRE;3 | SET OF CODES | D:DELETE ALL ENTRIES P:DELETE CALLED PATIENTS DA:DELETE ENTRIES AND ADD NEW PA:DELETE CALLED PATIENTS AND ADD NEW AO:ADD NEW ENTRIES ONLY N:NOTHING | Preregistration nightly background job. This field determines which actions the background job performs when run. Delete removes all entries from the call list. Purge removes only the called patients from the call list. Nothing tells the background job to leave the call list alone. Add, just adds entries to the call list, without removing any. | |
| 1100.04 | days to maintain log | DGPRE;4 | NUMERIC | This field is the number of days to maintain entries in the PRE-REGISTRATION CALL LOG File, #41.43. All entries before this limit will be purged. | ||
| 1100.05 | days to pull appointment | DGPRE;5 | NUMERIC | This field sets the number of days in advance to look for appointments to pull patients for. | ||
| 1100.06 | run for weekend | DGPRE;6 | BOOLEAN | 1:YES 0:NO | If this field is 'Y'es, then the background job will run and add on weekends. | |
| 1110 | clinic exclusion | DGPREC;0 | MULTIPLE | 43.04 | ||
| 1120 | eligibility exclusion | DGPREE;0 | MULTIPLE | 43.08 | ||
| 1201 | restrict patient record access | REC;1 | BOOLEAN | 1:YES 0:NO | If this parameter is set to 1 and the user does not hold the DG RECORD ACCESS security key, they will not be allowed to access their own PATIENT (#2) file record. | |
| 1202 | purple heart sort | PH;1 | SET OF CODES | A:ASCENDING D:DESCENDING | This field should be edited if the local site wants the daily tasked Purple Heart Status Report to be sorted in 'A'scending order by the number of days since the last status update. By default, the report will sort by descending order. | |
| 1203 | net worth calculation | GMT;1 | BOOLEAN | 0:NO 1:YES | This field is used as a flag to indicate the method to use in determining the veteran's net worth. If the Net Worth Calculation = "YES" then net worth is equal to the veteran's assets minus debts. If the Net Worth Calculation = "NO" then net worth is equal to assets plus income minus debts. | |
| 1205 | vfa start date | VFA;1 | DATE-TIME | The date, January 1,2013, that the Veteran Financial Assessment(VFA) project becomes operational. A Primary Means Test(MT) on file less than or equal to 1 year old as of the VFA Start Date shall not expire. Otherwise, MTs older than 1 year shall be considered expired and a new MT shall be required. | ||
| 1301 | ao sta exp date | ENR;1 | DATE-TIME | If populated, this field will be used as the expiration date for the Special Treatment Authority (STA) for Agent Orange (AO) Veterans with an AO exposure location of Vietnam. New enrollments of AO Veterans with an exposure location of Vietnam and no additional eligibility factors will no longer be enrolled as a Priority Group 6 if the enrollment date is greater than the expiration date. | ||
| 1302 | swac sta exp date | ENR;2 | DATE-TIME | If populated, this field will be used as the expiration date for the Special Treatment Authority (STA) for Southwest Asia Condition (SWAC) Veterans. New enrollments of SWAC Veterans and no additional eligibility factors will no longer be enrolled as a Priority Group 6 if the enrollment date is greater than the expiration date. |
Not Referenced