Data Element ST02 is defined as an alpha-numeric field. Our Agency has imposed additional constraints upon the syntax requiring that this field be restricted to numeric data only.
We have a complaint from a provider stating that we are violating X12 guidelines for the 276 transaction; specifically failing to accept alphanumeric character strings in the ST02 data element.
Our position is that even though the element ST02 is defined as alpha-numeric, the Implementation guide allows us to impose additional restrictions on the syntax such as only allowing numeric values.
1. The example provided in the EDI Implementation guide uses only numeric values.
2. A previous RFI response said, "An implementation guide could impose a constraint that each functional group start a new sequence of ST02 values starting at the value 1 and incrementing by 1". This references only numeric values.
The ST02 element is defined by the X12 Standard as an alphanumeric (AN) value. The 'AN' element is a sequence of characters from the basic or extended character sets, which includes numeric values or numbers.
The 005010X212 (276/277) TR3 ST02 element name is Transaction Set Control Number, and the element note states: The Transaction Set Control Numbers in ST02 and SE02 must be identical. The number is assigned by the originator and must be unique within a functional group (GS-GE). For example, start with the number 0001 and increment from there.
The note states 'The number' (i.e. numeric value) as opposed to 'The value' (which could be numeric, alphabetic or special characters) and also provides a numeric example for creating uniqueness. Therefore the intent of the 5010 276/277 TR3 element note, establishes the ST02 as only allowing a number or numeric value that must be unique within the group and interchange.
See RFI #2308 and the Formal Response to RFI #2329. RFI #2244 has been identified as being incorrect and will be addressed by the X12 Standards body.