OAR 436-160-0420: Medical Bill Acknowledgement

(1)(a) The sender is expected to retrieve both TA1 and 999 interchange and functional acknowledgements (as defined by ASC X12) for each medical bill file submitted, unless technical errors in the file prevent 999 processing. In addition, the sender is expected to retrieve the 824 detailed acknowledgement, as defined by IAIABC Release 2.0 (Feb.1, 2014) for each medical bill file submitted, if at least one transaction has successfully passed the 999 edits. (b) The detailed acknowledgement will indicate either an item accepted (IA) or an item rejected (IR) acknowledgement for each individual transaction. (2) A TA1, 999 or 824 acknowledgement will be available for all transactions the division is unable to process, including but not limited to: (a) An omitted mandatory data element; (b) An improperly populated data element field, e.g., numeric data element field is populated with alpha or alphanumeric data, or is not a valid value according to the standards adopted in 436-160-0004; (c) Transactions or electronic records within the transaction that require matching, and cannot be matched to the division's database, e.g., cancellation of an original bill that does not match the Unique Bill ID; (d) Illogical data in mandatory or required conditional field, e.g., payment date is after reporting date; (e) Duplicate transmission or duplicate transaction within the transmission; (f) Invalid bill submission reason code; or (g) Illogical event sequence relationship between transactions, e.g., cancellation transaction submitted before an original bill is accepted. (3) A transaction accepted acknowledgement will be available for all transactions that are in a format capable of being processed by the division's information processing system and that are not rejected under section (2) of this rule. (4) An insurer’s obligation to report medical bill data for the purposes of this rule is not satisfied unless the division acknowledges acceptance of the transaction.