Patient Statement Tracking

Billing statement state from Elation Billing, one row per patient rather than per statement - how many statements have been sent, when the most recent one was sent, and whether statements should be sent to the patient at all. Join back to patient via patient_id for demographics. This table’s columns and relationships are shown in the Hosted Database schema.

patient_statement_tracking.patient_id joins to patient.id and is null when the Elation Billing patient does not map to an EHR patient.

For reporting on but not limited to:

Patients who have never been sent a statement
When each patient was last sent a statement
Patients excluded from statements via the send_stmt flag

Statement status per patient

Returns each patient’s statement state, joined to patient for the name, with a never_sent_statement flag derived from last_statement. Order by last_statement for the most recent send, or filter to never_sent_statement = true for patients who have never been sent one.

select
    pst.patient_id
  , p.full_name
  , pst.statement_counter
  , pst.last_statement
  , pst.send_stmt
  , pst.last_statement is null as never_sent_statement
from patient_statement_tracking pst
  left join patient p on p.id = pst.patient_id
where pst.is_deleted = false
order by pst.last_statement desc nulls last;

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

⌘I

Hosted Database

Overview

How Tos

Common Queries

Elation Billing

Frequently Asked Questions

Early Release

Changelog

Statement status per patient

​Statement status per patient

Statement status per patient