Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
HCM v1.5 is a product release with upgrades for a new campaign adaptation such as IRS.
Enhancement of DIGIT HCM for managing a new campaign such as IRS.
Enhancement to provide the ability to link downloaded households to new campaigns.
The product has been enhanced to capture information related to house structure, room details, and the number of pregnant women and children present in the house independent of the campaign type.
Enhanced accuracy for geo coordinates capture in the app.
Enhancement of DSS dashboards for new campaign adaption.
Enhancement to provide the ability to view dashboards for District Supervisors in the mobile application.
Closed Household: This feature enables data collection on closed households by utilizing the existing registration and delivery package. It allows CDDs (Community Drug Distributors) to revisit households for registry updates efficiently.
Registration and Delivery: Added intermediate screens to enhance registration of households to support new campaigns.
User Action: Full CRUD functionality for project-related actions taken by the field worker that are not tasks related to the beneficiary like:
Refusal of consent for data collection.
Scanning of resources that will be reused for multiple deliveries.
Marking a transit post-non-compliant (polio).
Marking any incident that doesn't bear relation to the beneficiary.
Location capture of the field worker app.
Dashboard Updates:
Mobile Dashboard: Enabled the mobile dashboard for district supervisors and configured the Digit UI DSS Dashboard to support new campaigns (e.g. IRS).
National Dashboard Enhancements: Introduced support for pie charts and bar charts.
Map Configurations: Moved map configuration data to S3 assets.
Chart Configurations: Added and modified chart configurations for both the Mobile and DSS Dashboards (e.g., IRS), including both new and existing charts.
Tech Debts
Search Query Optimization: Enhanced search queries across the mobile application for improved performance.
Boundary Localizations: Migrated boundary localizations from the ISAR (JSON) database to an SQL database in the mobile application for better efficiency.
Pop-ups have been added to various screens to improve geo-coordinate accuracy within the app. These pop-ups will display a message and temporarily freeze the screen, allowing users to capture a person's geo-coordinates without disruption.
No breaking changes were made.
Configurable Project Dashboard: Previously, project dashboard configurations were hardcoded. Now, they are fully configurable based on boundary v2 and project-type codes.
Removal of Hardcoded Context Paths: All hardcoded context paths have been removed throughout the application, improving flexibility and maintainability.
Map Config Data Moved to S3: Due to the large size of the map configuration data, it could not be loaded into MDMS v2. This data has now been moved to S3 assets for better handling and storage.
Search Query Enhancement: Previously, each entity had its own individual search. Now, we have implemented a unified query builder, which has significantly improved the performance of the search functionality.
The HCM v1.5 release does not require any migration from the 1.4 release.
Find the service build updates below:
HCM v1.4 is a tech release with only server upgrade to with some additional cleanup.
Digit core LTS integration
MDMS v2 integration
Boundary V2 integration
HCM Admin Console
DIGIT HCM app modules as package extractions
Missing unique validation on client reference ID added in all offline supported services.
Project types have been moved to project additional details from MDMS.
UI modules extracted as packages
Registration and delivery
Referral reconciliation
Inventory management
Attendance management
DIGIT scanner
DIGIT showcase
All core services have been upgraded to core 2.9 LTS barring the services modified for offline use cases.
All data models have been restructured with an "is a relationship" from base eGov model and the base eGov search model.
All data models have been moved to the health common library and duplicates removed.
Removed reflection until code in the health common library that is Incompatible with Java 9 and above.
All the master data for the DIGIT HCM app are separated by functionality from one single master.
Flyway version upgrade to 9.22.3 for LTS upgrade.
Boundary v2 Integration
Category (Tag)
Services
Docker Artifact ID
Remarks
Facility
egovio/facility-db:v1.1.2-00a7accbda-14
Not Changed
Household
egovio/household-db:v1.1.4-a0e714254c-30
Changed
Individual
egovio/individual-db:v1.1.6-a0e714254c-12
Changed
Project
egovio/project-db:v1.1.5-a0e714254c-13
Changed
Product
egovio/product-db:v1.1.0-00a7accbda-31
Not Changed
Referral Management
egovio/referralmanagement-db:v1.0.3-a0e714254c-42
Changed
Stock
egovio/stock-db:v1.1.3-a0e714254c-31
Changed
Transformer
transformer:HDDF-1277-2f487e8dc5-256
Changed
HRMS
egovio/egov-hrms-db:v1.2.7-00a7accbda-19
Not Changed
Pgr
egovio/pgr-services-db:v1.1.7-00a7accbda-19
Not Changed
Service-request
egovio/service-request-db:v1.0.1-a0e714254c-18
Changed
Health-attendance
egovio/health-attendance-db:v1.0.2-30824c427-11
Not Changed
Digit-Ui
egovio/digit-ui:health-dashboard-digit-ui-d216162056-686
Changed
Health-UI
health-ui:health-dashboard-product-5bd3650bf2-691
Changed
Not Changed
Dashboard
egovio/dss-dashboard:v1.8.0-0d70d60e63-53
Unchanged
egovio/dashboard-analytics:master-impel-f705ac483a-48
Unchnaged
egovio/dashboard-ingest:v1.1.4-72f8a8f87b-10
Unchnaged
egovio/project-factory:v0.2.0-1ea8b5b5b9-9
Changed
egovio/workbench-ui:v0.2.0-6f08f64238-535
Changed
Checklist
Yes/No/Partially
Reference Link/ETA
Owner
Reviewer
Remarks
The development is complete for all the features that are part of the release.
Yes
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet.
Yes
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback.
Yes
12-June-24
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX.
Yes
30-May-24
Mail has been communicated to Andrew Jones for UI/UX audit
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA.
Yes
Lata
UI, and API technical documents are updated for the release along with the configuration documents.
Yes
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners.
Yes
Lata
The API backward compatibility testing is completed.
Yes
No breaking changes are made.
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication.
Yes
4-June 24
As part of admin console product owner sign-off has been completed
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable).
Yes
20-June-24
As part of admin console product owner sign-off has been completed
The GIT tags and releases are created for the code changes for the release.
Yes
Verify whether the release notes are updated.
Yes
Link
Verify whether all the UAT builds are updated along with the GIT tag details.
Yes
Link
Lata
Verify whether all MDMS, configurations, infra-ops configurations are updated.
Yes
Verify whether all docs will be published to http://health.digit.org by the Technical Writer as part of the release.
Partially
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead.
Yes
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any.
Yes
Link
Verify whether all the localisation data was added in UAT, and updated in the release kits.
Yes
No functional changes were made
Verify whether the product release notes and user guides are updated and published.
No
No product functional changes were made
The demo of the released features is done by the product team as part of a sprint/release showcase.
Yes
20-June-24
Demo has been give as a part of the HCM Console release
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover).
Yes
Architect sign-off and technical quality report.
Yes
Verify Bug Bash has been completed
Yes
31-May-24
Gate 2
21-Jun-24
The internal release communication along with all the release artefacts are shared by the engineering/ product teams.
Implemented validation for updating the project start date and the end date. Implementing this ensures that any changes made to these critical campaigns adhere to the predefined criteria.
Added the number of sessions field in additional details for the attendance registry, which enhances the system's ability to manage attendance tracking within projects. This field specifically denotes the frequency of attendance-taking sessions for a given project. Each session represents an instance where attendance is recorded, typically within a single day. For instance, if a project requires attendance twice daily (for example, morning and afternoon sessions), the number of sessions field would indicate ‘2’ to reflect this frequency. This information provides crucial context for understanding the attendance requirements and scheduling patterns within the project.
Added the ability to search by user UUID (Universally Unique Identifier) for individual search. This addition expands the search capabilities within the DIGIT-HCM platform, providing users with a more versatile and efficient means of locating specific individuals. A UUID is a unique identifier assigned to each user within the system. This new feature allows users to quickly retrieve information about a particular individual by entering their UUID into the search functionality. By leveraging UUIDs, which ensure each user has a distinct identifier, the search process becomes highly precise and reliable, minimising the risk of ambiguity or confusion, particularly in large datasets.
Health Facility Referral Feature Update
New Feature: HF Referral
DIGIT-HCM now includes a Health Facility Referral (HF Referral) functionality that enhances the platform’s capability to efficiently manage referrals across health facilities. This addition is aimed at improving coordination and communication, ensuring a smoother referral process.
Enhance the inventory flow with the sender ID and the receiver ID added. Including sender and receiver IDs offers flexibility in handling inventory transactions within the DIGIT-HCM platform. Transactions can involve movement between warehouses, from warehouse to staff, from staff to staff, or any combination thereof. This accommodates various scenarios, such as inter-departmental transfers, internal requisitions, or supplier deliveries.
Sender Identification: The sender ID specifies the entity initiating the inventory transaction. This could be a warehouse, indicating that inventory items are being dispatched from a specific storage location. Alternatively, it could represent an individual staff member responsible for authorising the transfer of inventory items.
Receiver Identification: The receiver ID denotes the entity or individual receiving the inventory items. Similar to the sender ID, this could represent either a warehouse where the items are being delivered or an individual staff member who is the designated recipient.
Implemented offline-enabled functionality in the Attendance Module. Implementing this functionality in the attendance module significantly enhances the usability and reliability of the DIGIT-HCM platform, especially in environments where internet connectivity may be intermittent or unavailable.
The HCM v1.4 release requires migration of the boundary and MDMS data if the server is not a fresh deployment but an existing v1.3 deployment
If the current environment has boundary data in MDMS v1 please follow the steps mention in the document below to migrate to boundary v2. Boundary migration from v1 to v2 LTS
If the environment is new the one click installer and data loader will by default load the data required.
If the Environment has pre existing data then the MDMS v2 migration tool should be run using the below document:
MDMS migration from v1 to V2 LTS
Following is the code link:
Category (Tag) | Services | Docker Artifact ID | Remarks |
Facility | egovio/facility-db:v1.1.2-00a7accbda-14 | Changed |
| Household | egovio/household-db:v1.1.3-00a7accbda-12 | Changed |
| Individual | egovio/individual-db:v1.1.5-00a7accbda-6 | Changed |
| Project | egovio/project-db:v1.1.4-00a7accbda-5 | Changed |
| Product | egovio/product-db:v1.1.0-00a7accbda-31 | Not Changed |
| Referral Management | egovio/referralmanagement-db:v1.0.2-00a7accbda-14 | Changed |
| Stock | egovio/stock-db:v1.1.3-00a7accbda-18 | Changed |
| Transformer | egovio/transformer:v1.1.2-00a7accbda-19 | Changed |
| HRMS | egovio/egov-hrms-db:v1.2.7-00a7accbda-19 | Changed |
Pgr | egovio/pgr-services-db:v1.1.7-00a7accbda-19 | Changed |
Service-request | egovio/service-request-db:v1.0.0-00a7accbda-16 | Changed |
Health-attendance | egovio/health-attendance-db:v1.0.2-30824c427-11 | Changed |
Digit-Ui | egovio/digit-ui:health-dashboard-product-3cb11409c9-636 |
Changed |
Dashboard | egovio/dss-dashboard:v1.8.0-0d70d60e63-53 | Unchanged |
egovio/dashboard-analytics:master-impel-f705ac483a-48 | Unchnaged |
egovio/dashboard-ingest:v1.1.4-72f8a8f87b-10 | Unchnaged |
egovio/project-factory:v0.1.0-6caaf2700e-6 | Changed |
egovio/workbench-ui:v0.1.0-6caaf2700e-16 | Changed |
Checklist | Yes/No/Partially | Reference Link/ETA | Owner | Reviewer | Remarks |
The development is complete for all the features that are part of the release. | Yes |
Test cases are documented by the QA team, reviewed by product owners, and test results are updated in the test cases sheet. | Yes |
The incremental demo of the features showcased during the sprint showcase and feedback is incorporated. If possible, list out the JIRA tickets for feedback. | Yes | 23-July-24 29-July-24 06-Aug-24 25-Sept-24 |
UI/UX audit review is completed along with feedback incorporation for any changes in UI/UX. | Yes | 23-July-24 |
QA sign-off is completed by the QA team and communicated to product owners. All the tickets’ QA sign-off status is updated in JIRA. | Yes | Lata |
UI, and API technical documents are updated for the release along with the configuration documents. | Yes |
UAT promotion and regression testing from the QA team is completed. The QA team has shared the UAT regression test cases with the product owners. | Yes | Lata |
The API backward compatibility testing is completed. | Yes | No breaking changes are made. |
The communication is shared with product owners for the completion of UAT promotion and regression by the QA team. The product owners have to give a product sign-off within one week of this communication. | Yes | 4-June 24 | As part of admin console product owner sign-off has been completed |
The UAT product sign-off communication is received from product owners along with the release notes and user guides (if applicable). | Yes | 20-June-24 | As part of admin console product owner sign-off has been completed |
The GIT tags and releases are created for the code changes for the release. | Yes |
Verify whether the release notes are updated. | Yes |
Verify whether all the UAT builds are updated along with the GIT tag details. | Yes | Lata |
Verify whether all MDMS, configurations, infra-ops configurations are updated. | Yes |
Partially |
Verify whether all test cases are up-to-date and updated along with the necessary permissions to view the test cases sheet. The test cases sheet is verified by the test lead. | Yes |
Verify whether the UAT credentials' sheet is updated with the details of new users and roles, if any. | Yes |
Verify whether all the localisation data was added in UAT, and updated in the release kits. | Yes | No functional changes were made |
Verify whether the product release notes and user guides are updated and published. | No | No product functional changes were made |
The demo of the released features is done by the product team as part of a sprint/release showcase. | No | Demo has been give as a part of the HCM Console release |
Technical and product workshops/demos are conducted by the engineering and product teams respectively to the implementation team (implementation handover). | Yes |
Architect sign-off and technical quality report. | Yes |
Verify Bug Bash has been completed | No |
Gate 2 | No |
The internal release communication along with all the release artefacts are shared by the engineering/ product teams. | Yes |
Health Campaign Management v1.3: The Frontline Worker’s App includes two new features that enable frontline teams to perform their tasks efficiently even when offline.
To learn more about the DIGIT Health Platform and the Health Campaign Management (HCM) product, click here.
The Health Campaign Management V1.0 frontline worker’s app includes four new modules with several features that allow frontline teams to perform their tasks efficiently even when offline. To learn more about the DIGIT Health Platform and the Health Campaign Management (HCM) product, please follow the
| Feature | Description |
|---|
Click to access the Jira dashboard.
Field 'type' does not exist or this field cannot be viewed by anonymous users.
The field 'assignee' does not exist or this field cannot be viewed by anonymous users.
A value with ID '10141' does not exist for the field 'project'.
Field 'labels' do not exist or this field cannot be viewed by anonymous users.
The field 'priority' does not exist or this field cannot be viewed by anonymous users.
Not able to sort using field 'priority'.
| Category (Tag) | Services | Docker Artifact ID | Remarks |
|---|
Mail has been communicated to for UI/UX audit
,
,
Verify whether all docs will be published to by the Technical Writer as part of the release.
Click to view the feedback from the UX audit.
Module
Functionality
Attendance Management
This is an offline-first module that allows supervisors who mark attendance for their teams to record their proof of work based on which the on-field workers will get paid.
The Attendance Module supports single-session and double-session attendance marking based on the cadence followed by the programme team.
Health Facility Referral
This is an offline-first feature that allows workers working at a given health facility (HF) who will be responsible for giving the diagnosis based on the type of symptoms they observe, then make a diagnosis, and provide the appropriate drugs.
This module provides the health facility workers with the capability to track referrals made by on-field health workers to different health facilities digitally via the Digit HCM app capturing all the cases of:
Beneficiary being referred
Referral details of the beneficiary
Reason for referrals and their diagnosis
Based on the diagnosis chosen, further details, if applicable
Module | Functionality |
Registration | Mobile app that enables the field teams to easily register eligible beneficiaries with built-in checks that enforce data collection protocols and validations to avoid data entry errors. The new features added are:
|
Service Delivery | Mobile app to enable the field teams to search for eligible beneficiaries and deliver the healthcare intervention with built in checks that enforce data collection protocols and validations to avoid data entry errors.
|
Inventory Management | Mobile app that enables the field staff to capture inflow and outflow of resources received from the warehouse or the supervisors.
|
Sync |
|
Registration | A mobile app that enables the field teams to easily register eligible beneficiaries with built-in checks that enforce data collection protocols and validations to avoid data entry errors. It facilitates the following:
|
Service Delivery | A mobile app to enable the field teams to search for eligible beneficiaries and deliver the healthcare intervention with built-in checks that enforce data collection protocols and validations to avoid data entry errors. It facilitates the following:
|
Inventory Management | A mobile app that enables warehouse managers to capture the inflow and outflow of resources from their warehouses to identify potential stockouts, wastage, and fraud, and take corrective action. It facilitates the following:
|
Supervision (Survey) | A mobile app that enables supervisors to to track the campaign staff's adherence to the campaign’s standard operating protocols, and record observations after the inspection. It facilitates the following:
- Yes/no type questions (Radio buttons). - Short answer questions (Text box). - Long answer questions (Text box). - Multiple response questions (Checkbox).
|
Core | Access control | egov-accesscontrol:v1.1.3-72f8a8f87b-24 | Not changed |
Encryption service | egov-enc-service-db:v1.1.2-72f8a8f87b-9 | Not changed |
File store | egovio/egov-filestore:v1.2.4-72f8a8f87b-10 | Not changed |
Localisation | egov-localization-db:v1.1.3-72f8a8f87b-6 | Not changed |
ID Gen | egov-idgen-db:v1.2.3-72f8a8f87b-7 | Not changed |
Indexer | egov-indexer-db:v1.1.7-f52184e6ba-25 | Not changed |
Location | egov-location-db:v1.1.5-f9271c8-7 | Not changed |
MDMS | egov-mdms-service:v1.3.2-72f8a8f87b-12 | Not changed |
Notification mail | egov-notification-mail:health-digit-master-6865af2823-2 | Not changed |
Notification SMS | egovio/egov-notification-sms:v1.1.3-48a03ad7bb-10 | Not changed |
OTP | egov-otp-db:v1.2.2-72f8a8f87b-12 | Not changed |
Persister | egov-persister:v1.1.5-3371bc2-5 | Not changed |
Searcher | egovio/egov-searcher:v1.1.5-72f8a8f87b-16 | Not changed |
URL shortening | egov-url-shortening-db:v1.1.2-1715164454-3 | Not changed |
User | egov-user-db:health-digit-dev-f2ddde9-32 | Not changed |
User OTP | egovio/user-otp:health-digit-master-6865af2823-3 | Not changed |
Workflow | egov-workflow-v2-db:v1.2.1-df98ec3c35-2 | Not changed |
Report | egovio/report:v1.3.4-96b24b0d72-16 | Not changed |
Document uploader | egov-document-uploader-db:v1.1.0-75d461a4d2-4 | Not changed |
Audit service | audit-service:audit-heatlh-40b1a4018a-1 | Not chnaged |
Error handler | error-handler:master-impel-dump-5022b7acff-1 |
dashboard-analytics | dashboard-analytics:master-impel-f705ac483a-48 |
dashboard-ingest | dashboard-ingest:v1.1.4-72f8a8f87b-10 |
Individual | egovio/individual:v1.1.3-69baa2050a-190 | Changed |
Household | egovio/household:v1.1.1-b78923bee4-103 | Not changed |
Facility | egovio/facility:v1.1.0-73167482a2-28 | Not changed |
Product | egovio/product:v1.1.0-73167482a2-12 | Not changed |
Project | egovio/project:v1.1.2-69baa2050a-199 | Changed |
Stock | egovio/stock:v1.1.2-69baa2050a-87 | Changed |
Referral management | egovio/referralmanagement:v1.0.1-69baa2050a-105 | Changed |
Service request | egovio/service-request:v1.0.0-a51bee1435-7 | Not changed |
Transformer | egovio/transformer:v1.1.0-73167482a2-38 | Not changed |
Complaints | pgr-services:v1.1.7-f58e5abb0d-8 | Not changed |
User management | egov-hrms:v1.2.6-ac8c591238-4 | Changed |
Attendance | attendance:v1.0.0-2c51c532-54 | Changed |
Feature | Service name | PR |
Attendance Session Configuration | Attendance | |
Role action Mapping Service register |
Feature | Service name | PR |
Health Facility Referral | referral | , |
Attendance |
Devops |
Health
MDMS
Config
Devops
Localisation