Five steps from a problem to its solution.

Help me design and build a first working prototype for this problem in Sikar, Rajasthan, India.

Problem: Workers with silicosis in Rajasthan can't see why their certification was cancelled, so they miss the monthly relief they depend on.
Who it hurts: Former mine and stone-crushing workers in Sikar, Kotputli-Behror and other mining districts with silicosis, many bedridden, and the widows and children who apply for them.
The moment it hurts: After registering on the portal and getting a chest X-ray, finding the registration cancelled again with no reason given and no one to ask.
What people do today: Patients register online, often with a relative's help, travel repeatedly to community health centres or district hospitals for examination and an X-ray, and wait for a doctor they never meet to decide.
Why it is still unsolved: Registration, the X-ray, the medical review and relief payment are separate steps handled by different people, and the applicant sees only the final status, not which step failed or what to fix.
What solved looks like: A status page and SMS for each applicant showing every step (registered, X-ray done, under review, certified or rejected), the reason for any rejection in Hindi, what to do next, and the nearest centre for a repeat test, so fewer people drop out after the first try.
Where: Sikar, Rajasthan, India

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.