Simple Patient Recall reminders and reporting

jcahn2 wrote on Sunday, January 15, 2012:

Ahoy Craig,

Very nice so far. 

The ability to go directly from the message one is reading to the patient chart in one click is an imperative!  I’m not sure if that is what you mean by “link to patient”.  That click should not bring up the “patient select” screen - it needs to go directly to the patient dashboard.

It would be nice to have the option to mark a message “save” and have the message list accessible from the patient dashboard.  One could also choose “delete” in which case it would be hidden from that listing and only available through audit. 

The user signing off the message or returning or rerouting the message is automatically logged (timestamp would be nice) and displayed with the message.  This would ale apply to a forwarded message.

We should be able to send a message from the patient dashboard or inside the encounter that defaults to the current patient, but would also allow override with the patient select.  Is this what you meant by “link to patient”?  Should be able to set a priority with this message so that if needed it can be made an “instant message”  that is, if the recipient is logged in, the message would display on top of other pages or preferably produce a flashing icon on all pages indicating an urgent  message is pending action.

Thank you.  IMHO this is a very important upgrade in OpenEMR function.

Jack Cahn
OEMR.org Board

cbezuidenhout wrote on Sunday, January 15, 2012:

The ability to go directly from the message one is reading to the patient chart in one click is an imperative! I’m not sure if that is what you mean by “link to patient”. That click should not bring up the “patient select” screen - it needs to go directly to the patient dashboard.

  - done

It would be nice to have the option to mark a message “save” and have the message list accessible from the patient dashboard. One could also choose “delete” in which case it would be hidden from that listing and only available through audit.

  - at this stage We have only added it to the Calendar, but could be incorporated anywhere really. Clicking the “Set As Completed” button sets the Processed field in the database. We will be adding a “view audit” screen in due course (we want to get to user functionality working first.

The user signing off the message or returning or rerouting the message is automatically logged (timestamp would be nice) and displayed with the message. This would ale apply to a forwarded message.

  - datestamp is there, forwarding is a good call (will add that to the todo list

We should be able to send a message from the patient dashboard or inside the encounter that defaults to the current patient, but would also allow override with the patient select. Is this what you meant by “link to patient”?

- the autoset current patient is a good call, we will implement this ASAP (however it will still be called from within the calendar screen for now)

Should be able to set a priority with this message so that if needed it can be made an “instant message” that is, if the recipient is logged in, the message would display on top of other pages or preferably produce a flashing icon on all pages indicating an urgent message is pending action.

- another good idea. Will add that to the feature set (does the calendar auto refresh ? )

===========================================================================================

now I have a query for anyone who can help :

I have a dialog opening to add a message, now I need another dialogue to open from within this one.
I am using the dlgopen function.

here is the dialogue code so far  (in the Add Dated Message File) :

    <script type="text/javascript" src="<?php echo $GLOBALS['webroot'] ?>/library/js/jquery.js"></script>  
    <script type="text/javascript" src="<?php echo $GLOBALS['webroot'] ?>/library/js/jquery-calendar.js"></script>   
    <script type="text/javascript" src="<?php echo $GLOBALS['webroot'] ?>/library/dialog.js"></script>            
    <script language="JavaScript">   
      $(document).ready(function (){ 
        $('.CalendarMe').calendar({dateFormat: 'YMD-', minDate: new Date()});  
        $('#selectPatient').click(function(){ 
          dlgopen('find_patient_popup.php', '_drPatSel', 600, 400);
          //alert('This should invoke find_patient_popup.php, but it is not working yet'); 
        })                                                   
    })

this is not working, if I comment the dlgopen line and uncomment the alert, the alert works so the click is being detected.

I used basically the same code to get the Add Dated Message File to open and it works.

cbezuidenhout wrote on Sunday, January 15, 2012:

Simple Forwarding Function Added

jcahn2 wrote on Sunday, January 15, 2012:

One more thing while I’m sharing the wish list:

The  “To:” field and the drop down menu that follows seem to be redundant when there is only one recipient.  The user displayed in the drop down should be sufficient.  I am not seeing how to select more that one user to whom to forward a message and how that would be displayed.

Jack
OEMR.org Board

jcahn2 wrote on Monday, January 16, 2012:

Mea culpa,   I see the selection of multiple recipients.  I am not seeing the direct link to the patient dashboard.  Has the demo been updated?

Jack
OEMR.org Board

cbezuidenhout wrote on Monday, January 16, 2012:

The “To:” field and the drop down menu that follows seem to be redundant when there is only one recipient.

  • not sure what you mean here, could you elaborate

We have multiple recipients as a feature to be implemented, not working as yet
the patient link is working in the calendar page, if you click on the patient’s name it will open the patient summary screen.

TODAY (Mr. Demo Patient) test message

clicking on (Mr. Demo Patient) would take you to his dashboard.

now onto the “send message” window
I am having problems getting the patient select dialog to open see post 22

need some input here please.

cbezuidenhout wrote on Monday, January 16, 2012:

okay, it checks for active patient now

cbezuidenhout wrote on Monday, January 16, 2012:

added a button next to currently logged in user name, in main_title so that user can send messages from anywhere in OpenEMR

hamdpa wrote on Wednesday, December 10, 2014:

Hello everyone,
I wondered if anything ever came from this. Is there a recall function available?
Thank You,
Henry

fsgl wrote on Wednesday, December 10, 2014:

Hi Henry,

Terry Hill is working on this. When it’s available, I’ll try to remember to post here.

teryhill wrote on Wednesday, December 10, 2014:

I have gotten input from fsgl on this. But i am sure we are open to other ideas/requests. I have the files the Tony uploaded showing how to manage it using the patient demographics.

Thanks to all
Terry

mdsupport wrote on Wednesday, December 10, 2014:

We had similar requirement where planned actions during encounter were e.g. repeat the labs in 3 months and come in for a follow up. Our approach was to create entries in patient reminder table (same table used by rules) and let office workflow take over.

As Tony’s original post says, demographics is a quick fix. It is better to leverage flexibility and configuration control of the rules engine.

teryhill wrote on Thursday, December 11, 2014:

Willing to share code?

Terry

hamdpa wrote on Thursday, December 11, 2014:

Thanks to all. How is it that the need for recall best handled.
Thanks again.

mdsupport wrote on Thursday, December 11, 2014:

Basic approach is as if a complex rule created the reminder for the patient - except the ‘rule’ is a clinician who sets necessary columns based on few custom rows in various rules lists. A common plugin section to several LBF forms does the simple INSERT.

A shortcoming of our approach is since we do not have a standalone form, these special reminders get created only during encounters.

Let me know what you would like to be shared.

fsgl wrote on Thursday, December 11, 2014:

This is what I emailed to Terry:

It would be great to have a link in the Encounter Form to the Recall Module. Once at the Recall Module, the user should be able to schedule the recall in a certain number of months or years. A great feature would be an option for email or regular mail reminders.

Specifically an email address would pop up so that the user can copy & paste the address for use in an email client. I don’t think it’s safe to email directly from OpenEMR. A list of email addresses can be saved to a clipboard, OpenEMR is closed & then emails sent. Our older patients don’t have computers, so in the absence of an email address, an option to print up address labels for postcards would be great.

If you have special requests & ideas, this is the time to express them, Henry.

hamdpa wrote on Thursday, December 11, 2014:

Sounds great fsgl! I would only add that what the patient is being recalled for and for when (week, month year) should to be included in both the manual (post card), email system and patient portal. The type of exam that the patient is being recalled for would ideally come from the Encounter (categories menu). The date of last visit could be included as well, as this gives the patient (especially the older ones) a point of reference as to when they were last examined. This is the way we use to handle it with post cards.
Thank you

teryhill wrote on Sunday, December 14, 2014:

can I see your “common plugin”. How do you have it setup in the encounter? I was thinking that the addition of code to run a report based on a diagnosis code and the last seen date for that code. Giving a repository to load the diag codes and set the interval for the recall (kinda making it automatic). so if the user sets up diagnosis code XXX.XX for a “yearly” recall then run a daily cron job printing the report and if selected send e-mail or print letter and giving a report showing what happened. If this is doable. still need some more thinking.

Thanks

Terry

mdsupport wrote on Tuesday, December 16, 2014:

This post provides the link to LBF enhancement that was shared long time ago. It greatly simplified custom LBF interactions for us. Without this our raw add-on is not useful.

However, you can use the addon functionality in standard codebase to inject javascript that will do the same thing with a jsonp call though code will be unpleasant for anyone unfortunate enough to stumble upon.

bradymiller wrote on Tuesday, December 16, 2014:

To work towards this in the CDR engine, another option is leveraging the CDR engine with templates:
http://www.open-emr.org/wiki/index.php/Active_Projects#Add_mechanism_to_allow_patient_specific_rules_and_plans

-brady
OpenEMR