Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

 

 

Primary mentor

Unlicensed user

Backup mentor

Unlicensed user

Assigned to

Unlicensed user

Abstract

The Data Integrity Module allows users to run integrity checks against the database and identify problems for review. Each integrity check has several records with a status of New, Ignored or Voided. Users browse through the records, look up paper forms and verify the data. The only way to remove a record from the listing is to mark it as Ignored or re-run the integrity check after fixing the problem (at which point the record is voided because it is no longer an error). It's very hard to manage and fix large number of integrity checks with having thousands of record for each check.Data Integrity Workflow Module allow users to efficiently and collaboratively manage data integrity checks.This module enable manager to assign records in a particular integrity check to users(can be a analytic people) for analyse the issue with the record and fix it.

Objectives

  • Allow a manager to assign individual results or entire groups of results to another user for follow-up
    One of the major feature of this module is to assign  single or group of records of each integrity check to users(can be analytic people) for follow up and fix the errors in the records.Data Integrity Module not having a option to assign  records.Because of this only few privilege people can be access and fix the errors in each a integrity check by going through all the records.This is not feasible approach for OpenMRS instances which having large data capacities.There may be thousands of records results in a integrity check which having numerous errors.One of main objective of this module is to collaboratively solve the errors in a database by dividing task to responsible people.

  • Allow a user to log in and see just his or her assigned results
    After manager assign records to a users,it's required users to view their assigned checks for further investigation for fix errors.User will receive a table of assigned records.Through this web interface user will select preferred reports to work on.

  • Allow a record to move through workflow stages, such as In Progress, Waiting on Information, Verified, etc. (this workflow can be provided by implementer community members)
    Managers need to keep track of the stages of the records which are assigned to follow up users. User can be change the status of a record to a another stage to indicate the he/she progressing on that record.
  • Allow managers and follow up users to comment on records
    Sometimes managers or the follow up users required to comment the details about a particular record. Follow up users will have lot's of issues in the process of solving integrity problems in a database which are can be express through the comments.May be managers also want to highlight some description about a record through a comment.

  • Provide summaries for seeing workflow stages and progress over time.
    It's very useful to have summaries and reports about a record. These summaries and reports will include assigner changes,stage changes and other required details. 

Mid term evaluation video clip

               

Requirements

Initial version of the module will be compatible with OpenMRS 1.8.x

Use Cases

UI Mockups

  • Manager Views
  • Analytic user's view

E-R Diagram


Storyboard


Project Plan

Project Timeline

May 27-Jun17

  • Discuss about the final project deliverables with the mentors and update the project requirements documents according to it.
  • Improve the user interfaces for manager and user while researching about possible approaches.
  • Getting more familiar with hibernate and Spring framework.

Jun 17-Jun 25

  • Finalize the user interfaces in the project
  • Designing and creating necessary table schemas
  • Explore more about writing module in openMRS

Jun 25-Jul 29 

Implement the first phase of the project

Goal-Finishing manager view implementations

  • Creating the table structures through liquibase 
  • Creating backend services with use of the dependent data integrity module
  • Implement the manager view
  • Creating pages for view report summaries
  • Finalise the manager view implementations
  • Get a initial start of implementing user view
  • Partially implementing the user views

Jul 29 -Aug 2 

  • Mid evaluations 

Aug 2- Sep 9

Implement the second phase of the project

Goal-Finishing user view implementations and finalise the project

  • Polishing first phase implementations according to feedbacks
  • Implement the user view front end pages
  • Perform necessary changes at the backend
  • Finishing user view implementations
  • Writing test cases and test the project for verify its’ functionality
  • Creating wiki pages for the module

Sep9-Sep16

  • Extra week for finishing and wrap up project work

Sep16-Sep23 

  • Final evaluation

Extra Credit

Resources

https://github.com/openmrs/openmrs-module-dataintegrity

https://modules.openmrs.org/modules/view.jsp?module=dataintegrity

Data Integrity Module 

  • No labels