Clearinghouse transaction

One row per clearinghouse transaction per warehouse. Each row is a lifecycle event for a claim as it moves through the ClaimMD clearinghouse - submitted, acknowledged, accepted or rejected, ERA received, crossed over to another payer, and so on. This data is specific to Elation Billing; there is no EHR-side equivalent. Join to claim and patient for the claim and patient the transaction belongs to. This table’s columns and relationships are shown in the Hosted Database schema.

type is the normalized lifecycle category (for example SUBMITTED, ACKNOWLEDGED, accepted, DENIED, REJECTED, ERA RECEIVED, CROSSOVER). status is the detailed, human-readable message for the same event and often includes the payer name (for example, “Submitted to clearinghouse for <payer>”). claimmd_id is the identifier assigned by the clearinghouse, not a Hosted Database key.

For reporting on but not limited to:

A claim’s progress through the clearinghouse over time
Submission, acceptance, rejection, and denial counts
Transactions for a given claim or patient
Tracing a transaction back to the clearinghouse via claimmd_id

Rejected and denied clearinghouse transactions

select
    t.created_timestamp
  , p.full_name
  , t.claim_id
  , t.type
  , t.status
from clearinghouse_transaction t
  left join patient p on p.id = t.patient_id
where t.type in ('REJECTED', 'DENIED')
  and not t.is_deleted
order by t.created_timestamp desc;

If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>

Elation SSO UserResolve the Elation Billing user on claims, payments, and financial transactions back to the Elation EHR user.

⌘I

Hosted Database

Overview

How Tos

Common Queries

Elation Billing

Frequently Asked Questions

Changelog

Rejected and denied clearinghouse transactions

​Rejected and denied clearinghouse transactions

Rejected and denied clearinghouse transactions