CDR Project QA Testing
From OpenEMR Project Wiki
Revision as of 00:51, 19 February 2011 by Bradymiller (talk | contribs) (→CDR Official Branch Commits)
CDR Project source locations
- Base Project (includes Project 2 and 3):
- Admin GUI (project 1 and Project 4)
- CQM/PQRI Reporting (Project 6)
- Merged branches --Tony - www.mi-squared.com 19:15, 18 February 2011 (UTC)
CDR QA Issues/Questions
Put your questions for clarification here.
CDR Bugs
Put any bugs you find here, there is a cut/paste simple "Bug Tracking" template here Bug Tracking Template
CDR Official Branch Commits
http://github.com/bradymiller/openemr/commits/rules_develop
(in order of first to last)
Interim development of a clinical decision making engine. Engine depends on rules, filters, targets, and actions. Basically, if a patient fits in the filter, and the target(s) is false, then the action(s) happens. The current scheme allows one filter and multiple targets and actions per rule, is very flexible, and supports internationalization. Engine is used for clinical decision support, clinical quality measures (CQM) and patient reminders. FUNCTIONALITY: 1) Clinical Decision Support widget can be found in the top right of the patient summary screen. 2) Clinical Reminder widget can be found in bottom left (above vitals widget) of the patient summary screen. 3) Clinical Reminder page can be found at Administration->Patient Reminders. The batch to send the messages can be run from this script by clicking the Send REminder Batch button. 4) CQM report can be found at Reports->Clinic->Quality Measures. TODO: 1. Finish rules for the 10 CQM rules (will require algorithm adjustments to deal with the encounter types and frequencies that are used in the CQM rules). 2. Ensure NIST is accomplished for CQM and clinical decision support. 3. Get the email and voice patient reminder mechanisms to work (may ask Visolve to help with testing the modified mavix//voice email scripts). 4. Ensure NIST is accomplished for the patient reminders. 5. Add a admin gui to allow per patient customization (note the mechanism to do this already exist, so just need a simple gui for it) 6. Add mechanism to allow multiple filters per rule. 7. Add a admin gui to allow rule modification and creation of new rules. 8. Add a mechanism for plans.
Added functionality to check the lists (which contains medications, allergies, diagnoses, surgeries, etc.), which means NIST functionality is almost done for clinical reminders and clinical decisions (just need to add a laboratory check). Also need to do more testing of this feature.
Placed a medication filter (coumadin) and a procedure checking target in the procedure tables (INR). Done getting procedures checking algorithm in, however still need to test/debug (currently passes all procedure targets, so a mild error somewhere to work out) Will convert the database to same mechanism as procedure checking since it's much cleaner. (collect another comparison parameter)
The procedure mechanism for filters and targets is now in place and working. To demonstrate NIST, put a medication filter (coumadin) that then checks for a procedure target (INR lab) with an interval of every 3 weeks.
Clarified database filters/targets algorithm and data objects.
Incorporated a basic appointment reminder mechanism within rules engine. To be useful will need some fine tuning, though.
Removed a debugging comment.
Added support for the Automatic Measure Calculation MU item.
Specifics:
1) Added support for the Automatic Measure Calculation MU item.
-Added pertinent columns to the clinical_rules table.
-Added mechanism to disallow patient specific customization
in clinical_rules.php since these are standard rules. Also
included the clinical quality measures in this mechanism.
-Added a selector for this in the interface/reports/cqm.php
report
2) Added some comments in sql/database.sql to clarify code.
3) Fixed some miscellaneous comment typos.
CDR module bug fix - user_settings label for patient_reminders_ps_expand fixed
Removed active column from clinical_rules table and:
1) Removed active column from clinical_rules table
and algorithm in clinical_rules.php
2) To resolve_rules_sql function in clinical_rules.php added
functionality to grab all per patient configurable
(ie. not cmq or amc) rules for the admin gui.
