> ## Documentation Index
> Fetch the complete documentation index at: https://help.elationhealth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-07-29

This release adds two tables: `health_maintenance` for preventive care item completions, and `payer` for the payers a practice bills through Elation Billing enriched with the Claim.MD payer directory.

## New Tables

| Table               | Description                                                                                                                                                                           |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| health\_maintenance | One row per health maintenance item completion per patient, with the measure name, completion date, clinician note, quality measure code, and result flags.                           |
| payer               | Payers a practice bills through Elation Billing, combined with the Claim.MD payer directory - payer identity and type, plus which transaction types Claim.MD supports for each payer. |

***

## Release Highlights

**health\_maintenance**

Each row records when a clinician marked a preventive care item as done, including the measure name (e.g., Cervical Cancer Screening), the date of completion, any free-text note entered at the time, and the result flags (`normal_result`, `abnormal_result`) defined by the measure rule. `measure_code` carries the clinical quality measure identifier (CMS or Elation-specific) for practices reporting on quality measures such as HEDIS or CQM. `physician_id`, `firstname`, and `lastname` identify the clinician who recorded the item. Rows with a non-null `deleted_date` have been removed from the patient's chart and should generally be excluded from reporting. See the [Health Maintenance article](/articles/hdb/health-maintenance) for example queries.

**payer**

One row per payer saved on an Elation Billing account, per practice. Each row pairs the payer as your account named it with the matching entry from the Claim.MD payer directory:

* `custom_payer_name` is the name your billing account gave the payer, which may differ from Claim.MD's.
* `claimmd_payer_name` is Claim.MD's canonical name for the same payer.
* `payer_id` is the Claim.MD-issued payer identifier. It is an external clearinghouse reference, not a Hosted Database key.
* `payer_type` is Claim.MD's category for the payer - `commercial`, `medicaid`, `medicare`, `bcbs`, `champus`, or `workerscomp`.
* `payer_alt_names` and `payer_alt_ids` list the other names and ids Claim.MD knows the payer by, where there are any.

The capability columns describe what Claim.MD supports for the payer: `institutional_claims`, `professional_claims`, `dental_claims`, `era`, `eligibility`, `workers_compensation`, `secondary`, `auto_insurance`, and `electronic_attachment`. Each is `yes`, `no`, or `enrollment` - `enrollment` meaning the payer supports it once your practice completes enrollment with them. `avg_era_enroll_days` carries Claim.MD's average number of days for ERA enrollment to complete with that payer.

Claim.MD does not record a value for every payer. Where it has no answer the column is `null`, never an empty string, so test for a missing value with `is null` rather than comparing against `''`. This applies to `payer_type`, to `payer_state` (which is `null` for national payers), and to the capability columns `institutional_claims`, `professional_claims`, `dental_claims`, `era`, `eligibility`, `secondary`, `auto_insurance`, and `electronic_attachment`. Note that a `null` matches neither `= 'yes'` nor `<> 'yes'`, so a filter on one of these columns leaves out the payers with no recorded value - the query below returns only payers Claim.MD explicitly marks as supporting eligibility checks.

`practice_id` joins to `practice` and `account_id` joins to `elation_billing_account`.

To list the payers set up for your practices that support electronic eligibility checks:

```sql theme={null}
select custom_payer_name, claimmd_payer_name, payer_type, era, eligibility
from payer
where is_deleted = false
  and eligibility = 'yes'
order by custom_payer_name
```

<Info>
  The `payer` 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.
</Info>

*If you have any questions about this topic please reach out to [Elation Support Portal](/articles/support-portal-introduction) with the subject line HDB - \<your\_question>*