Demonstrations will be available to anyone wanting to present or discuss technologies or ideas in a more hands-on way. If there’s something you want to show or demonstrate to the entire OpenMRS Community, now is your chance! You’ll have your own station to present and discuss your topics as well as share the challenges you’ve experienced in deploying or implementing your work. If you’re interested in giving a demonstration, please submit your proposed demonstration below!
Please include a title and a short description . Putting “####” in front of your title will highlight it in your post.
Please limit replies only to proposed demonstrations (not side discussion) – i.e., if you want to discuss any entry below or this topic in general, click on the timestamp for the post (on the top right edge of it) and then click the “+ New Topic” link to create a linked topic.
If you want to see it… vote for it! If someone has suggested a demonstration you would like to see “like” the post by clicking its heart icon.
We are currently building features on the RefApp for Maternal Child Health – htmlforms, vaccinations widget, clinician-facing dashboards, and using “off-the-shelf” pieces (Relationships, Programs, etc). Would love feedback and see what others have done for this clinical care area.
Openmrs has been a hurdle for writing reports and doing analytics over the database because of its highly normalised and hierarchical data model.
To address this problem we have built Bahmni mart which can create a flattened data model out of Openmrs. Now this database can be plugged into any analytical tool or can be used for writing complex reports in an easy and simpler manner.
We would like to showcase our experience building mart database and the impact that it has created in writing reports and doing analytics.
Currently, the implementers create concept sets in openMRS for observations to be captured. Later they provide JSON configuration for these forms to define how different concepts and concepts behave in UI. Also currently users can write custom javascript functions to provide validations for certain fields on these observation forms.
Why?
Reduce the technical know-how dependency required for the implementers currently to configure forms in Bahmni (Implementation of Openmrs).
Remove the current dependency for every form or section within the form to be a concept set. Instead of allowing the implementers to design the UI elements separately without the need of having a concept set.
How?
Provide users with a user interface using which:
They shall define the forms and its UI elements.
The UI elements may be bound to the data source.
They shall be allowed to define validations on the UI elements. (Whereby eliminating the need for users to edit JSON configuration files and to provide custom javascript functions for validations)
Allow users to share the form definition across implementations thereby reducing the startup time for defining forms at each implementation site.
What?
The form builder shall allow users to,
Define new forms, edit existing forms or delete (retire) existing forms.
The user shall be able to drag and drop fields on the form as its UI elements.
The user shall/may bind each of this UI element to a data source which shall be a concept.
We have successfully integrated the use of Smart Cards for handling HIV testing and immunizations data in KenyaEMR. We would like to showcase the work we have done and the experience with Smart Card. We would also like to get your views/reactions to help improve the solution.
You are welcome
We’ll be demoing OpenSRP a mobile health platform that integrates with OpenMRS.
We will demonstrate our Child Immunization and Clinical ANC app. We are also in the process of developing OpenSRP modules to be used by CHWs for partners like UNICEF.