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

# The Insurance Card Image Object

> The scanned front and back of a patient's insurance card, returned as time-limited download URLs.

## In the EHR

Practice staff attach a photo or scan of the patient's insurance card to the coverage it belongs to, from the same **Insurance, Payment & Membership** section of Demographics where the policy itself is recorded, using **Upload Front** and **Upload Back**. Staff can then view, replace, or remove either side from the patient's chart. See [Patient Demographics Guide - Insurance Management](/articles/Patient-Demographics-Insurance-Management).

## Working with insurance card images via the API

**Card images belong to the policy they were uploaded against.** These endpoints address images by policy, and an upload is recorded against the policy it was sent to, so another policy on the same patient carries its own images. Upload images against the policy you want them to appear on.

**Uploads are accepted for processing rather than stored before the response returns.** A success means the images were accepted, and they become available from this endpoint shortly afterwards. Read the card images back when you need to confirm an upload landed.

**The returned URLs are temporary.** Each one grants time-limited access to the image and stops working once it lapses, so fetch the images again when you need them rather than storing a URL for later use.

**A delete removes one side of the card.** Each call takes a single `image_rank`, so removing both sides takes two calls and leaves the policy with no card images.

## Field notes

* `image_1` and `image_2` on upload are the front and the back of the card, and are the same two images the delete endpoint addresses as `image_rank` 1 and 2.