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 |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Global Variables Directly Accessed |  Local Variables  | All
Print Page as PDF
Global: ^LAHM(62.9

Package: Automated Lab Instruments

Global: ^LAHM(62.9


Information

FileMan FileNo FileMan Filename Package
62.9 LAB SHIPPING CONFIGURATION Automated Lab Instruments

Description

Directly Accessed By Routines, Total: 31

Package Total Routines
Automated Lab Instruments 25 FEEDER SHIPPING CONFIGURATION    LA7SBCR2    LA7SCE    LA7SM    LA7SM1    LA7SM2    LA7SMU2A    ^LAHM(62.93
LA27    LA7SMB    LA7SMP    LA7SMP0    LA7SMU    LA7SMU1    LA7SMU2    LA7SRPT1
LA7SRPT2    LA7SRPT3    LA7VHLU2    LA7VORM    LA7VORM1    LA7VSTP1    ORDERING LOCATION    TEST/PROFILE
^LAHM(62.9    
Lab Service 5 LR302A    LRCE    LRVERA    LRWRKINC    LRWRKLST    
Toolkit 1 ^XTV(8989.51    

Accessed By FileMan Db Calls, Total: 3

Package Total Routines
Automated Lab Instruments 3 LA27    LA7SCE    LA7SMP    

Pointed To By FileMan Files, Total: 2

Package Total FileMan Files
Automated Lab Instruments 2 LAB SHIPPING MANIFEST(#62.8)[.02]    LAB SHIPPING CONFIGURATION(#62.9)[#62.9002(.01)]    

Pointer To FileMan Files, Total: 14

Package Total FileMan Files
Lab Service 7 LABORATORY TEST(#60)[#62.9001(.01)]    TOPOGRAPHY FIELD(#61)[#62.9001(.03)]    COLLECTION SAMPLE(#62)[#62.9001(.09)]    URGENCY(#62.05)[#62.9001(.04)]    LAB ELECTRONIC CODES(#64.061)[#62.9001(1.15), #62.9001(1.25), #62.9001(2.15), #62.9001(2.25), #62.9001(2.35)]    LAB LOINC(#95.3)[#62.9001(1.16), #62.9001(1.26), #62.9001(2.16), #62.9001(2.26), #62.9001(2.36)]    ACCESSION(#68)[#62.9001(.02)]    
Automated Lab Instruments 5 LA7 MESSAGE PARAMETER(#62.48)[.07]    LAB SHIPPING CONFIGURATION(#62.9)[#62.9002(.01)]    LAB SHIPPING CONTAINER(#62.91)[#62.9001(.05), #62.9001(.07)]    LAB SHIPPING METHOD(#62.92)[.08]    LAB SHIPPING CONDITIONS(#62.93)[#62.9001(.06)]    
Kernel 1 INSTITUTION(#4)[.02, .03, .031, .06, #62.9001(.025)]    
Scheduling 1 HOSPITAL LOCATION(#44)[#62.9003(.01)]    

Fields, Total: 18

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

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<3)!'(X'?1P.E) X
  • LAST EDITED:  JUN 04, 1997
  • HELP-PROMPT:  Answer must be 3-30 characters in length.
  • DESCRIPTION:  
    This field is used to give a name to a pair of facilities that have entered into a relationship in which the collecting facility sends the host facility laboratory specimens for clinical testing.
  • CROSS-REFERENCE:  62.9^B
    1)= S ^LAHM(62.9,"B",$E(X,1,30),DA)=""
    2)= K ^LAHM(62.9,"B",$E(X,1,30),DA)
.02 COLLECTING FACILITY 0;2 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  MAR 19, 2002
  • HELP-PROMPT:  Select the institution which will be collecting and shipping lab test specimens.
  • DESCRIPTION:  
    This field is used to designate the collecting facility that is part of a shipping configuration.
  • CROSS-REFERENCE:  62.9^C
    1)= S ^LAHM(62.9,"C",$E(X,1,30),DA)=""
    2)= K ^LAHM(62.9,"C",$E(X,1,30),DA)
  • RECORD INDEXES:  CH (#18)
.03 HOST FACILITY 0;3 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  MAR 19, 2002
  • HELP-PROMPT:  Select the institution which will be the Host facility receiving the lab test shipment.
  • DESCRIPTION:  
    This field is used to designate the host facility that is part of a shipping configuration.
  • RECORD INDEXES:  CH (#18)
.031 HOST FACILITY'S SYSTEM 0;11 POINTER TO INSTITUTION FILE (#4)
************************REQUIRED FIELD************************
INSTITUTION(#4)

  • LAST EDITED:  AUG 13, 1997
  • HELP-PROMPT:  Institution which has host's computer system.
  • DESCRIPTION:  
    The name of the institution which houses the computer system of the host which will be receiving the order.
  • CROSS-REFERENCE:  62.9^E
    1)= S ^LAHM(62.9,"E",$E(X,1,30),DA)=""
    2)= K ^LAHM(62.9,"E",$E(X,1,30),DA)
    This cross reference is used to easily identify the host facility systems during the LEDI setup option.
.04 STATUS 0;4 SET
  • '0' FOR INACTIVE;
  • '1' FOR ACTIVE;

  • LAST EDITED:  APR 21, 1997
  • HELP-PROMPT:  Enter the status of this sending/receiving combination.
  • DESCRIPTION:  
    This field is used to designate whether this shipping configuration is "active", i.e. selectable by the user for use in building, processing and receipting shipments of laboratory test.
.05 COLLECTING FACILITY'S SPEC ID 0;5 SET
************************REQUIRED FIELD************************
  • '0' FOR COLLECTING FACILITY;
  • '1' FOR HOST FACILITY;
  • '3' FOR SAME SYSTEM;

  • LAST EDITED:  MAR 31, 2004
  • HELP-PROMPT:  Select the source of the specimen id provided by the collector.
  • DESCRIPTION:  This field is used to determine the source of the specimen id (Lab UID) used to identify a specimen. It is used by the Host facility when accessioning tests requests from Collecting facilities to determine if the Host
    facility needs to generate a new specimen id/label or use the specimen id/label from the Collecting facility.
    If both the Collecting and Host facilities on operating on the same computer system then select #3 - SAME SYSTEM.
.06 COLLECTING FACILITY'S SYSTEM 0;6 POINTER TO INSTITUTION FILE (#4) INSTITUTION(#4)

  • LAST EDITED:  AUG 05, 1997
  • HELP-PROMPT:  Institution which has collector's computer system.
  • DESCRIPTION:  
    The name of the institution which houses the computer system from which the sender transmitted/sent the order.
  • CROSS-REFERENCE:  62.9^D
    1)= S ^LAHM(62.9,"D",$E(X,1,30),DA)=""
    2)= K ^LAHM(62.9,"D",$E(X,1,30),DA)
    This cross reference is used to easily identify the collection facilities during the LEDI setup.
.07 LAB MESSAGING LINK 0;7 POINTER TO LA7 MESSAGE PARAMETER FILE (#62.48) LA7 MESSAGE PARAMETER(#62.48)

  • LAST EDITED:  MAR 19, 2002
  • HELP-PROMPT:  Enter the message configuration to link to this shipping configuration.
  • DESCRIPTION:  This field is used to link a shipping configuration with an electronic transmission of shipping manifests. When a shipping manifest is shipped, this field is checked to determine if the software should transmit the orders
    on the manifest to the host facility. It identifies the entry in the LA7 MESSAGE PARAMETER file #62.8 to use for building and transmitting the manifest.
  • CROSS-REFERENCE:  62.9^AC
    1)= S ^LAHM(62.9,"AC",$E(X,1,30),DA)=""
    2)= K ^LAHM(62.9,"AC",$E(X,1,30),DA)
    This cross reference is used to identify the LA7 MESSAGE CONFIGURATION entries in the LAB SHIPPING CONFIGURATION file (#62.9).
.08 SHIPPING METHOD 0;8 POINTER TO LAB SHIPPING METHOD FILE (#62.92) LAB SHIPPING METHOD(#62.92)

  • LAST EDITED:  JUN 04, 1997
  • HELP-PROMPT:  Enter the method used to transport a shipment.
  • DESCRIPTION:  
    This field is used to designate the method of shipment used by a shipping configuration. Examples could be courier, taxi, commercial carrier, etc.
.09 BARCODE MANIFEST 0;9 SET
  • '0' FOR NO;
  • '1' FOR YES;
  • '2' FOR YES-COMPACT;

  • LAST EDITED:  MAR 07, 2001
  • HELP-PROMPT:  Should site/patient/specimen information be barcoded on shipping manifest.
  • DESCRIPTION:  This field determines if site/patient/specimen information is barcoded on the shipping manifest when it has a status of "shipped".
    There are two styles of bar codes. The regular style (code="YES"), which was released with the original version of Laboratory Electronic Data Interchange (LEDI), produces a long bar code. If the receiving site, which is
    reading these type of bar codes, has problems then switch to the compact style (code="YES-COMPACT"). This will produce a shorter bar code.
.1 MANIFEST RECEIPT 0;10 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  JUL 01, 1997
  • HELP-PROMPT:  Should a receipt print with shipping manifest for courier to sign.
  • DESCRIPTION:  Allows site to have a receipt printed with a shipping manifest when the status of the manifest is "SHIPPED". This receipt can be used to record acknowledgment of receipt of the shipment by the courier service used to
    transport the specimens to the host facility.
.11 OTHER SYSTEM IDENTIFIER 0;12 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>3!($L(X)<2)!'(X?2.3A) X
  • LAST EDITED:  JUN 24, 2004
  • HELP-PROMPT:  Answer must be 2-3 alpha characters in length.
  • DESCRIPTION:  If this entry is used to communicate with a non-VA, non-DoD system, enter the 2-3 alpha character identifier used to uniquely identify this system.
    This identifier is used in constructing the HL7 application name and facility and resolving identification of institutions during HL7 message building and processing.
    This field is not used when VistA is communicating with a VA or DoD facility. These facilities are identified by their VA station number or DoD DMIS ID respectively.
.12 ACCOUNT NUMBER 0;13 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<1) X
  • LAST EDITED:  SEP 10, 1997
  • HELP-PROMPT:  Answer must be 1-30 characters in length.
  • DESCRIPTION:  
    If the system that you are shipping to requires an account number for billing or other purposes enter the number here. It will be printed on shipping manifests and transmitted in electronic messages if applicable.
.13 INCLUDE UNCOLLECTED SPECIMENS 0;14 SET
  • '0' FOR NO;
  • '1' FOR YES;

  • LAST EDITED:  SEP 25, 1997
  • HELP-PROMPT:  Determines if specimens that have not arrived in lab are built on a shipping manifest
  • DESCRIPTION:  If specimens that are still pending receipt in lab are to build on a shipping manifest then answer "YES". If only specimens that have been received in the lab, i.e. have a lab arrival time, are to build then answer "NO".
    If field is blank then default is "NO".
.14 TEST CODING SYSTEM 0;15 SET
  • '0' FOR NLT;
  • '1' FOR NON-VA;
  • '2' FOR LOINC;

  • LAST EDITED:  FEB 24, 1999
  • HELP-PROMPT:  Answer with type of coding system to use for this configuration.
  • DESCRIPTION:  If orders are being sent to a non-VA facility and the facility can not accept VA test order codes then answer with the type of coding system. "NON-VA" indicates that the other system is using a local coding system. The
    laboratory shipping software will then use the non-VA test codes entered for each test on this configuration.
    If the non-VA facility can accept VA test codes then answer "NLT" and the software will sent VA test order codes.
    VA test order codes are usually NLT codes but in the future may be LOINC codes. Selecting "LOINC" is currently not supported. Support will be added in a future version of the LEDI software when LOINC coding has been
    implemented within VA facilities.
.15 SPECIMEN CODING SYSTEM 0;16 SET
  • '0' FOR HL7 TABLE 0070;
  • '1' FOR LOCAL-NON HL7;

  • LAST EDITED:  JAN 07, 2003
  • HELP-PROMPT:  Answer with type of specimen coding system to use for this configuration.
  • DESCRIPTION:  Collecting facility: If orders are sent to a non-VA facility and the facility can not receive HL7 specimen codes from HL7 table 0070 then answer with the type of coding system "LOCAL".
    Host facility: If orders are received from a non-VA facility and the facility can not transmit HL7 specimen codes from HL7 table 0070 then answer with the type of coding system "LOCAL".
44 ORDERING LOCATION 44;0 POINTER Multiple #62.9003 62.9003

  • DESCRIPTION:  Use this field to specify specific ordering locations used by this configuration. Only those ordering locations defined will attempt to build to a manifest related to this configuration.
    This field is useful when an accession area is shared by a division that has multiple physical locations which ship independently of each other. It allows specimens from selected locations to build to a manifest and avoid
    adding specimens from other locations that match on other criteria - accession area, division, test.
    If there are no ordering locations specified then ordering location will not be a factor is selecting and placing an accession on a manifest related to this configuration.
  • INDEXED BY:  ORDERING LOCATION (AL)
60 TEST/PROFILE 60;0 POINTER Multiple #62.9001 62.9001

  • LAST EDITED:  SEP 15, 1997
  • DESCRIPTION:  This multiple is used to define the tests and criteria that is used to determine which tests/specimens are built on a shipping manifest used by this configuration.
    If you need to have the same test in more than once to support different specimen/urgency criteria then enter the test name enclosed in "" to add the same test.

Global Variables Directly Accessed

Name Line Occurrences  (* Changed,  ! Killed)
^LAHM(62.9 - [#62.9] IXCHSL+1*, IXCHKL+1!, IXCHKEIC+1!, .01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .031(XREF 1S), .031(XREF 1K), .06(XREF 1S)
, .06(XREF 1K), .07(XREF 2S), .07(XREF 2K)

Local Variables

Legend:

>> Not killed explicitly
* Changed
! Killed
~ Newed

Name Field # of Occurrence
>> DA IXCHSL+1, IXCHKL+1, .01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .031(XREF 1S), .031(XREF 1K), .06(XREF 1S), .06(XREF 1K)
, .07(XREF 2S), .07(XREF 2K)
X .01+1!, .01(XREF 1S), .01(XREF 1K), .02(XREF 1S), .02(XREF 1K), .031(XREF 1S), .031(XREF 1K), .06(XREF 1S), .06(XREF 1K), .07(XREF 2S)
, .07(XREF 2K), .11+1!, .12+1!
X(1 IXCHSL+1, IXCHKL+1
X(2 IXCHSL+1, IXCHKL+1
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  Global Variables Directly Accessed |  Local Variables  | All