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 |  All
Print Page as PDF
Global: ^INTHL7M

Package: IHS Generic Interface System

Global: ^INTHL7M


Information

FileMan FileNo FileMan Filename Package
4011 SCRIPT GENERATOR MESSAGE IHS Generic Interface System

Description

Directly Accessed By Routines, Total: 67

Package Total Routines
IHS Generic Interface System 56 INHD    INHMG1    INHMG2    INHMGD    INHMGD1    INHMGD11    INHMGD2    INHMGD6
INHMGD7    INHMGD8    INHMGD9    INHPCO1    INHPSA    INHSG    INHSGZ    INHSGZ1
INHSGZ2    INHSGZ23    INHSYS01    INHSYS02    INHSYSU1    INHUT    INHUTIL    INHUVUT1
INMPORT    INTSTR    INTSTR1    INXHR08    INXHR081    INXPORT    IS00006    IS00007
IS00008    IS00009    IS00010    IS00011    IS00012    IS00013    IS00014    IS00015
IS00016    IS00017    IS00018    IS00019    IS00020    IS00021    IS00022    IS00023
IS00024    IS00025    IS00026    IS00027    IS00028    IS00029    IS00030    IS00031
IHS Support HL7 Interfaces 4 BHLFO    BHLMSH    BHLRDXM    BHLU    
IHS Immunizations Interface 3 BYIMIMM2    BYIMPORT    BYIMSEGS    
Data Warehouse Export System 2 BDW10P4    BDW10P5    
IHS Changes To Lab 2 BLRRLU    BLRRPOST    

Accessed By FileMan Db Calls, Total: 13

Package Total Routines
IHS Generic Interface System 6 INHMG    INHMGD    INHSG    INHSGZ    INMPORT    INXPORT    
IHS Support HL7 Interfaces 3 BHLRDXM    BHLU    BHLXAC    
IHS Changes To Lab 2 BLRRLU    BLRRPOST    
Data Warehouse Export System 1 BDW10P4    
IHS Immunizations Interface 1 BYIMPORT    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
IHS Generic Interface System 3 INTERFACE SCRIPT(#4006)[100, 101]    INTERFACE TRANSACTION TYPE(#4000)[#4011.02(.01)]    SCRIPT GENERATOR SEGMENT(#4010)[#4011.01(.01), #4011.01(.11)]    
VA Fileman 1 FILE(#1)[.05, #4011.01(.05)]    

Fields, Total: 42

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

  • INPUT TRANSFORM:  K:X["""" X I $D(X) K:$L(X)>45!($L(X)<3)!'(X'?1P.E)!'$$ISNS^INHUT2(X) X
  • LAST EDITED:  JUL 13, 1995
  • HELP-PROMPT:  Answer must be 3-45 characters in length and properly name-spaced
  • DESCRIPTION:  
    This is the name of the Script Generator Message.
  • EXECUTABLE HELP:  D:$D(DW)>1 MSG^INHUT2
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  4011^B^MUMPS
    1)= S ^INTHL7M("B",$E(X,1,45),DA)=""
    2)= K ^INTHL7M("B",$E(X,1,45),DA)
.02 EVENT TYPE 0;2 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>20!($L(X)<2) X
  • LAST EDITED:  MAY 06, 1991
  • HELP-PROMPT:  Answer must be 2-20 characters in length
  • DESCRIPTION:  
    Enter the event type corresponding to this type of message.  This value will be placed in the ENV segment for outgoing messages and will be looked for in that segment in incoming messages.
.03 PROCESSING ID 0;3 SET
************************REQUIRED FIELD************************
  • 'P' FOR PRODUCTION;
  • 'D' FOR DEBUG;
  • 'T' FOR TRAINING;

  • LAST EDITED:  MAY 08, 1991
  • DESCRIPTION:  
    This value corresponds to the PROCESSING ID in the Message Header segment of a message.
.04 VERSION 0;4 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>5!($L(X)<1) X
  • LAST EDITED:  MAY 19, 2000
  • HELP-PROMPT:  Answer must be 1-5 characters in length.
  • DESCRIPTION:  
    This corresponds to the VERSION ID value in the Message Header segment.
.05 ROOT FILE 0;5 POINTER TO FILE FILE (#1)
************************REQUIRED FIELD************************
FILE(#1)

  • LAST EDITED:  OCT 07, 1993
  • DESCRIPTION:  This is the root file upon which this message is based. As with all of FileMan, data extraction and processing has to begin in a "home" file. This field contains that "home" file upon which all navigations, etc. are
    based and entry numbers are given for.
.06 MESSAGE TYPE 0;6 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>10 X
  • LAST EDITED:  DEC 18, 1995
  • HELP-PROMPT:  Answer must be 1-10 characters in length
  • DESCRIPTION:  This is used to tell the receiving system the subsystem to which this message belongs. Example values are: ADT, ORM, ORU, etc. This field is used to populate the MSH-9 field.
    If the Event Type field is populated it will be appended onto this field in the MSH (ex. ADT\A28).
    Special variables (ex. @MSGTYPE) may also be used.





.07
LOOKUP PARAMETER
0;7
SET 

************************REQUIRED FIELD************************
  • 'F' FOR FORCED LAYGO;
  • 'L' FOR LAYGO ALLOWED;
  • 'N' FOR NO LAYGO;
  • 'O' FOR LOOKUP ONLY;
  • 'P' FOR PARSE ONLY;
  • LAST EDITED:  MAR 13, 1992
  • DESCRIPTION:  This value is used for incoming data to determine which entry in the local database is to be updated.  It affects how a lookup is done as follows:
    FORCED LAYGO = a new entry in the root file will always be created.
    LAYGO ALLOWED = an attempt will be made to match the incoming data to that already in the local database (using the fields identified as being used for lookup).  If the attempt fails, then a new entry will be created.
    NO LAYGO = an attempt will be made to match the incoming data to that already in the local database as in the LAYGO ALLOWED case, but if the match fails, an error will be generated and no new entry will be made.
    LOOKUP ONLY = perform the lookup but no storing operations for the root file.





.08
INACTIVE FLAG
0;8
SET

  • '0' FOR NO;
  • '1' FOR YES;
  • LAST EDITED:  JAN 22, 1992
  • DESCRIPTION:  
    Entering YES here will mark this message as inactive and it will not be generated.





.09
AUDITED
0;9
SET

  • '0' FOR NO;
  • '1' FOR YES;
  • LAST EDITED:  JAN 25, 1992
  • DESCRIPTION:  If this field is set to YES, audit information will be generated for a transaction processed with the script generated from this message.  Code will automatically be inserted into the generated script to compile the
    necessary audit information.





.1
ACCEPT ACKNOWLEDGEMENT
0;10
SET

  • 'AL' FOR ALWAYS;
  • 'NE' FOR NEVER;
  • 'ER' FOR ERROR/REJECT;
  • 'SU' FOR SUCCESS ONLY;
  • LAST EDITED:  OCT 24, 1994
  • HELP-PROMPT:  Enter the HL7 code which indicates the type of accept acknowledgement that is required for this message.
  • DESCRIPTION:  
    This field will place a code in the message header indicating the type of accept acknowledgement that is required from the receiving system.





.11
APPLICATION ACKNOWLEDGEMENT
0;11
SET

  • 'AL' FOR ALWAYS;
  • 'NE' FOR NEVER;
  • 'ER' FOR ERROR/REJECT;
  • 'SU' FOR SUCCESS ONLY;
  • LAST EDITED:  OCT 24, 1994
  • HELP-PROMPT:  Enter the type of application acknowledgement required of the receivng system.
  • DESCRIPTION:  
    This field places a code in the message header which inidicates the type of application acknowledgement that is required of the receiving system.





.12
STANDARD
0;12
SET 

************************REQUIRED FIELD************************
  • 'HL7' FOR HL7;
  • 'NCPDP' FOR NCPDP;
  • 'X12' FOR X12;
  • 'ADSI' FOR ADSI;
  • 'HTML' FOR HTML;
  • 'XML' FOR XML;
  • LAST EDITED:  JUN 07, 1999
  • HELP-PROMPT:  Enter the protocol standard that this interface is based on (e.g. HL7.)
  • DESCRIPTION:  
    The STANDARDS set of codes represents the protocol standard that will be used by the Generic Interface System to properly format or parse messages.





1
SEGMENTS
1;0
POINTER Multiple #4011.01
4011.01
  • LAST EDITED:  JUL 13, 1995
  • DESCRIPTION:  
    This is the multiple that contains the segments for the message.





2
TRANSACTION TYPE MULTIPLE
2;0
POINTER Multiple #4011.02
4011.02
  • DESCRIPTION:  This is a Transaction Type to which the generated script for this message type will be attached.  When generating scripts, the DIRECTION field in the Transaction Type file for the pointed-to entries will be used to
    determine the type of script to build.





3
DESCRIPTION
3;0
WORD-PROCESSING #4011.03

  • DESCRIPTION:  
    This is the description of the message.





4
MUMPS CODE FOR LOOKUP
4;0
WORD-PROCESSING #4011.06   

  • DESCRIPTION:  This is MUMPS code which will be placed in the script prior to the lookup on the root file.  If this code sets INDA to a non-null and non-zero value it will be used as the entry in the root file and the regular lookup will
    not be performed.





5
LOOKUP/STORE ROUTINE
5;E1,200
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>60!($L(X)<2) X
  • LAST EDITED:  MAR 13, 1992
  • HELP-PROMPT:  Answer must be 2-60 characters in length
  • DESCRIPTION:  
    If this field is entered, it will contain the name of a routine (with tag and parameters, if desired) which should be used to conduct all lookup and storing operations.





6
OUTGOING INITIAL MUMPS CODE
6;0
WORD-PROCESSING #4011.08   

  • DESCRIPTION:  This is MUMPS code that will be executed only in outgoing scripts.  It will be executed prior to the DATA section.  This code will be included in a MUMPS section.
    Error flagging can be done here for the message.





7.01
SENDING APPLICATION
7;1
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>45 X
  • LAST EDITED:  SEP 14, 1993
  • HELP-PROMPT:  Answer must be 1-45 characters in length
  • DESCRIPTION:  
    This is used for the HL7 MSH segment.  This identifies the CHCS application.





7.02
SENDING FACILITY
7;2
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>45 X
  • HELP-PROMPT:  Answer must be 1-45 characters in length
  • DESCRIPTION:  
    This is used for the HL7 MSH segment.  This identifies the CHCS facility.





7.03
RECEIVING APPLICATION
7;3
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>45 X
  • HELP-PROMPT:  Answer must be 1-45 characters in length
  • DESCRIPTION:  
    This is used for the HL7 MSH segment.  This identifies the application from the external system.





7.04
RECEIVING FACILITY
7;4
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>45 X
  • HELP-PROMPT:  Answer must be 1-45 characters in length
  • DESCRIPTION:  
    This is used for the HL7 MSH segment.  This identifies the facility of the external system.





12.01
X12 AUTHOR INFO QUALIFIER
12;1
SET

  • '00' FOR No authorization information present.;
  • '03' FOR Additional Data ID.;
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Enter the code to identify the type of authorization info.
  • DESCRIPTION:  
    This code is used to identify the type of authorization information.  Field number is ISA01.





12.02
X12 AUTHOR INFORMATION
12;2
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>10!($L(X)<0) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 0-10 characters in length.
  • DESCRIPTION:  
    Additional identification or authorization.  Field number is ISA02.





12.03
X12 SECURITY INFO QUAL
12;3
SET

  • '00' FOR No security info. present.;
  • '01' FOR Password.;
  • OUTPUT TRANSFORM:  S Y=Y
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Enter code to identify the type of security info.
  • DESCRIPTION:  
    Code to identify the type of security information.  Field number is ISA03.





12.04
X12 SECURITY INFORMATION
12;4
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>10!($L(X)<0) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 0-10 characters in length.
  • DESCRIPTION:  
    Additional information about the interchange sender or the data of the interchange. Field number is ISA04.





12.05
X12 INTERCHANGE ID QUAL S
12;5
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>2!($L(X)<2) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 2 characters in length.
  • DESCRIPTION:  
    Code to identify the method of code structure used.  Field number is ISA05.





12.06
X12 INTERCHANGE SENDER ID
12;6
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<0) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 0-15 characters in length.
  • DESCRIPTION:  
    Identification code published by the sender.  Field numberis ISA06.





12.07
X12 INTERCHANGE ID QUAL R
12;7
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>2!($L(X)<2) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 2 characters in length.
  • DESCRIPTION:  
    Code to identify the method of code structure used.  Field number is ISA07.





12.08
X12 INTER RECEIVER ID
12;8
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<0) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 0-15 characters in length.
  • DESCRIPTION:  
    Identification code published by the receiver.  Field number is ISA08.





12.09
X12 FUNCTIONAL ID CODE
12;9
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>2!($L(X)<2) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 2 characters in length.
  • DESCRIPTION:  
    Code indicating a group of application related transaction sets.  Field number is GS01.





12.1
X12 APPL SENDER CODE
12;10
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<2) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 2-15 characters in length.
  • DESCRIPTION:  
    Code to identify party receiving transmission.  Field number is GS02.





12.11
X12 APPL RECEIVER CODE
12;11
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>15!($L(X)<2) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 2-15 characters in length.
  • DESCRIPTION:  
    Code to identify party receiving transmission.  Field number is GS03.





12.12
X12 INTER CTRL VERSION NUM
12;12
NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>99999)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Type a Number between 0 and 99999, 0 Decimal Digits





12.13
X12 VERSION ID CODE
12;13
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>12!($L(X)<0) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 0-12 characters in length.
  • DESCRIPTION:  
    Code indicating version, release, subrelease and industry of standard used. Field number is GS08.





12.14
X12 ACK REQUESTED
12;14
SET

  • '0' FOR No Ack requested.;
  • '1' FOR Ack requested.;
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Enter a code to indicate whether an Ack is required.
  • DESCRIPTION:  
    Code to indicate whether an interchange ack is required.  Field number is ISA14.





12.15
X12 USAGE INDICATOR
12;15
SET

  • 'T' FOR Test;
  • 'P' FOR Production;
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Enter the code to indicate test or production data.
  • DESCRIPTION:  
    Code to indicate whether this interchange is test or production data.  Field number is ISA15.





12.16
X12 TRANSACTION SET ID CODE
12;16
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>3!($L(X)<3) X
  • LAST EDITED:  APR 04, 2001
  • HELP-PROMPT:  Answer must be 3 characters in length.
  • DESCRIPTION:  
    Code to identify this transaction set.  Field number is ST01.





100
INPUT SCRIPT
S;1
POINTER TO INTERFACE SCRIPT FILE (#4006)
INTERFACE SCRIPT(#4006)
  • LAST EDITED:  MAY 07, 1991
  • DESCRIPTION:  This is the script that was generated for this message for incoming transactions.  Only one incoming script is generated per script generator message. All incoming transaction types then make use of this script.  This
    field should only be updated by the system.





101
OUTPUT SCRIPT
S;2
POINTER TO INTERFACE SCRIPT FILE (#4006)
INTERFACE SCRIPT(#4006)
  • LAST EDITED:  FEB 17, 2000
  • DESCRIPTION:  This is the script that was generated for this message for outgoing transactions.  Only one outgoing script is generated per script generator message.  All outgoing transaction types then make use of this script.  This
    field should only be updated by the system.
  • CROSS-REFERENCE:  4011^O
    1)= S ^INTHL7M("O",$E(X,1,30),DA)=""
    2)= K ^INTHL7M("O",$E(X,1,30),DA)





9999999.01
FIELD SEPARATOR
FS;1
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>1!($L(X)<1) X
  • LAST EDITED:  APR 12, 2000
  • HELP-PROMPT:  Answer must be 1 character in length.





9999999.02
ENCODING CHARACTERS
EC;E1,4
FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>4!($L(X)<1)!'(X?1.4P) X
  • LAST EDITED:  APR 12, 2000
  • HELP-PROMPT:  Answer must be 1-4 characters in length.







    



Info | 
Desc | 
Directly Accessed By Routines | 
Accessed By FileMan Db Calls | 
Pointer To FileMan Files | 
Fields | 
All