Product Incubator
The product incubator serves as a space to draft ideas for the further improvement of openIMIS. Anybody can come up with new ideas and jot them down on a wiki-page - over time these pages can involve into full development concepts that serve as a basis for feature development.
These are the existing incubator pages, some of them were prioritized by openIMIS Implementers: Incubator Prioritization . Feel free to copy an existing “Idea”-page (to have a valid page structure) and modify the content to your needs for your own ideas. Creating one page per idea will make it easier to manage the pages:
- Custom openIMIS Functionalities
- Incubator Prioritization
- Incubator: Integration of a Payment Layer
- Idea: Claims pre-authorisation
- Idea: Beneficiary self management portal
- Idea: Multi-programmes
- Idea: Separation of Target Groups (Multi-tenancy)
- Idea: Use of biometrics
- Idea: Anonymization function
- New feature requests prioritization
- Idea: Matching Provider ID with Patient ID
- Idea: Two-factor authentication
- Idea: Claim management variety
- Idea: Claim edit
- Idea: Claim dispute and appeals
- Idea: Service case for claims [Done]
- Idea: Linking claims referral cases
- Idea: Performance paid payments
- Idea: Case management module
- Idea Group: Linkage to Registries
- Idea: Integration with patient record systems
- Idea: Linkage to budget planning systems
- Idea: Integrated document management
- Idea: Voucher scheme management
- Idea: Mobile app for beneficiaries
- Idea: Mobile app to find nearest provider
- Idea: ID via mobile app
- Idea: Matching provider with patient ID
- Idea: Alternative identification mechanism
- Idea: Create inspection case
- Idea: Status check of inspection case
- Idea: Inspection case approval
- Idea: Informative Home Screen
- Idea: Snomed CT compliance
- Idea: Account lock
- Idea: Improve multilinguality in openIMIS
- Demo instances of integrated systems OpenMRS and Bahmni
- Idea: Schedule-tasks engine
- Idea: Server time to UTC
- Idea: Camera access from webapp
- Idea: FHIR: Search for patients
- Idea: super admin user
- Idea: OpenIMIS - current technology review and upgrade ideas
- Product determination stage
- Idea: Frontend migration to Vite
- Idea: AI Chatbot for knowledge management
- Idea: Patient OTP Verification in openIMIS Claims Workflow
- Idea: Claims Feedback & Beneficiary Engagement Integration
- Incubator: Integration of additional schemes
- Mobile Strategy
- Search and refresh strategies
- Nepali Requirements
- Database records versioning (history)
- Configurable Workflows
- Simplify openIMIS reference package
- Database migration to PostgreSQL (explorative pilot)
- SOSYS Nepal: openIMIS linkages with beneficiary management systems
- OpenIMIS structural limitations : New data structure required
- REST API migration to modular architecture
- Report Migration to Modular Architecture
- File Import Modules for the new Modular Architecure
- Workflow: Task based update of entities
- Incubator: Customisable Keywords
- Incubator: Synchronise Translations
- DHIS2-openIMIS Integration Production Ready Requirement
- Idea: integration with ILO Actuarial platform
- ADX support in DHIS2 ETL
- Offline usages
- File importer
- Improved Claims Review
- Notification to the users, insurees and Beneficiaries
- Error codes and messages
- Technical Specification Template
- OpenIMIS Dashboarding
- Search particular object in history
- Incubator: Automatic log out
- Incubator: deactivate users
- Claim failed submision
Uwe Wahser, since the 'Nepali Requirements' are also applicable to other contexts, should we remove that one layer, and tag the child pages under it with 'nepal' and 'new requirements'?