clearinghouse_message, the individual messages the ClaimMD clearinghouse returns against a claim submission.
New Tables
Release Highlights
clearinghouse_message One row per message the clearinghouse returned within a clearinghouse transaction, so a single transaction usually has several messages. Join onclearinghouse_transaction_id, or filter directly using claim_id and practice_id, which are copied from the parent transaction.
message_subject and message change meaning together. On a validation or scrubbing message, message_subject names the claim form field at fault (diag_1, ins_number, prov_npi) and message is readable text such as “Diagnosis code invalid [R108].” On a message derived from an ERA, message_subject is a label (Total Paid, ICN, Paid Date) and message holds that label’s value. message_code distinguishes the two: it is populated for messages the clearinghouse returned against a submission and null for ERA-derived rows and Elation Billing’s own scrubbing status lines, so filter with message_code is not null for submission responses.
Only messages the clearinghouse linked back to a transaction are included. The rest are mostly acknowledgments, plus payer denial reason lines that arrive with a remittance rather than a claim submission, and cannot be attributed to a practice. Use clearinghouse_transaction.type for the acknowledgment lifecycle, and era_matched_adjustment for denial reason analysis - it carries the payer’s adjustment and remark codes with the amounts and the claim they apply to.
clearinghouse_message is documented together with its parent table in the Clearinghouse transactions and messages article.
The
clearinghouse_message table is present only for practices on the Elation Billing product. If your practice is not on Elation Billing, it is not created in your Hosted Database.