RFI Browser

Back  RFI # 1498: Trailing Delimiters and 999

Formal vs. Informal Help Informal Formal

Submitter

Todd Cochrane

Description

In HIPAA 5010 TR3 B.1.1.3.10 Absence of Data "Optional simple data elements and/or composite data structures and their preceding data element separators that are not needed must be omitted if they occur at the end of a segment."

In X12 5010 CHM 3.7.4 Absence of Data "Optional simple data elements and composite data structures and their preceding data element separators that are not needed shall be omitted if they occur at the end of a segment; ..."

For example: Assuming that * is the data element separator and ~ is the segment terminator and UM05 and UM06 are both optional data elements in the segment (sic).

UM*SC*I*3*11:B**~

If we are interpreting the above rule correctly then this situation must result in an X12 EDI syntax error. However, we are still seeing data being traded with this excess trailing data element separators (and with excess trailing composite separators). If this is to be trapped and reported, what IK304/IK403 would be the clearest reporting on the 999?

Submitter Assigned Keywords

Should Shall Must IK3

Response

Your interpretation and examples concerning the use of three words, should, shall and must, is correct. Usage of the words must, shall and should are as follows. Must and shall convey an absolute requirement. Should conveys a recommendation that can be ignored in circumstances that may be restricted. Your example demonstrates the incorrect usage of the data element separator.

Your second question, concerning reporting the errors in the example would be to use code 8 – “Segment has data element errors” in the IK304 and code value 3 – “Too many data elements” in the IK403. If the example referenced a composite data element, the appropriate value for IK403 is 13 – “Too many components”.

FURTHER DISCUSSION
During the creation and discussion of this RFI, X12C subcommittee members agreed more descriptive codes would be helpful in reporting the error within the example. Additional codes will be added to a future version of the 999 transaction set.

Recommendation

The official response to a formal RFI is a letter from the current ASC X12 chair. This website often displays a summary of the RFI. Click here to view a PDF of the letter for this RFI.
Submission 1/20/2012
Status Date 1/20/2012
Status F - Final
Primary References
Document 005010X231
Section1