# Registration source comparison — 16 October 2026

The deployed registration definition was visually compared with the printed questions in `Date_Source/Elderly Input/IMG_1.JPG`, `IMG_2.JPG` and `IMG_3.jpg`. These are filled examples, not blank templates. No handwritten identity, clinical narrative, contact information or signature was transcribed, seeded or used as a default.

| Source area | Registration implementation |
| --- | --- |
| Image 1: program ID, registration date, name, age, sex, address and phone | Identity group; General/clinic ID is retained from the workbook |
| Image 1: living alone and co-resident number, occupation and income | Household group; co-resident details appear when living alone is No |
| Image 1: chronic disease, disability and existing caregiver | Health and care group; workbook categories plus disease narrative; caregiver age/relationship are consolidated in Caregiver details |
| Image 1: other assistance and provider | Other support group, including type, provider and amount |
| Image 1: housing tenure, construction and roof/wall security | Housing group; both “Other” answers have a conditional description. Damage options display percentages, retaining workbook fraction values |
| Image 2: livelihood, income and household expenses | Livelihood group; units and periods are not invented |
| Image 2: MAM check-up, food assistance, social assistance, clinic escort, basic-needs package and housing repair | Six controls in Requested support; source option labels are retained |
| Image 2: caregiver age, family relationship and daily/other activities | One caregiver section; family yes/no and relationship detail remain available; activities are narrative so several can be described |
| Image 2 and image 3 continuation: reason for support | One case-summary narrative rather than a page-break-dependent duplicate |
| Image 3: collection date, collector name and role/department | Assessment controls; collector identity is typed text, with no drawn signature or image upload |
| Image 3: approver comments and approval date | Separate approval narrative/date controls |
| Image 3: registrar name and date | Separate controls, with a combined compatibility value generated for the workbook |
| Workbook additions | General/clinic ID and current program outcome remain available; duplicate caregiver columns are compatibility aliases; reporting year/month are derived concepts |

The final comparison added `housing_tenure_detail` and `housing_type_detail`, and corrected damage display labels to 25%, 50% and 75%. The definition now contains 52 controls in 10 groups. New narrative answers live in the existing encrypted payload; no additional database migration was needed. Browser checks cover conditional retention, local save/offline recovery and sync round-trip for these corrections.

The user subsequently specified the program ID structure: clinic `HTY`, `SPT`, `SDG` or `TL`, year code `26`, and five serial digits, for example `HTY-26-00001`. This confirmed rule supersedes the phase 1 open question about code format. One stored ID field is presented as three entry controls; the source workbook and photos remain unchanged.

The page covers the registration questions with the phase 2 representation decisions documented above. It is not a facsimile of the paper layout or a source-compatible Excel export. Minimum eligibility age, monetary units, single/multiple category policy and drawn signatures remain business decisions; see the phase 1 decisions document. Images 4–5 define follow-up; their implemented checklist mapping is recorded in [PHASE_3.md](PHASE_3.md).
