bradymiller wrote on Thursday, January 28, 2010:
error criteria 4) above should read:
4) if the target names are found in different active health plans, simply use the most stringent/recent one
anonymous wrote on Thursday, January 28, 2010:
Hi Brady,
Years to Repeat is not the same as the age filter. You can have a health plan template for an age group, but for specific patients, you may only want to repeat it for a number of years.
To do what you say, we will need to convert the current layout from:
Action # 1: A1C Test #1
Start Date: 1/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 2: A1C Test #2
Start Date: 4/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 3: A1C Test #3
Start Date: 7/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 4: A1C Test #4
Start Date: 10/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
to
Action # 1: A1C Test
Frequency: 4 times a year
Date Override: O Yes O No
Target Date #1: 1/1/2010
Target Date #2: 4/1/2010
Target Date #3: 7/1/2010
Target Date #4: 10/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 2: Foot Exam
Frequency: 2 times a year
Date Override: O Yes O No
Target Date #1: 1/1/2010
Target Date #2: 7/1/2010
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
To me, the only real benefit is the automatic calculation of target dates. But we also need an override so that each of the dates can be changed manually. The plan layout would be by type of actions instead of in a chronological order, which I prefer.
bradymiller wrote on Thursday, January 28, 2010:
is something like this feasible?
Action # 1: A1C Test
Frequency: 4 times a year
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 2: Foot Exam
Frequency: 2 times a year
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action #3: Flu Shot
Frequency: Seasonal
Target Date: 10/15
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
Action # 3: Hep B shots
Frequency: Series
Target Date #1: 0 months
Target Date #2: 3 months
Target Date #3: 9 months
Reminder Timeframe: 4 weeks
Followup Timeframe: 4 weeks
-brady
bradymiller wrote on Thursday, January 28, 2010:
above would be the generic template.
Then in the patient specific target sql entries (created using above template); the physician could always change the date of the calculated next target. And when a target is hit, it reproduces a new target from the template rules.
-brady
blankev wrote on Thursday, January 28, 2010:
This on “above” on e-paper is a nice time frame. But medicine is a living (let’s hope for it) science, it’s existence depends on failures and glory.
So there has to be some kind of evaluation before you can implement action 1, 2, and 3. It is obvious that THE DOCTOR meets his/her patient and thinks “now it is time for a foot examination” (or a heath plan) or “Oh oh oh why did the client not listen when I said come back for lab control six month’s ago”.
So the starting point could be with action 3, and/or action 2, and/or action 1, and since all are interrelated there should be an option that all tests can be related, but are dependent of the start situation.
And during my writing of this reaction I realize that all actions should be standing on their own, since not all patients need the HEPB shots and some Diabetic Patients only need to be reminded once a year of the foot examination.
So, if feasible, it could lead to the following conclusion:
Some tests “have to be” done in a certain time frame and other tests “could be done” within a certain time frame, but could also be during any client doctor contact. The client gets advise from the doctor and both will be happy for the next period scheduled.
But at this point there comes the manual interference with the digital automatism. The doctor patient contacts are sometimes relevant and sometimes irrelevant with the schedule stipulated.
The only important part is that the patient and/or doctor is not alarmed with some kind of memory refreshment if the consultation in the schedule happened earlier or later than stipulated within the time frame.
Yes Brady might say, but lets get things in place for my template and Thomas e.a might say but this is what we are doing, ……… so leave my remarks for what they are, just some remarks.
**
No reply needed.**
Tnx for all your efforts to make OpenEMR a even better product.
_
Pimm_
drbowen wrote on Thursday, January 28, 2010:
I agree with Thomas. We are trying very strongly to avoid “feature creep”. We are sticking to “Meaningful Use” requirements first. Additional features can be done later in the year after MU is completed so keep a “requested features list.”
We’re heading for 3,000 downloads off of SourceForge for the month of January.
Sam Bowen, MD
http://openmedsoftware.org/
blankev wrote on Thursday, January 28, 2010:
Sam,
are these ALL downloads or just downloads of the very “old” version V3.1 ?
Or is everybody downloading V 3.2 as THE nearby workinghorse ;-))
Pimm
drbowen wrote on Thursday, January 28, 2010:
Since 3.2 has not been released yet these are all 3.10.
OpenEMR Current 3.1.0 - 6,399<br>
OpenEMR Windows XAMPP 3.1.0 - 3,737<br>
OpenEMR Virtual Appliance 3.1.0 - 1,241<br>
OpenEMR Ubuntu_debian 3.1.0 - 1,310<br>
3.10 has been downloaded a total of 12,687. 8,950 linux versions and 3,737 Windows versions.
Sam Bowen, MD
http://www.openmedsoftware.org/
anonymous wrote on Thursday, January 28, 2010:
Thanks everyone for your review and feedback. We know this feature can be enhanced, and it’s really just a matter of timing. So to clarify, I’m not objecting to Brady’s ideas but when to work on them. It’s a lot more work than what we have planned to do now.
Brady, the new layout that you proposed can be handled by using “separate” health plans. Try it out, and you will see that it does exactly what you want. In the future, we can build mini plans within the big plan. This would be good for those patients who have a lot of diseases and health maintenance issues.
I also agree that “Target Frequency” and “Target Date” are better wording and will change them now.
anonymous wrote on Thursday, January 28, 2010:
Anyone who wants Admin access to http://www.medbloom.com, please email me at thomaswong.usa@gmail.com. I will set it up for you.
bradymiller wrote on Thursday, January 28, 2010:
hey,
Here’s a listing of hits goals from google analytics for last month for the www.openmedsoftware.org site, which gives a good idea of downloads of all packages and demo use. Note it’s only counting downloads started from the site, and does not count downloads initiated from sourceforge (Sam’s stats above include those)
190 conversions, Goal 1: Original OpenEMR tar.gz Download
425 conversions, Goal 2: Original OpenEMR zip Download
603 conversions, Goal 3: Windows OpenEMR XAMPP Download
130 conversions, Goal 4: Ubuntu Package OpenEMR Download
82 conversions, Goal 5: OpenEMR Appliance Download
2 conversions, Goal 6: CVS OpenEMR tar.gz Download
22 conversions, Goal 7: CVS OpenEMR zip Download
7 conversions, Goal 8: CVS Ubuntu Package Download
17 conversions, Goal 9: CVS OpenEMR 3.2.x tar.gz Download
29 conversions, Goal 10: CVS OpenEMR 3.2.x zip Download
1,893 conversions, Goal 11: 3.1.0 OpenEMR Demo
269 conversions, Goal 12: CVS Devel Tip OpenEMR Demo
89 conversions, Goal 13: CVS 3.1.x OpenEMR Demo
224 conversions, Goal 14: CVS 3.2.x OpenEMR Demo
anonymous wrote on Saturday, January 30, 2010:
We have added “Print All” and “Export Data” to patient reminders in Administration. This is to address the printing/send letter requirement. Instead of trying to build a letter/postcard template, we opt to export the data into Excel CSV format. This option is allowed by the MU requirement.
The file can then be merged with Word letter/postcard template quite easily. None of our programmers uses OpenOffice. Can someone test out the exported file to see if it works with OpenOffice?
I will submit the files for review shortly.
bradymiller wrote on Saturday, January 30, 2010:
hey,
If you can, please base the patch and new files off the “sftip” branch that is in your cchit SVN. This will make it much easier and quicker to review/test/commit.
-brady
anonymous wrote on Saturday, January 30, 2010:
Yes, that’s the instruction from Tony, and we have already updated our files with the latest version.
We have also set up 3 instances in our team folder to manage multiple MUs.