|
|
| (30 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ==MU Requirements==
| | #REDIRECT [[Clinical_Decision_Rules]] |
| 1. AM 35.01 The system shall provide the ability to update the clinical content or rules utilized to generate clinical decision support reminders and alerts. "Growth charts, CPT-4 codes, drug interactions would be an example. Any method of updating would be acceptable. Content could be third party or customer created."
| |
| | |
| 2. AM 23.09 The system shall provide the ability to automatically generate reminder letters for patients who are due or are overdue for disease management, preventive or wellness services. "The term 'automatically' means that the system is able to generate patient recalls for all due or overdue reminders for an individual patient based on the current date, regardless of whether a user initiates this action, or if the action is triggered by pre-set parameters in the system. An example would be generating a letter to all patients overdue for a screening mammography. It is acceptable if the output allows generation of letters, such as a mail merge file."
| |
| | |
| ==Proposed Solution==
| |
| | |
| 1. Create a health plan management system for adding health maintenance (preventive services), disease management, and wellness plans.
| |
| | |
| [[File:CDS_Admin_Plan1.png]]
| |
| | |
| [[File:CDS_User_Plan1.png]]
| |
|
| |
| 2. The provider can assign any health plan to any patient. Here are some of the pre-built health plans:
| |
| | |
| [[File:CDS_5.5_Pre-Built_Health_Plans.png]]
| |
|
| |
| 3. The provider can also do a group assignment by rule, e.g. all women between 30 and 50 years old.
| |
| | |
| [[File:CDS_5.1_Health_Plan.png]]
| |
| | |
| [[File:CDS_5.2_Health_Plan.png]]
| |
| | |
| 4. Create a rule-based patient alert system for #1. The alerts are for screen display.
| |
| | |
| [[File:CDS_5.4_System_Alert_Setup.png]]
| |
| | |
| [[File:CDS_Patient1.png]]
| |
| | |
| 5. Create a rule-based patient reminder system for #1. The reminders are sent to provider's Messages box, which are then route to the patients.
| |
| | |
| [[File:CDS_5.3_Patient_Reminder_Setup.png]]
| |
| | |
| 6. A patient reminder can be sent in three ways: phone call, email, and/or by letter.
| |
| | |
| 7. CKEditor or Word (MS/OpenOffice) will be integrated for managing the email and letter templates.
| |
| | |
| [[File:CDS_CKEditor.png]]
| |
| | |
| 8. The messages are archived and managed in the administration area, while the provider can delete them from his/her Messages box.
| |
| | |
| [[File:CDS_Messages1.png]]
| |
| | |
| [[File:CDS_Messages_Box.png]]
| |
| | |
| 9. The data collected from #1 and 2 can be used for patient tracking and reporting later.
| |
| | |
| 10. The patient alert and reminder systems can be integrated with e-prescribing/medication later.
| |
| | |
| 11. Integrate patient reminder with an optional VOIP service to do automated phone calls. This is done using an API. No development work is needed for VOIP.
| |
| | |
| ==Effected Code, Tables, etc==
| |
| | |
| ==Owner and Status==
| |
| Thomas Wong
| |
| | |
| | |
| ==Links==
| |
| * [[CCHIT_MU_2011_Project]]
| |
| * Top Diseases in US: http://www.chronicdiseaseimpact.com/
| |
| * Chronic Diseases: http://www.health.state.ny.us/diseases/chronic/
| |
| * Associated with Sourceforge forum thread: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/3494342
| |
