Blank fee sheet on openemr 5.0.0

thanks @Dave_S, @crlsgzmn have you cleared the cache and is your 5.0 install upgraded from 4.2?

Yes, I cleared the cache in both Firefox and Chrome. I did indeed upgrade from 4.2 to 5.0 then applied patch 1.

got it, thanks again, trying to check in with crisgzmn

Yes, I did erase the browsing data, and tried doing the same thing with windows.

As I said earlier, the issue presents itself only with new encounters, if I go to phpmyadmin and change the provider ID from 0 to 6, the Fee sheet will start opening again.

Regards,

The error happens when the logged in user is not authorized and there is no appointment You need to Change line 121 of feesheet.class.php to read like this

if (empty($this->provider_id)) $this->provider_id = $this->findProvider();

You also have an error in the statement print program that produces 2 statements each time when multiple DOS are there.

You cannot delete a patient.

Just a couple of more issues that you will run across

ok, thanks Terry

Hi @teryhill ,

Thanks! I just committed this fix since straightforward bug(missing $this-> in function call):

(btw, this fix will also be in the next 5.0.0 patch)

-brady

Awesome! that worked. Thank you very much.

where in phpmyadmin would you go to make this change?

it’s not the database, it’s in the code, click on the fee sheet bug link above to see the file that needs to be changed

OK, I’ll edit it in Textedit.

Thanks

Good morning,

Guys after changing that line, I don’t know if its related i’m getting an error that basically causes a segmentation fault in Apache2, and the openemr stops working as soon as you open the calendar screen.

Attached is my apache2 error log to see if it helps, that I know of nothing else was done to the system.

https://drive.google.com/open?id=0B_Qc48Wwm2_2S2E1TTd1dzlYZkU

Regards,

The error is apparently this one:

[Fri Apr 07 13:18:55.356442 2017] [:error] [pid 2324] [client 200.26.174.122:60265] PHP Fatal error: Maximum execution time of 60 seconds exceeded in /var/www/openemr/interface/main/calendar/modules/PostCalendar/pnuserapi.php on line 1394, referer: http://54.148.19.215/openemr/interface/main/main_info.php

The line that is reffering to is:

// we should bring the event up to date to make this a tad bit faster
    // any ideas on how to do that, exactly??? dateToDays probably.
    $nm = $esM; $ny = $esY; $nd = $esD;
    $occurance = Date_Calc::dateFormat($nd,$nm,$ny,'%Y-%m-%d');
    while($occurance < $start_date) {
      $occurance =& __increment($nd,$nm,$ny,$rfreq,$rtype);
      list($ny,$nm,$nd) = explode('-',$occurance);
    }
    while($occurance <= $stop) {
      if(isset($days[$occurance])) {
        // check for date exceptions before pushing the event into the days array -- JRM

The problem only happens when you try to open the calendar, if you don’t the EMR will work normally.

hi, i know that developer epsdky is a specialist with the calendar and has completed recent improvements in this area of the code, i’ve reached out to him for input

the above error isn’t in the log you uploaded (it’s an older copy of the log since most recent date is Fri Apr 07 12:41:59.196444 2017) but am seeing this error in the log
PHP Fatal error: Maximum execution time of 60 seconds exceeded in /var/www/openemr/library/encounter_events.inc.php on line 374, referer: http://54.148.19.215/openemr/interface/main/main_info.php

Ok.

Thanks for the clarifitation.

I’m also getting postnuke errors, and index errors.

Everything happened after trying to remove a in office schedule from the calendar…

you’re welcome, ok, was that a reccurring provider event?

Yes.

But I tried to delete just one event, for that specific day. My mistake was that I did not take an screenshot of the error, but there was something mysql related…

The only things i’ve modified in the code is the line to repair the fee sheet, and also an array to add another payer ID on the type of insurances, but apart from the normal calendar categories nothing else.

My system is a EC2 instance running ubuntu 14.04 with all the updates applied to it, with the /var/www directory mounted in a EFS (NFS) filesystem.

Adding a link to a screenshot with what’s happening.

https://drive.google.com/open?id=0B_Qc48Wwm2_2U0dPOXhSZUpjcHM

regards,