The Data Integrity module is used to find data quality violations in data entered in OpenMRS from different sources like the Web app or the Android Client and it is not always possible to validate data while taking input. It is often used for validations that cannot be done within the form capture tools.
The violations are checked across any OpenMRS objects visits, encounters, observations and patient attributes even across time. The violations are checked against the rule written in Java or Groovy. As the rules can be programmed, there is very little scope for inconsistency. Added rules can also be configured to run on scheduled time.
The current module based on code donated from a rewrite by ThoughtWorks for the Bahmni project. The long term plan is to support data quality improvement projects and best practices.
The project currently needs the following enhancements and improvements:
|Week 1||OpenMRS Data Integrity Module|
|Week 2||Issues, Markdown and OpenMRS|
|Week 3||OpenMRS Patient Dashboard & Improved Filtering|
|Week 4||Webpack, OpenMRS, and Redux|
|Week 5||FontAwesome, Datatables and OpenMRS|
|Week 6||Sass, Compass & OpenMRS|
|Week 7||Rolling out new version of Data Integrity Module|
|Week 8||API, Liquibase & OpenMRS|
|Week 9||Breadcrumbs, flow, and OpenMRS|
|Week 10||REST API, Data Integrity Module & OpenMRS|
|Week 11||WebServices, REST APIs & OpenMRS|
|Week 12||APIs, TDD & OpenMRS|