Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All
Print Page as PDF
Global: ^HLD(779.9

Package: Health Level Seven

Global: ^HLD(779.9


Information

FileMan FileNo FileMan Filename Package
779.9 HLO PRIORITY QUEUES Health Level Seven

Description

Directly Accessed By Routines, Total: 3

Package Total Routines
Health Level Seven 3 ^HLD(779.9    HLOQUE    LINKS    

Accessed By FileMan Db Calls, Total: 1

Package Total Routines
Health Level Seven 1 HLOQUE    

Pointer To FileMan Files, Total: 1

Package Total FileMan Files
Health Level Seven 1 HL LOGICAL LINK(#870)[#779.91(.01)]    

Fields, Total: 5

Field # Name Loc Type Details
.01 QUEUE 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • 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)
.02 DIRECTION 0;2 SET
************************REQUIRED FIELD************************
  • '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)
.03 APPLIES TO ALL LINKS (YES/NO) 0;3 SET
************************REQUIRED FIELD************************
  • '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)
.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)
1 LINKS 1;0 POINTER Multiple #779.91 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:  

External References

Name Field # of Occurrence
RESETF^HLOQUE IXEKL+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^HLCS(870 - [#870] IXFP4TS+1
^HLD(779.9 - [#779.9] IXESL+1*, IXEKL+1!, IXEKEIC+1!, IXFSL+1*, IXFKL+1!, IXFKEIC+1!, IXFP1CC+1, IXFP2CC+1, IXFP3CC+1, .01(XREF 1S)
.01(XREF 1K)

Naked Globals

Name Field # of Occurrence
^(0 ID.04+1

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> DA IXEKL+1, .01(XREF 1S), .01(XREF 1K)
>> DA(1 IXFP1CC+1, IXFP2CC+1, IXFP3CC+1
>> DIC ID.02+1
U ID.04+1
X IXESCC+1*, IXFP1CC+1*, IXFP2CC+1*, IXFP3CC+1*, IXFP4TS+1*, .01+1!, .01(XREF 1S), .01(XREF 1K), .04+1!
>> X1(1 IXFKL+1
>> X1(2 IXEKL+1, IXFKL+1
>> X1(3 IXEKL+1
>> X1(4 IXFKL+1
>> X2(1 IXESCC+1, IXFSL+1
>> X2(2 IXESL+1, IXFSL+1
>> X2(3 IXESL+1, IXFSL+1
>> X2(4 IXESL+1, IXFSL+1
>> X2(5 IXFSL+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointer To FileMan Files |  Fields |  Found Entries |  External References |  Global Variables Directly Accessed |  Naked Globals |  Local Variables |  All