Global: ^INTHL7F

This is the name of the Script Generator Field.

1)= S ^INTHL7F("B",$E(X,1,50),DA)=""

2)= K ^INTHL7F("B",$E(X,1,50),DA)

1)= F %=1:1 Q:$P(X," ",%,99)=""  S I=$P(X," ",%) I $L(I)>2,$L(I)<31,^DD("KWIC")'[I S ^INTHL7F("C",I,DA)=""

2)= F %=1:1 Q:$P(X," ",%,99)=""  S I=$P(X," ",%) I $L(I)>2,$L(I)<31 K ^INTHL7F("C",I,DA)

Enter the type of data element this will be.  The choices are from the HL7 data type table.

This is the maximum length that this field can be.

If the data location for this field is a WP field, then this will indicate if the incoming data should be appended to any current data or replace anything that may be there.  Default value if left null will be OVERWRITE.

If this field is set to YES then the generated input template line for this field will be created using a //// stuff instead of the normal ///.

If set to YES, if a null value appears in the receiving system the field will be deleted.

This designates whether the field length will be fixed, variable or minimum/maximum in the interface message sent to a remote system.

If the field is a minimum/maximum field length type (such as is used in X.12 messaging), this value will be the minimum.

If the field length type is fixed or minimum/maximum, this field designates the character which will be used to pad the value up to the required length.

If the field length type is fixed or minimum/maximum, this field determines whether the data value is padded to the left or to the right with the character designated in the field PAD CHARACTER.

FieldNumber:FileNumber ex (1.02:2.95) or

FieldName:FileNumber   ex (TYPE OF DISPOSITION:2.95) or

FieldName:FileName     ex (FMP/SSN:PATIENT) or

FieldNumber:FileName   ex (8000:PATIENT) or

FieldNumber  ex (8000) when FileName can be determined from the context, or

FieldName    ex (FMP/SSN) when FileName can be determined from the context.

Used when the DATA TYPE does not reflect the true data type.  ex String data is sometimes used for data that has been extracted and formatted using application code.

This contains the field identifier as specified by an interface standard. For example, the NCPDP standard specifies a unique identifier for each field in the NCPDP data dictionary.

This is a description of this field.

This is MUMPS code used to validate this field in incoming data.  The value of the data will be in the variable X.  The code should kill X if the data is invalid.

Enter 'Y' for year, 'L' for month, 'D' for day, 'H' for hour, 'M' for minute, 'S' for second, or '1' for auto precision (which indicates    to determine the precision based on the data

HL7 V2.3 Standard Examples (assuming Auto Precision):

Outbound:

For "1" : 2950625.15 converts to 19950625150000\M

For "2" : 2950625.15 converts to 19950625150000

For "3" : 2950625.15 converts to 1995062515

Inbound:

For "1" : 19971129100000\D converts to 2971129

"2" is not used for inbound conversions

For "3" : 19971129 converts to 2971129

enter '2' to subtract 1 second

enter '3' to subtract 1 minute .... For inbound enter '1' to subtract 1 day and set time to 2400

enter '2' to add 1 second

enter '3' to add 1 minute

Examples when Day offset:

outbound:

For "1" : FileMan dt/tm - 2971011.24  HL7 dt/tm 19971012000000

For "3" : Fileman dt/tm - 2971011.24  HL7 dt/tm 19971011235900\M

inbound:

For "1" : HL7 dt/tm 19971012000000 FileMan dt/tm 2971011.24

For "3" : HL7 dt/tm 19971012000000 FileMan dt/tm 2971012.0001

Example -

Enter '1' to substitute left~R~right to left|right

a part.

This field can be used to override the Incoming Transformation for the specified Data Type of this field.

Use this field to override the Outgoing Transform given for the specified data type of this field.

This contains additional code to be placed in a generated input template prior to the store command for this field.  It must be valid input template code.

recursive pointer.

table and then translated to the local system's corresponding value.