> ## 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.

# Patient Guarantor

> Look up the responsible party (guarantor) recorded for a patient in Elation Billing.

One row per patient per warehouse holding responsible-party (guarantor) demographics from Elation Billing - whoever is financially responsible for the patient's account, often the patient themselves, sometimes a parent, spouse, or other party. HDB `patient` remains the source of truth for the patient's own demographics; this table carries only the responsible-party fields, which have no EHR equivalent.

This table's columns and relationships are shown in the [Hosted Database schema](/articles/hdb/schema).

<Note>
  `patient_guarantor.patient_id` joins to `patient.id` and is null when the Elation Billing patient has no crosswalk to an HDB patient. The responsible party's SSN is intentionally not exposed.
</Note>

**For reporting on but not limited to:**

* Responsible-party contact details for billing follow-up
* Patients whose guarantor is someone other than themselves
* Guarantor mailing addresses for statements

## Responsible-party (guarantor) details

Pulls the full responsible-party record - contact details and mailing address - for each patient's Elation Billing account. Add `and pg.patient_id = <patient_id>` to look up a single patient.

<CodeGroup>
  ```sql sql theme={null}
  select
      pg.patient_id
    , pg.resp_first_name
    , pg.resp_last_name
    , pg.resp_dob
    , pg.resp_phone
    , pg.resp_email
    , pg.resp_address1
    , pg.resp_address2
    , pg.resp_city
    , pg.resp_state
    , pg.resp_zip
  from patient_guarantor pg
  where pg.is_deleted = false;
  ```
</CodeGroup>

*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>*