STANDARD DATA DICTIONARY #779.11 -- HLO ERROR SCREENS FILE 3/24/25 PAGE 1
STORED IN ^HLD(779.11, *** NO DATA STORED YET *** SITE: WWW.BMIRWIN.COM UCI: VISTA,VISTA (VERSION 1.6)
DATA NAME GLOBAL DATA
ELEMENT TITLE LOCATION TYPE
-----------------------------------------------------------------------------------------------------------------------------------
The Health Leven Seven (Optimized) software (HLO) was released as patch HL*1.6*126 to the HL7 v1.6 software package. Although it
is structurally and functionally an independent system, it is officially part of HL7 1.6. This is a messaging system similar to
the old HL7 1.6 package, but it was designed from the ground up and is more robust, more capable, and supports a much higher
message throughput.
This file is used create screens for reporting HLO messaging errors. A screen is a list of criteria used to either include or
exclude specific error types in an error report.
A screen is identified by its name. The name should be namespaced and be descriptive as to its intended use.
DD ACCESS: @
RD ACCESS: @
WR ACCESS: @
DEL ACCESS: @
LAYGO ACCESS: @
AUDIT ACCESS: @
CROSS
REFERENCED BY: SCREEN NAME(B)
779.11,.01 SCREEN NAME 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>30!(X?.N)!($L(X)<3)!'(X'?1P.E) X
LAST EDITED: JAN 29, 2010
HELP-PROMPT: The name should be 3-30 characters, namespaced and descriptive.
DESCRIPTION: This is the name to identify the screen. It should be namespaced and descriptive.
CROSS-REFERENCE: 779.11^B
1)= S ^HLD(779.11,"B",$E(X,1,30),DA)=""
2)= K ^HLD(779.11,"B",$E(X,1,30),DA)
779.11,1 DESCRIPTION 2;0 WORD-PROCESSING #779.111 (IGNORE "|")
TECHNICAL DESCR:
LAST EDITED: JAN 29, 2010
HELP-PROMPT: Enter a full explanation for the purpose of this screen.
779.11,2 CREATOR 0;3 POINTER TO NEW PERSON FILE (#200) (Required)
LAST EDITED: JAN 29, 2010
HELP-PROMPT: Enter the name of person creating this screen.
DESCRIPTION: This is the person who created the screen.
779.11,3 DATE/TIME CREATED 0;4 DATE (Required)
INPUT TRANSFORM: S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
LAST EDITED: JAN 29, 2010
HELP-PROMPT: Enter the date and time the screen was created.
DESCRIPTION: This field contains the date/time the screen was created.
779.11,4 TYPE OF SCREEN 0;5 SET (Required)
'0' FOR EXCLUDE;
'1' FOR INCLUDE;
LAST EDITED: JUL 27, 2010
HELP-PROMPT: Enter 'EXCLUDE' to exclude specific errors from the display, or 'INCLUDE' to include only specific
errors from the display.
DESCRIPTION: This field is used to determine the type of error screen to be applied to the error list. There
are two types:
EXCLUDE (0) - excludes the error messages from being displayed INCLUDE (1) - includes the error
messages on the display.
EXECUTABLE HELP: D HELP^HLOUSR2
779.11,5 ERRORS 1;0 Multiple #779.115
DESCRIPTION: This is a list of strings used to determine what errors should display. Each string is compared to
each error that would otherwise be included in the display. If the string matches a string that
occurs within the error, the error is either:
INCLUDE type screens - the error will be included in the display. EXCLUDE type screens - the error
will be excluded from the display.
This is the verbatim text of the error to be screened. A list of possible errors is in the HLO
Technical Manual. Alternately, you may cut and paste text from the error display into this field.
You might screen errors for the following purposes: 1) To exclude certain errors from the display.
Some of the errors don't require any action on your part. 2) To display only certain errors.
These are critical errors which you want to act on quickly. You KNOW from experience what those
errors are.
TECHNICAL DESCR:
779.115,.01 ERRORS 0;1 FREE TEXT (Multiply asked)
INPUT TRANSFORM: K:$L(X)>200!($L(X)<1) X
LAST EDITED: JUL 27, 2010
HELP-PROMPT: Answer must be 1-200 characters in length.
CROSS-REFERENCE: 779.115^B
1)= S ^HLD(779.11,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^HLD(779.11,DA(1),1,"B",$E(X,1,30),DA)
779.115,.02 PARTIAL MATCH OK? 0;2 SET
'0' FOR NO;
'1' FOR YES;
LAST EDITED: JUL 27, 2010
HELP-PROMPT: If the actual error message contains the text that you entered, should it be considered a match
even if there are additional characters in the actual error message?
FILES POINTED TO FIELDS
NEW PERSON (#200) CREATOR (#2)
INPUT TEMPLATE(S):
HLO EDIT ERROR SCREEN JUL 27, 2010@17:14 USER #0
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):