Hello everyone!
And welcome to this first post summarizing our last IASO’s Product Meeting.
News and Opportunities
- Two IASO demos will be presented at the Global Digital Health Forum next week in Nairobi. The use cases involve IASO for nutrition (a World Food Program use case) and IASO for campaign digitalization.
Features
-
UX/UI Improvements:
- form submissions (the web page for viewing submission details).
- reset password feature
- mobile application navigation to ensure a better user experience
-
Entity Duplicates Page Upgrade: It was reorganized by form type because most comparison data comes from the registration form (e.g., registering a new child under five). Now, when an analysis for entity duplicates is launched, it is reflected in the “tasks” section of IASO, providing details on success, failure, and reasons. The tasks screen also shows data imports from mobile, indicating if they failed.
-
Stock Management: A new menu entry for stock management has been added and will soon be part of a module that can be hidden for projects where it is not used.
-
Users can create Stock Keeping Units (SKUs) to track stock. An example use case is tracking the number of polio vaccine vials.
-
SKUs can be assigned to a project, an organization unit type (e.g., health facility level), and linked to a form (e.g., a form asking how many vials were used during the day).
-
Rules can be added to an SKU to perform actions like subtraction or a reset (to set a direct number) based on a field in the linked form. The rule can be published after setting it up.
-
The feature needs to be activated with a feature flag for mobile use.
-
In the mobile app, users can see the stock (e.g., initial stock minus used items equals current stock) and view the details of events and calculations.
-
The stock is tracked at all organizational unit levels (regions, areas, sites). The goal is to track everything, including transfers and inventory for resets.
-
Stock updates can be integrated with other forms, such as automatically reducing stock when a package of food is delivered to a beneficiary during the entity enrollment process.
-
-
Color-Coding: IASO has been updated with more color-coding.
-
Colors now appear in the dropdown menu for projects, helping with navigation.
-
Colors have also been added for teams as part of the UX refurbishing of the planning interface.
-
-
Planning Interface: The planning interface is evolving.
-
A new button to delete assignments is now available; previously, users had to click again to un-assign.
-
The configuration of the planning is being rethought, including dependencies like selecting a specific form linked to a project.
-
The base organization unit assignment will now link the planning to one organization unit type level, addressing issues where listing all organization unit types did not make sense.
-
A pipeline launch feature allows users to launch a pipeline (currently LQAS, but the idea is to support others) and specify parameters (e.g., assign 10 facilities per person per region). The first LQAS pipeline is working, connecting a pipeline from OpenHEXA to IASO to automatically handle signatures in the interface.
-
-
Forms Page Performance: The search button requirement on the forms page was introduced to improve performance by delaying the calculation of the “last submission” column. The page now loads much faster by removing this field by default. The “last submission” column is now an optional column under “select visible columns”.
Upcoming Features and Initiatives
- Data Validation and Cascade Validation: Mockups have been created for data validation and cascade validation (validation at different organization unit levels). The idea is to allow people to configure a validation workflow for a form, specifying the order (e.g., area, district, province). Users would be able to validate and see the current level of validation, with a history showing submissions, refusals with comments, and validations.