This is the complete requirements for an offline-enabled Mobile Application integrated with a Local Server and MMU (Mobile Medical Unit) Application for beneficiary registration, clinical processing, and synchronization with a Central Server.

The system enables:

• Offline beneficiary registration
• Clinical and counselling data capture
• Local data synchronization via MMU
• End-of-day sync with central server

Refined Functional Statements

1. The Mobile Application shall function completely in offline mode without dependency on internet connectivity.
2. The Mobile Application shall support the following user roles:
   • Register User
   • Nurse User
   • Counsellor User
3. The Register User shall register beneficiaries by capturing demographic details along with village information.
4. The Mobile Application shall synchronize all beneficiary registration details to the nearby Local Server.
5. The Local Server shall host the Mobile Medical Unit (MMU) Offline Application.
6. The MMU Offline Application shall support secure user login functionality.
7. Upon receiving beneficiary registration details from the Mobile Application, the MMU Offline Application shall process the data locally.
8. The MMU Offline Application shall append additional operational parameters to the beneficiary records using MMU user login details, including:
   • VAN ID
   • Service Point ID
   • Parking Place
   • MMU User Details
   • Other operational parameters
9. The MMU Offline Application shall generate and return Beneficiary IDs to the Mobile Application as part of the synchronization response.
10. The system shall make beneficiary details along with Beneficiary IDs accessible to all three user roles:

• Register User
• Nurse User
• Counsellor User

1. The Nurse User shall capture clinical screening and other examination details for beneficiaries.
2. The Nurse module shall synchronize clinical screening and examination data to the Local Server using Beneficiary ID as the primary key.
3. The Counsellor User shall capture counselling details for beneficiaries.
4. The Counsellor module shall synchronize counselling data to the Local Server using Beneficiary ID as the primary key.
5. The Local Server shall store all beneficiary, clinical screening, and counselling data locally in offline mode.
6. The Local Server shall synchronize all offline data to the Central Server at the End of Day (EoD) whenever internet connectivity becomes available.