Global: ^INRHT

The INTERFACE TRANSACTION TYPE supplies the formatter process of the interface with information on how the formatter will handle any particular transaction.  The name must be UNIQUE.

1)= S ^INRHT("B",$E(X,1,60),DA)=""

2)= K ^INRHT("B",$E(X,1,60),DA)

1)= D UNQ^INHUT2(DA)

2)= Q

Trigger to set unique ID when .01 entry is first created.

This points to the INTERFACE DESTINATION FILE, which contains the destination for the transaction type.

This field contains the name of the script which is run to generate an interface message. The field is automatically stuffed with the name if the script is created using the script generator.

This field should contain a unique identifier for the transaction type.  Its value will be used in the construction of cms elements in the form of routines.

1)= S ^INRHT("ID",$E(X,1,30),DA)=""

2)= K ^INRHT("ID",$E(X,1,30),DA)

This cross-reference will be used by the field to insure that all entries are unique.

This field designates whether the transaction type is active or inactive.

The application calls a "parent" transaction type, which does not directly generate messages. "Child" transaction types point to the "parent" and do generate messages.

1)= S ^INRHT("AC",$E(X,1,30),DA)=""

2)= K ^INRHT("AC",$E(X,1,30),DA)

children TT that does not have a dependency value is executed last.

Designates Outgoing vs Incoming transaction types.

If this field is non-null, it indicates that messages of this Transaction Type must be acknowledged.  The value placed here is the name of a Transaction Type which is used to send the outgoing acknowledge message.

This is the amount of time between attempts to process entries.  Only entries with the PENDING status will be retried.  Enter a number of hours (nnH), number of minutes (nnM), or number of days (nnD).

Destination file.

required, the transaction is COMPLETE after it is successfully sent.  Otherwise it's status is SENT (Awaiting Acknowledge) following its successful transmission.

implicit value of the 4th parameter of the ^INHF call.  Placing a value in the 4th parameter will override this value. Leaving this blank equates to NOW. An entry of STAT will force the transaction to the top of the queue.

Examples of valid entry are: T-3@1030, NOW-2H, etc.

transactions, or if they all have the same priority, they will be processed in the order received.

as T@0500 or T+1@0200 or NOW-2H.  A value of STAT will force entries to the top of the queue.  Leaving this blank equates to NOW.

have the same priority, they will all be procssed in the order received.

Until August, 1994, priorities were set in field .08 of the Interface Destination File.

and to search for the next available server slot.

acknowledgements. A value in this field will over-ride any value contained in MSH-16 of the incoming message.

This is a description of this transaction type.

This is the API Selective Routing M Code.  Screening logic placed here will be executed at the GIS API (^INHF) process.   This screening logic is applicable to outbound parent transaction types only.

types only.

types only.

This is the Output Controller Inbound Selective Routing M Code.  Screening logic placed here will be executed at the Output Controller process.   This screening logic is applicable to inbound transaction types only.

types only.

This is the Receiver  Selective Routing M Code.  Screening logic placed here will be executed at the Receiver process.   This screening logic is applicable to inbound transaction types only.

This is the Transmitter Selective Routing M Code.  Screening logic placed here will be executed at  the Transmitter process.   This screening logic is applicable to outbound child and replicant transaction types only.