# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | FREE TEXT | B | This is the name of the rule, used to identify it uniquely in the file; it is visible in the Rule Editor only. | |
1 | inactivated | 1;1 | DATE-TIME | This is the date/time this rule is no longer considered active; after this date/time, this rule will no longer apply. | ||
1.5 | activation history | 2;0 | MULTIPLE | 100.61 | ||
2 | type of event(+) | 0;2 | SET OF CODES | A:ADMISSION T:TRANSFER D:DISCHARGE S:SPECIALTY TRANSFER O:O.R. | This is the event that should cause orders to be automatically discontinued; for OR events, the orders will be discontinued when the TIME PAT IN OR field is entered in the Surgery package. | |
3 | division(+) | 0;3 | POINTER | 4 | This is the division that this auto-dc rule should be applied to; for a transfer across divisions, this should be the new division that the patient is going to. | |
4 | dc reason | 0;4 | POINTER | 100.03 | This is the reason that will be saved with the order indicating why it was automatically discontinued. | |
5 | display text(+) | 0;5 | FREE TEXT | This field is the name of the rule as it will appear to the user in CPRS. | ||
6 | except from observation | 0;6 | SET OF CODES | 0:NO 1:IF READMITTING 2:YES | This indicates if an observation treating specialty should prevent this rule from being applied, when the patient is discharged from it. Enter YES if an observation specialty should always be considered an exception to this rule, or NO to never consider it. IF READMITTED will cause the clerk to be asked if the patient will be immediately admitted again, and a response of YES will prevent this rule from being applied; because it requires user interaction, this value should only be used with the non- tasked OR GUA EVENT PROCESSOR NOTASK protocol on DGPM MOVEMENT EVENTS, otherwise a value of NO will be assumed and this rule will be applied without exception. | |
30 | mas movement types | 3;0 | MULTIPLE | 100.63 | These are the MAS Movement Types that define this event; when an MAS event occurs for one of these types, this rule will be processed if active. | |
40 | excluded treating specialties | 4;0 | MULTIPLE | 100.64 | These are treating specialties that will cause this rule to not be processed, if the EXCEPT FROM and TO specialties match the patient's transfer. | |
50 | included locations | 5;0 | MULTIPLE | 100.62 | ||
60 | included divisions | 6;0 | MULTIPLE | 100.66 | These are the divisions that will cause this rule to be processed, if the FROM division matches the patient's transfer. | |
70 | included packages | 7;0 | MULTIPLE | 100.67 | These are the packages whose orders are to be automatically discontinued when this rule is processed. | |
80 | excluded orderable items | 8;0 | MULTIPLE | 100.68 | These are the orderable items that are NOT to be automatically discontinued when this rule is processed, even if an order for it belongs to a package in the INCLUDED PACKAGES multiple. | |
81 | edit history | 9;0 | MULTIPLE | 100.681 | ||
100 | excluded display group | 10;0 | MULTIPLE | 100.65 |