STANDARD DATA DICTIONARY #779.9 -- HLO PRIORITY QUEUES FILE 3/24/25 PAGE 1
STORED IN ^HLD(779.9, *** 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 contains the priorities of HLO queues as assigned by the system operations staff.
It is not necessary to assign a priority to a queue. However, doing so will change the frequency that HLO services the queue.
Important queues that tend to be backed up should be assigned a higher priority. Less important queues may be assigned a lower
priority. The goal of setting queue priorities is to balance the HLO resources over the queues in order to obtain a desired
performance.
Currently priorities may be set only for outgoing queues, though the file was designed to also support the assignment of priorities
for incomming queues. The option for entering the type of queue (incomming or outgoing) currently will automatically default to
outgoing. A future enhancment may support the ability to assign priorities to incomming queues.
To set the priority the name of the queue must be specified. As explained, currently the queue will be assumed to be outgoing.
Optionally,if the priority is to be set only for a specific link then the link must be specified.
Examples:
You could set the priority of an outgoing queue named "HLO OUT" without specifying the link. The effect would be to set the
priority of all outgoing queues named "HLO OUT" regardless of the link.
You could set the priority of an outgoing queue named "HLO OUT" and also specify the link. The effect would be to set the priority
of the outgoing queue named "HLO OUT" that is sending messages via that specific link only.
If a queue's priority is specified to apply to all links, but that queue's priority is also specified for a specific link, that
specific priority setting will override the general one.
IDENTIFIED BY: DIRECTION (#.02)[R], PRIORITY (#.04)
CROSS
REFERENCED BY: QUEUE(B)
INDEXED BY: APPLIES TO ALL LINKS (YES/NO) & QUEUE & DIRECTION & PRIORITY (E), LINK & LINK-SPECIFIC PRIORITY (F)
779.9,.01 QUEUE 0;1 FREE TEXT (Required)
INPUT TRANSFORM: K:$L(X)>20!($L(X)<3)!'(X'?1P.E) X
LAST EDITED: JAN 20, 2010
HELP-PROMPT: Enter the name of a message queue, 3 to 20 characters.
DESCRIPTION: The name of either an outgoing or incoming queue.
CROSS-REFERENCE: 779.9^B
1)= S ^HLD(779.9,"B",$E(X,1,30),DA)=""
2)= K ^HLD(779.9,"B",$E(X,1,30),DA)
RECORD INDEXES: E (#561)
779.9,.02 DIRECTION 0;2 SET (Required)
'IN' FOR INCOMING;
'OUT' FOR OUTGOING;
LAST EDITED: JAN 29, 2010
HELP-PROMPT: What direction is the queue's messages?
DESCRIPTION: HLO includes queues that contain incoming messages and other queues that contain outgoing messages.
For example, there may be two queues named 'MPI ADT~A08', with one for messages being transmitted
to another system, and the other queue of the same name for messages that were received from other
systems.
At present this field will automatically default to OUTGOING. A future enhancment may support the
assignment of priorties for incomming queues.
RECORD INDEXES: E (#561)
779.9,.03 APPLIES TO ALL LINKS (YES/NO) 0;3 SET (Required)
'1' FOR YES;
'0' FOR NO;
LAST EDITED: FEB 01, 2010
HELP-PROMPT: Answer YES if this priority applies to all links for this queue. A YES does not preclude entering a
different priority for a specific queue.
DESCRIPTION: Enter YES if the priority should be applied to all queues of the given name, regardless of the link
the queue is for.
It is allowed that even if set to YES, a different priority can be assigned to that queue for
specific links, and that priority for the queue/link will override the more general one.
If this field is set to NO, that means that the PRIORITY field (#.04) is ignored. A priority can
still be assigned to a specific queue by specifying the specific link, along with the priority for
that queue/link.
If it is set to NO or left blank then the queue would assume the default priority of 50, unless
overridden in the LINKS multiple.
RECORD INDEXES: E (#561)
779.9,.04 PRIORITY 0;4 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>100)!(X<20)!(X?.E1"."1.N) X
LAST EDITED: JAN 29, 2010
HELP-PROMPT: Enter a whole number between 20 and 100. Queues given a higher priority will be serviced more
often. The default priority is 50.
DESCRIPTION: A priority is an integer between 20 and 100, with a default value of 50. The lower the priority,
the less frequently the queue will be serviced. Conversely, the higher a queue's priority the more
frequently it will be serviced. The recommended use of the priority functionality is to reserve
its use to the operations staff. A queue's priority should be increased if experience shows that it
tends to get backed up.
RECORD INDEXES: E (#561)
779.9,1 LINKS 1;0 POINTER Multiple #779.91
DESCRIPTION: A link is an entry in the HL Logical Link file (#870). It defines a a destination point for HL7
messages, and the lower level communication protocol that should be used to transmit messages to
that destination.
TECHNICAL DESCR:
779.91,.01 LINK 0;1 POINTER TO HL LOGICAL LINK FILE (#870) (Multiply asked)
LAST EDITED: JAN 29, 2010
HELP-PROMPT: Select the specific link that the queue priority will apply to.
DESCRIPTION: This is a link which will have special priority separate from the general priority of the queue.
CROSS-REFERENCE: 779.91^B
1)= S ^HLD(779.9,DA(1),1,"B",$E(X,1,30),DA)=""
2)= K ^HLD(779.9,DA(1),1,"B",$E(X,1,30),DA)
RECORD INDEXES: F (#562) (WHOLE FILE #779.9)
779.91,.02 LINK-SPECIFIC PRIORITY 0;2 NUMBER
INPUT TRANSFORM: K:+X'=X!(X>100)!(X<20)!(X?.E1"."1.N) X
LAST EDITED: NOV 23, 2009
HELP-PROMPT: Enter the priority as a number 20-100. A higher priority will cause the queue to be serviced more
frequently. The default priority is 50.
DESCRIPTION: Entering a priority here will cause it to be specific to this link. If the priority is not
entered here, the priority will be derived from the PRIORITY field at the higher level in file
779.9.
RECORD INDEXES: F (#562) (WHOLE FILE #779.9)
FILES POINTED TO FIELDS
HL LOGICAL LINK (#870) LINKS:LINK (#.01)
File #779.9
Record Indexes:
E (#561) RECORD MUMPS IR LOOKUP & SORTING
Short Descr: Used to find the queue priority.
Set Logic: S ^HLD(779.9,"E",X2(2),X2(3))=$G(X2(4))
Set Cond: S X=X2(1)
Kill Logic: K:($L(X1(2))&$L(X1(3))) ^HLD(779.9,"E",X1(2),X1(3)),^HLD(779.9,"F",X1(2),X1(3)) D RESETF^HLOQUE(DA)
Whole Kill: K ^HLD(779.9,"E")
X(1): APPLIES TO ALL LINKS (YES/NO) (779.9,.03) (forwards)
X(2): QUEUE (779.9,.01) (Len 20) (forwards)
X(3): DIRECTION (779.9,.02) (Len 3) (forwards)
X(4): PRIORITY (779.9,.04) (Len 3) (forwards)
Subfile #779.91
Record Indexes:
F (#562) RECORD MUMPS IR LOOKUP & SORTING WHOLE FILE (#779.9)
Short Descr: Used to lookup queue priority specific to a particular link.
Description:
Set Logic: S:($L(X2(1))&$L(X2(2))&$L(X2(4))) ^HLD(779.9,"F",X2(1),X2(2),X2(4))=$S(X2(5):X2(5),X2(3):X2(3),1:50)
Kill Logic: K:($L(X1(1))&$L(X1(2))&$L(X1(4))) ^HLD(779.9,"F",X1(1),X1(2),X1(4))
Whole Kill: K ^HLD(779.9,"F")
X(1): Computed Code: S X=$P(^HLD(779.9,DA(1),0),"^")
(Subscr 1) (Len 20) (forwards)
X(2): Computed Code: S X=$P(^HLD(779.9,DA(1),0),"^",2)
(Subscr 2) (Len 3)
X(3): Computed Code: S X=$P(^HLD(779.9,DA(1),0),"^",4)
(Len 3)
X(4): LINK (779.91,.01) (Subscr 3) (Len 10) (forwards)
Transform (Storage): S X=$P(^HLCS(870,X,0),"^")
X(5): LINK-SPECIFIC PRIORITY (779.91,.02) (Len 3) (forwards)
INPUT TEMPLATE(S):
PRINT TEMPLATE(S):
SORT TEMPLATE(S):
FORM(S)/BLOCK(S):