> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/ph-v1.7/design/architecture/field-app-architecture/ui-packages/registration-and-delivery-package.md). # Registration & Delivery Package This package provides a way to register a household and individual members and deliver the resources to the registered households. To learn more about Registration and Delivery, [click here.](https://health.digit.org/hcm-product-suite/health-products/frontline-workers-app/user-manual)\ \ Link to the pub package: {% embed url="" %} ## Role * DISTRIBUTOR ## **Features** * Register new households and individuals. * Search existing households and individuals. * Update details for existing households and individuals. * Record service delivery of healthcare interventions to households and individuals for a single round campaign. * Auto-calculation of resources to be delivered to a household or individuals based on the configured rule. ## Getting Started To use this package, add the following dependency to your pubspec.yaml file: ``` dependencies: registration_delivery: ^latest digit_scanner: ^latest ``` ## Integrating with the HCM Application: 1. To integrate this package with the HCM Application, run the main function located in `health-campaign-field-worker-app/tools/registration_delivery_imports.dart.` * This will automatically add the necessary imports, mapper initializers, route config, setting initial data, and repository initialization to the required files. 2. Make sure you are on the path `apps/health_campaign_field_worker_app` and run the command: ```dart dart run build_runner build --delete-conflicting-outputs ``` This adds a package route to the `main router.gr.dart` 3. Install the application and you should have Registration and Delivery integrated into your base app. By following these steps, you can successfully integrate and use the registration and delivery module within your application. {% hint style="info" %} The below step is required as per your use case {% endhint %} During boundary selection, if you need to downsync registration-delivery-related data, include the below code in the `project_beneficiaries_downsync` file: ```dart final LocalRepository householdLocalRepository; final LocalRepository householdMemberLocalRepository; final LocalRepository projectBeneficiaryLocalRepository; final LocalRepository taskLocalRepository; final LocalRepository sideEffectLocalRepository; final LocalRepository referralLocalRepository; ``` Next, find this method in the same file `networkManager.writeToEntityDb` and the below repositories: ```dart householdLocalRepository, householdMemberLocalRepository, projectBeneficiaryLocalRepository, taskLocalRepository, sideEffectLocalRepository, referralLocalRepository, ``` With the above changes, you will enable the down sync of registration and delivery data. #### **Registries -Update** When the user down sync's the data by passing project id and boundary code. Server will send responses which are created under that selected boundary. #### **Response Entities** * Household * Individual * House Member #### **Now what ?** **Case 1:** Need to update the Entities related to project specific data. **Case 2:** Create Project specific data - (Beneficiary - Mandatory. Task and other relative entities) #### **Introducing Filters** * Registered * Un registered * Closed #### **Combination of filters by search.** * **Proximity enabled** * **Search by name** To get the search response we create a query build which is as shown below. It's an example for an individual based project.
**Sequence diagram :**\ \
#### Fields Incorporated in Registration Flow. 1. GPS accuracy - Household Location screen 2. No. of Pregnant Women and No. of Childs- Member screen - Both these field values persist in Additional fields Object of HH Member entity 3. Added a new screen to capture the structure of household structure The structure data will be fetched from MDMS and rendered in card format and the selected value will be stored in Additional Details Object in Household Entity. #### Closed House Data Capture. It’s been built as a new module (pub package)- [**closed\_household**](/health/ph-v1.7/design/architecture/field-app-architecture/ui-packages/closed-household-package.md) and It will be a dependency of registration and delivery package. ### Unsuccessful delivery For HH based flow we have introduced a flow to capture the reason for unsuccessful delivery **Sequence diagram**

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.digit.org/health/ph-v1.7/design/architecture/field-app-architecture/ui-packages/registration-and-delivery-package.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.