# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | This field is the name of this set of parameters. The name of the base set that is sent out is "HOSPITAL". The code will work more efficiently if the name of the base set of parameters is not changed from "HOSPITAL". | |
1 | top 10 reactions | 1;0 | MULTIPLE | 120.841 | A list of reactions for the user to choose from when selecting reactions for a patient allergy/adverse reactions. These will be the ten most common reactions, and modifiable by the site. | |
2 | autoverify food/drug/other | 0;2 | SET OF CODES | 0:NO AUTOVERIFY 1:AUTOVERIFY DRUG ONLY 2:AUTOVERIFY FOOD ONLY 3:AUTOVERIFY DRUG/FOOD 4:AUTOVERIFY OTHER ONLY 5:AUTOVERIFY DRUG/OTHER 6:AUTOVERIFY FOOD/OTHER 7:AUTOVERIFY ALL | This field determines which types of allergies a site wants autoverified at the user sign off. | |
3 | autoverify observed/historical | 0;3 | SET OF CODES | 0:NO AUTOVERIFY 1:AUTOVERIFY HISTORICAL ONLY 2:AUTOVERIFY OBSERVED ONLY 3:AUTOVERIFY BOTH | This field is configurable by the site to allow autoverification of observed or historical allergies. | |
3.5 | autoverify logical operator | 0;6 | SET OF CODES | !:OR &:AND | This field will determine how the Autoverify Food/Drug/Other and Autoverify Observed/Historical parameters relate to each other. OR means that the reaction will be autoverified if it meets the criteria of one of the two parameters, while AND means the reaction will be autoverified only if it meets the criteria of both parameters. If this field is left null, the OR condition will be used. For example, if you want to verify only observed drug reactions, you would set the Autoverify Food/Drug/Other parameter to AUTOVERIFY FOOD/OTHER and the Autoverify Observed/Historical to AUTOVERIFY HISTORICAL ONLY , and the Autoverify Logical Operator to OR. This means that a reaction that has a type of Food/Other OR is Historical will be autoverified, thus leaving observed drug reactions to be verified. Another example would be if you wanted to verify all observed reactions and all drug reactions whether observed or historical. The parameters should be set accordingly: Autoverify Food/Drug/Other to AUTOVERIFY FOOD/OTHER, Autoverify Observed/Historical to AUTOVERIFY HISTORICAL ONLY and Autoverify Logical Operator to AND. In this case to be autoverifed, a reaction has to have a type of Food/Other AND it must be Historical, all other reactions will need to be verified. | |
4 | require originator comments | 0;4 | BOOLEAN | 0:NO 1:YES | This field indicates whether the originator will be required to enter comments for an OBSERVED reaction. | |
5 | *last dfn converted | CONV;1 | NUMERIC | The data in this field is the entry number of the Patient file record whose data was last converted by the Patient file data conversion. This field will be 0 before the conversion begins and after the conversion is over. | ||
5.1 | *conversion task number | CONV;2 | NUMERIC | This is the TaskMan task number of the Patient file data conversion job. The data in this field will be null before the job is queued to run, and after it has finished running. | ||
5.2 | *conversion finished | CONV;3 | BOOLEAN | 0:NO 1:YES | This field indicates whether the Patient file data conversion has finished running or not. The data in this field will be 1 if the Patient file data conversion has finished running, or did not need to run. | |
6 | division | 6;0 | MULTIPLE | 120.846 | The divisions associated with this set of site parameters. | |
7 | mark id band flag | 0;5 | BOOLEAN | 0:NO 1:YES | This field is an indicator to denote whether the site wants to document if the patient ID band should be marked for a certain allergy. The system will assume the site wants to document the marking of inpatient ID bands. If this field is answered NO, the site does not want to document the marking of inpatient ID bands. | |
7.1 | method of notification | 0;8 | SET OF CODES | 0:BULLETIN 1:OE/RR TEAMS 2:NO NOTIFICATION | This field tells ART if or how the users should be notified for chart or ID band markings. There are three methods. The first method is the use of BULLETINs, which is the current way ART works. The second method is the use of OE/RR Teams. If this method is used, then you will need to set up different teams for each ward and also assign printers to these teams. The third method is to turn off the function. | |
7.2 | alert id band/chart mark | 0;9 | BOOLEAN | 1:YES 0:NO | This field is to let the system know if you want to issue alerts if the fields have not been answered in the Enter/Edit Patient Reaction Data portion of the system. If the field is answered yes(1) or is null then, the system will continue to issue the alerts. If this field is no(0), then the system will not issue alerts for this record. | |
7.3 | new admission chart mark | 0;10 | BOOLEAN | 1:YES 0:NO | This is to indicate if the site wants to send chart mark bulletin for a new admission. | |
8 | *3.0 conversion last dfn | CONV3;1 | NUMERIC | This field will contain the last field that has been fully converted. The field is initially set to 0. | ||
8.1 | *3.0 task number | CONV3;2 | FREE TEXT | This field is the TaskMan number that was assigned. In the event that there is a conversion failure this will enable the system to give the programmers the tools to investigate the problem. | ||
8.2 | *conversion finished | CONV3;3 | BOOLEAN | 1:YES 0:NO | This field indicates whether the V3.0 data structure conversion has finished running. The data in this field will be 1 if the conversion has finished running or did not need to run. | |
9 | nka conversion | NKA;0 | MULTIPLE | 120.849 | This field contains all the entries that are to be converted in the 3.0 NKA conversion. | |
10 | fda data required | 0;7 | BOOLEAN | y:YES n:NO | This field will indicate whether the entry of FDA Data should be required during the Enter/Edit Patient Reaction Data. If this field is answered "YES", then the user must enter the FDA Data at the time of entering a reaction. If this field is left null or answered "NO", then the FDA Data entry will not be required during the Enter/Edit Patient Reaction Data option. | |
10.1 | e/e description active | 0;11 | BOOLEAN | 1:YES 0:NO | Permit users to indicate why a reaction was Entered in Error. | |
11 | reporter name | RPT;1 | FREE TEXT | This field would contain the default reporter name to be used on the FDA reports. | ||
12 | reporter address1 | RPT;2 | FREE TEXT | This field would contain the first line of the reporter address to be used as a default for the FDA reports. | ||
13 | reporter address2 | RPT;3 | FREE TEXT | This field would contain the second line of the reporter address to be used as the default on the FDA reports. | ||
14 | reporter address3 | RPT;4 | FREE TEXT | This field would contain the third line of the reporter address to be used as the default on the FDA reports. | ||
15 | reporter city | RPT;5 | FREE TEXT | This field contains the city to be used as the default on the FDA Reports. | ||
16 | reporter state | RPT;6 | POINTER | 5 | This field contains the default state to be used on the FDA reports. | |
17 | reporter zip | RPT;7 | FREE TEXT | This field contain the default Zip Code to be used on the FDA reports. | ||
18 | reporter phone | RPT;8 | FREE TEXT | This field contains the default phone number to be used on the FDA reports. | ||
19 | occupation | RPT;11 | FREE TEXT | This field contains the reporter's occupation. | ||
21 | *conversion of nka | CONNKA;1 | BOOLEAN | y:YES n:NO | This field indicates if the NKA conversion is complete. ATS 3.0 will not install onto a system that has ATS Version 2.2 if this field is not set. |
Not Referenced