Flexible data model
- Flexible longitudinal data management
- Data types - Text, Single Select, Multi-Select, Number, Geolocation, Image, Video, Date, DateTime, Time, Duration
- Configurable multi-level location support (e.g. District, Block, Village)
- Multiple pages per form, and one or more questions per page
- Skip logic (Screenshot)
- Calculated form fields - e.g. estimated date of delivery based on last menstrual period date
- Help tips (Screenshot1, Screenshot2)
- Take a photo or video recording while collecting data
- Capture current geo-location
- Register individuals or other subject types (Screenshot)
- Enrol and exit individuals/subjects into programs
- Link individuals via relationships (mother, daughter, etc)
- Access entire record on device (Screenshot)
- Search Individuals or other Subject types (Screenshot)
- Algorithmic decision support - e.g. High risk pregnancy identification, referral conditions (Screenshot)
- Field level, form level validation
Form level validation
OpenCHS can trigger a validation that can use complete data set for the subject/individual and can validate the data. e.g.: validate that date of delivery being filled in the Delivery Form cannot be within 4 months from LMP date captured during ANC registration form.
On-field work management
- Automated scheduling of encounter
- Manage scheduled and overdue encounters and plan visits (Screenshot)
- Cancel a scheduled encounter
Each individual (and other subjects) are registered to a location (e.g. village). The user can be assigned a group of locations (e.g. villages) or a group of higher level locations (e.g. gram panchayats). This forms the catchment of the user and all the individuals (or subjects) in those locations will be present offline on their device.
Device data security and Login
- Data protected on the device by login (Screenshot)
- Change password and reset the password from the device (SMS and Email support)
- Powered by AWS Cognito
Reporting dashboard (using metabase)
- Table, Chart and Geographical
- Download data as Excel, CSV and JSON
- Drill down (one level)
- Email and Embed support
- Support for multiple languages. (Screenshot)
- Video library on device with telemetry for monitoring usage
- Multiple organisation support (live, training, test) with same implementation definition
While the platform supports multiple languages, and adding translations is simple, currently the platform has been translated in Hindi, Marathi and Gujarati.
About video library
Multiple videos can be added for your implementations. All the information about how many times and how long the video has been played can be tracked.
- Immunisation schedule management (up to 5 years) (Screenshot)
- Child growth charts (WHO) (Screenshot)
- Inbuilt health modules for RCH (ANM and ASHA)
Inbuilt health modules
There are certain health programs in India that have been standardised to great extent. Programmatic implementation of such programs doesn't vary by place too much. Hence with OpenCHS has health modules that capture the shared understanding of these health modules.
- Android version 4.1 and above
Roadmap (with rough timelines, 2019)
Product goals for year 2019
- OpenCHS is focused on the use case where the primary user is in the field provides services or collecting data. OpenCHS doesn't aim to be a platform for data management for users who are well connected to the Internet - this is well served space and there are platforms that do this already (Salesforce, Liferay, React Admin, Django) and some under works (Google App maker). But the programs that are field based, often have supplementary use cases like a call center user who calls the clients, on-behalf data entry users who fill in for busy users (e.g. doctors in PHC) or data entry to be done in bulk because it is too difficult to capture data when service is being provided (e.g. mass height/weight capturing activities. But these user/use-cases are as much part of their core program - which primarily field based.
- Standing up a new implementation and then running the program, requires a lot of specialised knowledge of OpenCHS. Hence these activities are dependent on availability of OpenCHS product team. In 2019, the goal is make the implementation easier via web interface and support self-serviceable by the using organisation themselves.
- Upto 2018, OpenCHS has followed the model which was centered around an individual (aka beneficiary, client) and all data is captured for it - enrolment, encounter, program encounter. In 2019 - we aim generalise Individual to Subject, allow multiple subject types and link subjects of different types to each other.
- Improving the existing features of the product based on user feedback.
- Link subjects of two different types (April)
- Ongoing improvements based on user feedback
- Self-management of users (March)
- Catchment and location hierarchy management (May)
- Data collection (May)
- Privilege based access to data (July)
- Manage forms (Month TBD)
- Get Individuals and other Subjects (September)
- We have put the dates in the road-map to the best of our knowledge today, which is fallible. As we learn more we could keep updating the roadmap.