avniproject / avni-roadmap-not-used-anymore- Goto Github PK

For an implementer to understand how the product works and how it achieves what it does.

• Product architecture, design and overview documentation

Ability to use the web browser interface to define the implementation schema and forms.

The user interface will allow the creation and management of implementation schema consisting of - individual types, program types and encounter types. Similarly, the form designer will have the ability to define a mapping to the schema item, form elements (data type, range, validation, answers, sort order of answers), form element groups and calculated fields.

The user interface will also allow for management of rules logic - for skip logic, calculated fields, validation, program summary and encounter schedule. The rules API documentation.

The non-transactional data is the same across these environments.

• Translations upload/download via Admin interface
• Translations not requiring new app release
• Implementation specific translations
• A sophisticated TMS available for Avni clients to use (Lokalise)

• Individual dashboard improvements
• Sync improvements

Developer Documentation (Architecture, Concepts, How-to, API)

API

• Rule upload
• Program summary
• Entity decisions
• Form validation
• Calculated field
• Skip logic
• Visit/Encounter schedule

1. Skip logic
2. Calculated fields
3. Field level custom validation

Usecases :

1. Data Entry Operator
2. Data quality monitoring and correction by supervisors
3. Quick case view by supervisors, district collectors, etc.
4. Linking of case records from reports

Separate websites for project and service.
A decision on tech stack for the website.

This will be achieved by making MyDashboard configurable.

• Intuitive workflows
• Inline help
• Rule templates / Declarative rules
• Kickstarter modules
• Polished Documentation

Access control to various functions and schema items based on privileges provided by the administrator.

• Scheduled demos
• Reaching out aggressively/proactively to schedule demos.

What are the search keywords we want to be hit.

Data Collection; Fieldwork; Community Health; Health Worker; Primary Health; Frontline Work;

This will allow a user to create a package of all the changes made in one environment and apply it to another environment.

Background
While the first deployment of implementation could be done directly in the production, but when the system goes live, making changes to production can create major issues, hence there must be a way to do this activity and test and then deploy to production.

(this)

Features, Use cases, Usage Statistics, Demo, Getting Started, FAQ, About Us and 2 case studies.

Google Analytics.

...so that implementers can understand how the product is configured.

Types of implementers (Service, Hosting, Support)
List of implementers.
List of the implementations done.
Contact an implementer.
Register as an implementer.

Certain reports should be available out of the box to the users:

• implementation schema views
• Operational reports like due list, overdue visits, cancelled visits, etc.

Options

1. Contact Us
2. Feedback
3. Query
4. Need implementation services (display list of implementers to choose, multiple select).

• Does not crash the app if a rule fails
• Logs rule failures which implementers can see on metabase and get notifications.

Required for implementations which have a lot of users. Its difficult to get all the users to update the app to promote a fix, etc. For this its required to ship the code without having to update the app.

A narrowed down workflow for beneficiaries

• This will enable the clients to use other reporting solution like SPSS, Strata, etc at their end wherever capability is available. Most clients have this capability.
• Also Will help reduce work and issues related to reports for the existing implementation team.