Skip to main content
One row per note per claim - the trail of notes billers build up on an Elation Billing claim as they work it. Each row carries the note text, the Elation Billing user who wrote it, and when it was written. Every note is attributed to a user, so this table is the record of who touched a claim and what they said about it. Filter on is_deleted = false to exclude notes that have since been removed. This table’s columns and relationships are shown in the Hosted Database schema.
claim_note.claim_id is the Elation Billing claim id and joins to claim.id - it is not an EHR bill id. claim_note.elation_billing_user_id joins to elation_billing_user.id and is an Elation Billing user identifier, not an Elation EHR user id.
For reporting on but not limited to:
  • The full note history on a single claim, in the order it was written
  • Which biller last touched a claim, and when
  • Note volume per biller over a date range
  • Notes flagged to count toward a patient’s statement (is_statement_note = true)
  • Auditing follow-up on denied or aging claims by pairing notes with claim status

Note history for a claim

Returns every note on a single claim, oldest first, with the name and login of the biller who wrote it.

Claims by who last touched them

Returns the most recent note on each claim, so you can see which biller worked a claim last and how long ago.

Note volume per biller

Ranks billers by how many claim notes they wrote over the last 90 days.

Statement notes for a patient

Returns only the notes flagged to count toward a patient’s statement, across every claim for that patient.
If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>