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 |  Local Variables |  All
Print Page as PDF
Global: ^HLD(779.1

Package: Health Level Seven

Global: ^HLD(779.1


Information

FileMan FileNo FileMan Filename Package
779.1 HLO SYSTEM PARAMETERS Health Level Seven

Description

Directly Accessed By Routines, Total: 14

Package Total Routines
Health Level Seven 14 HLOAPI6    HLOMSG1    HLOP158    HLOPING    HLOPOST    HLOPROC    HLOPROC1    HLOSITE
HLOSRVR    HLOSTRAC    HLOTLNK    HLOUSR    HLOUSR1    ^HLD(779.1    

Accessed By FileMan Db Calls, Total: 1

Package Total Routines
Health Level Seven 1 HLOUSR    

Pointer To FileMan Files, Total: 2

Package Total FileMan Files
Health Level Seven 1 HL LOGICAL LINK(#870)[.1]    
Kernel 1 TASKMAN SITE PARAMETERS(#14.7)[.13]    

Fields, Total: 13

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

  • INPUT TRANSFORM:  K:$L(X)>64!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  AUG 05, 2004
  • HELP-PROMPT:  The domain name for this system. It will be used to populate component 2 of the Sending Facility field of the HL7 message header.
  • DESCRIPTION:  
    The domain name for this system.  It will be used to populate component 2 of the Sending Facility field of the HL7 message headers.
  • CROSS-REFERENCE:  779.1^B
    1)= S ^HLD(779.1,"B",$E(X,1,60),DA)=""
    2)= K ^HLD(779.1,"B",$E(X,1,60),DA)
.02 STATION NUMBER 0;2 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>7!($L(X)<3) X
  • LAST EDITED:  AUG 05, 2004
  • HELP-PROMPT:  Enter the station number with suffix that this system belongs under. It will be used in component 1 of the Sending Facility field of the HL7 message header.
.03 PRODUCTION ID 0;3 SET
************************REQUIRED FIELD************************
  • 'P' FOR production;
  • 'T' FOR training;

  • LAST EDITED:  AUG 05, 2004
  • HELP-PROMPT:  ENTER P if this is a production system, T otherwise.
.04 MAXIMUM STRING LENGTH 0;4 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999)!(X<1)!(X?.E1"."1N.N) X
  • LAST EDITED:  JUL 06, 2005
  • HELP-PROMPT:  This is the maximum length for strings built by HLO when local applications create new messages to send.
  • DESCRIPTION:  This parameter determines the maximum length for strings that HLO will create when messages are being built. It doesn't apply to servers, as the size of input buffer used by TCP/IP determines the maximum string length
    created by a single read.
.05 BUFFER SIZE FOR HL7 (BYTES) 0;5 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>20000)!(X<10000)!(X?.E1"."1.N) X
  • LAST EDITED:  AUG 05, 2005
  • HELP-PROMPT:  This parameter represents the size of the buffer used by HLO for its background processes. It defaults to 15000 bytes, but may be set from 10,000 bytes to 20,000 bytes.
.06 BUFFER SIZE FOR USER (BYTES) 0;6 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>10000)!(X<512)!(X?.E1"."1.N) X
  • LAST EDITED:  AUG 05, 2005
  • HELP-PROMPT:  This parameter is the size of the buffer used by HLO in the context of an online user. It defaults to 5000, but may be reset to between 512 and 10000 bytes.
.07 NORMAL MSG RETENTION (DAYS) 0;7 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  MAR 26, 2012
  • HELP-PROMPT:  How many days should successful messages be kept before being purged? Enter a whole number, 1 to 99.
  • DESCRIPTION:  This field controls how many days successful messages are retained after being fully processed before they are purged.
    The application may specify a longer time to retain its messages, which would override the time specified here.
.08 BAD MESSAGE RETENTION (DAYS) 0;8 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99)!(X<5)!(X?.E1"."1.N) X
  • LAST EDITED:  MAR 23, 2012
  • HELP-PROMPT:  How many days should message with errors remain on your system? Enter 5 to 99. The default is 7.
  • DESCRIPTION:  This field controls the purging of HL7 messages that do not complete successfully. The period should be reasonably long to allow investigation, but because of the high daily volume of messages purging must occur as
    quickly as practical.
.09 HLO ON/OFF SWITCH 0;9 SET
  • '0' FOR OFF;
  • '1' FOR ON;

  • LAST EDITED:  MAY 03, 2005
  • HELP-PROMPT:  Set to 0 to turn off messaging and all HL7 processes.
.1 HLO STANDARD LISTENER 0;10 POINTER TO HL LOGICAL LINK FILE (#870) HL LOGICAL LINK(#870)

  • INPUT TRANSFORM:  S DIC("S")="I ($P($G(^HLCS(870,Y,400)),""^"",3)=""M"")!($P($G(^HLCS(870,Y,400)),""^"",3)=""S"")" D ^DIC K DIC S DIC=$G(DIE),X=+Y K:Y<0 X
  • LAST EDITED:  JUN 01, 2005
  • HELP-PROMPT:  Select an entry from the HL Logical Link file that is the listener that remote applications will normally connect to.
  • SCREEN:  S DIC("S")="I ($P($G(^HLCS(870,Y,400)),""^"",3)=""M"")!($P($G(^HLCS(870,Y,400)),""^"",3)=""S"")"
  • EXPLANATION:  This screen allows only server entries to be selected.
.11 HLO RECOUNT ON/OFF FLAG 0;11 SET
  • '0' FOR OFF;
  • '1' FOR ON;

  • LAST EDITED:  OCT 25, 2007
  • HELP-PROMPT:  Set to 1 to disallow update of queues when a recount is being performed.
.12 UNSENT MSG RETENTION (DAYS) 0;12 NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999)!(X<1)!(X?.E1"."1.N) X
  • LAST EDITED:  JUL 23, 2008
  • HELP-PROMPT:  How many days should an unsent message be kept before it is purged? (default value is 45 days)
.13 BOX-VOLUME PAIR 0;13 POINTER TO TASKMAN SITE PARAMETERS FILE (#14.7) TASKMAN SITE PARAMETERS(#14.7)

  • LAST EDITED:  MAR 24, 2010
  • HELP-PROMPT:  Enter the BOX-VOLUME pair that HLO processes should run on.
  • DESCRIPTION:  The BOX-VOLUME PAIR parameter allows a site to specify which CPU and volume set the HLO processes should run on. This parameter only controls procesess started by the HLO Process Manager by calling the Taskmanager APIs.
    This parameter is optional.
    For VMS sites, this parameter generally does NOT control what node to run the listener on, because VMS sites should use VMS TCPIP Services for their listener.
    For Cache/NT sites using a load balancer, this parameter can be used to specify what node to run the listener on.

Found Entries, Total: 1

DOMAIN NAME: HL7.VISTA.DOMAIN.EXT    

External References

Name Field # of Occurrence
^DIC .1+1

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^HLD(779.1 - [#779.1] .01(XREF 1S), .01(XREF 1K)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> DA .01(XREF 1S), .01(XREF 1K)
DIC .1+1!*
DIC("S" .1+1*, .1SCR+1*
>> DIE .1+1
X .01+1!, .01(XREF 1S), .01(XREF 1K), .02+1!, .04+1!, .05+1!, .06+1!, .07+1!, .08+1!, .1+1*!
, .12+1!
>> Y .1+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 |  Local Variables |  All