# PatientPhotoUploadResponse

Model ID: `patient.UploadPhotoResponse`

No description.

Type: `object`

## Fields

| Field | Type | Required | Format | Allowed values | Default | Nullable | Description |
|---|---|---:|---|---|---|---:|---|
| `athena_photo_status` | `string` | Yes |  | linked, skipped_no_athena, skipped_unlinked, failed |  | No | Outcome of mirroring the uploaded photo to Athena. `linked` means Athena created or replaced the image; skipped values mean no Athena write was applicable; `failed` leaves the FHIR photo stored after a non-fatal Athena sync failure. |
| `binary_id` | `string` | Yes |  |  |  | No | FHIR Binary resource ID of the newly stored photo. |
| `openloop_photo_status` | `string` | Yes |  | linked, skipped_no_openloop, skipped_unlinked, failed |  | No | Outcome of mirroring the uploaded photo to the patient's Healthie (OpenLoop) avatar. `linked` means the avatar was set; skipped values mean no Healthie write was applicable; `failed` leaves the FHIR photo stored after a non-fatal sync failure. |
| `steadymd_photo_status` | `string` | Yes |  | linked, skipped_no_steadymd, skipped_unlinked, skipped_no_open_episode, failed |  | No | Outcome of mirroring the uploaded photo to the patient's SteadyMD chart (intake `selfie` file). `linked` means the intake file was attached; `skipped_no_open_episode` means the patient has no open SteadyMD episode yet; `failed` leaves the FHIR photo stored after a non-fatal sync failure. |

## Example

None declared in canonical OpenAPI.