Developer Documentation » VDM » Oe_rr_Notifications-100_9
Oe/rr Notifications (100.9)
This file contains data used to generate notifications. Packages determine if a notification should be sent then send the patient ID and notification ID (IEN in this file) to order entry routines. Based on the notification IEN, data from this file is used to generate the notification and help determine its recipients.
|Label/Field Name||Field #||Description||Datatype||Attributes||Range|
||.001||This is the internal entry number assigned to a notification. Entries
1 through 9999 are reserved for National release by the OE/RR
For local site-defined notifications, the internal entry number must be
specific to your VAMC in the following format:
For example, if your site is number 456, your first locally created
notification would be 45601.
||.01||This is the name of the notification. It should match the text in the
MESSAGE TEXT field as closely as possible (it may be an abbreviated version
of the entry in MESSAGE TEXT.) This field is displayed to users when
selecting or reviewing entries in this file (100.9).
||.02||This entry should always be “OR” to indicate the alert (notification) is
processed by OE/RR. “OR” is stuffed via a trigger x-ref in field .01.
This Package ID will have “;DFN;NIEN” concatenated to the end of it, to
make the XQAID variable which is used by the XQALERT routine to provide a
unique cross-reference. The order entry notification system will check
the New person file to determine if this message is already pending for
the user. If it already exists, the user will not receive a second message.
DFN is the Patient File internal entry number.
NIEN is the Notification File internal entry number.
||.03||This text will be appended to the Patient last name and last 4 characters of
the social security number to create the order notification text.
(e.g., SMITH (4356): Unsigned orders. - Where “Unsigned orders.” is the
content of MESSAGE TEXT.) Text entered into this field is the default text
for notifications where the text message usually comes from the package
(MESSAGE TYPE = PKG).
||.04||MESSAGE TYPE field is used as a flag to determine where the message text originates. If from the NOTIFICATION file, MESSAGE TYPE is ‘NOT.’ If the message comes from the package, MESSAGE TYPE is ‘PKG.’||ENUMERATION||REQUIRED||NOTIFICATION FILE PROVIDES MESSAGE: NOT
PACKAGE PROVIDES A VARIABLE MESSAGE: PKG
||.05||This a mandatory flag used to regulate processing in XQALERT processing.
The flag is set to I to indicate the notification is for INFORMATION ONLY -
no follow-up action is to be taken. ‘I’ notifications are deleted as each
user reviews them. ‘R’ notifications have a follow-up action associated
with them. The user will be taken to another routine or option when they
select a notification with ACTION FLAG = R and a follow-up routine/option
|ENUMERATION||REQUIRED||RUN ROUTINE: R
INFORMATION ONLY: I
||.06||This is an optional field used to create the XQAROU variable to be used by
the XQALERT routine. This field represents the TAG in tag^routine.
||.07||This is an optional variable identifying a routine or tag(field .06)^routine
used to create XQAROU for processing by XQALERT.
|Non-menu Type Option Action
||1||This is an optional field used to create the variable XQAOPT for use
by XQALERT. It should indicate a non-menu type option on the user’s
primary or secondary menu, not on the Common menu. The phantom jump
is used to navigate to the destination option and will check pathway
restrictions in doing so.
||1.5||This field contains the name of the package where the notification originates or is triggered (e.g., LAB, MAS, Pharmacy.)||STRING|
||4||This field contains free text describing the notification, how it is trig-
gered and what action(s) delete it.
||5||This field contains the type of follow-up action to be taken. It is used
by the application managing the follow-up action (e.g. GUI interface) to
initiate the proper follow-up action separate from the underlying data
base and application layers. Example follow-up types include: report,
Document generated on August 31st 2017, 2:55:41 pm