Skip to main content
This release adds a granular billing_status_detail column and provider reference columns to the bill table, exposing the provider roles recorded in the visit note billing section.
Early release. These columns are available now to early-release Hosted Database clients and become generally available on the standard bill table on 2026-07-13.

​
Schema Changes

TableColumnDescription
billbilling_status_detailDetailed billing status for each bill
billrendering_provider_id, supervising_provider_id, billing_provider_id, referring_provider_idProvider roles from the visit note billing section

​
Release Highlights

Billing Status Detail The existing billing_status column collapses eight underlying bill statuses into four categories (Unbilled, Billed, UnresolvedError, ResolvedError). The new billing_status_detail column exposes the full status shown in Billing Home, so you no longer have to reconstruct it. billing_status is unchanged. Values:
StatusMeaning
Awaiting sign-offUnbilled, visit note not yet signed
SignedUnbilled, visit note signed
Received by PMSBilled
Sent to PMSTransmitted to a PMS
Marked as billedBilled manually
Failed to sendErrored (unresolved or resolved)
Provider reference columns on bill The bill table now carries the provider roles from the visit note billing section. Previously only visit_note.physician_user_id was available, which does not always match the rendering provider shown on the bill. Three of the columns identify Elation user accounts. Resolve them to provider name, NPI, and credentials by joining the user table on user.physician_id:
  • rendering_provider_id — the provider who rendered the services on the bill.
  • supervising_provider_id — the supervising provider.
  • billing_provider_id — the billing provider (for example, incident-to billing).
select
    b.id as bill_id
  , ru.first_name as rendering_first_name
  , ru.last_name  as rendering_last_name
from bill b
left join user ru on ru.physician_id = b.rendering_provider_id
The remaining column is a record ID into the bill’s referring-provider record, not a user account:
  • referring_provider_id — the referring-provider record; its name and state are already surfaced on bill as referring_provider and referring_provider_state.
Join the three user-backed *_provider_id columns to user on user.physician_id, not user.id.
If you have any questions about this topic please reach out to Elation Support Portal with the subject line HDB - <your_question>