regarding the placement of the link…My choice will be to place the link in left nav as “Patient flow board”. It should be separate entity rather than a sub menu. The patient flow board should be accessible to front office, physicians, nurses and doctors.
Regarding color coding -
Color coding is always very very helpful. rather than making color coding of alternate strips, can it be color coded according to the status? Suppose, Arrived has a green code and checked out red etc etc…May be arrived late can be made red too…
one more thing which is really essential…ability to click the patient names so that we can go to the demographics of the patients directly and introducing patient ID in the list. It will help because many might have similar names.
Can yo tell me what you were doing? What was the status of the patient you were changing? That error usually means that there was no record ID in the flow board file(IE the patient was never “Arrived” or “Arrived Late” in the calendar)
Hi Terry,
Got it…need to first change the status in the calendar to arrived or arrived late and then the pop up window will work. Its working now…thank you!
Something i have noted while reviewing this project is that the apptstatus is currently stored in openemr_postcalendar_events, which seems to be a huge bug in the case of recurring appointments. For example, won’t changing a status for one appt change them for all the recurring appts? If so, then sounds like it may make sense to store the current appt status in the newly created patient_tracker table that will be used for Terry’s feature and use this instead. Thoughts?
There is a yellow advisory that pops up offering 3 options when changing a recurrent event. Very hard for a user to miss. The buttons are clearer to understand than the sentence.
The project is evolving and changing. There are some really great Ideas being kicked around off forum. I am asking for more ideas. Arnab has it running and has made some suggestions (link to Demographics which is being worked on and color coding the status). What would you want to see in reports? How should it handle yesterdays data? I have got plenty to do but if I can put the “Hooks” in while it is growing it will be easier than trying to shoehorn it in later.
Regarding the recurring appointment bug, the issue is twofold:
On the Patient Summary screen, recurrent appointments are not shown (except for day of first recurrent appointment or when the appt status is modified, which creates another entry in openemr_postcalendar_events). Here is the query that pulls appointments in the Patient and as you see it has no special treatment for recurring appointments: openemr/demographics.php at master · openemr/openemr · GitHub
Note that the Patient Tracker feature is based of method 2 above, so is bringing in two appointments erroneously also:
To deal with this bug, will need a function (likely adjusting the fetchEvents or fetchAppointments function) that works and is used in both places in issue 1 and 2 above (suggest that whomever fixes this bug see how it is done in postcalendar module itself, since the calendar works just fine with these recurring appointments). Another developer has sent me an email whom is interested in attacking this bug. After the bug is fixed, could then plug the working function into Terry’s code (note there is no need to delay the Patient Tracker project for this fix).