I am new to OpenEMR. I am using REST API call to fetch data from OpenEMR system. I am able to login into OpenEMR through REST API call and also able to fetch existing User/Provider details. But when I am trying to fetch the Provider’s Appointment Schedule it returns null even after giving proper data inputs through POST.
When I debugged the code execution thoroughly I found that it throws an error and the execution is stopped.
In api/includes/pdflibrary/tcpdf.php file api/includes/pdflibrary/config/tcpdf_config.php file is required to be included but when I looked into the folder that file was missing in stead I found a file tcpdf_config_alt.php there. In the commented section of that file the file name is written as “File name : tcpdf_config.php” .
I renamed the file “tcpdf_config_alt.php” to “tcpdf_config.php” and this solved my problem.
Is it a bug? As neither I found anything mentioned anywhere regarding this non-availability of the file tcpdf_config.php nor about renaming the file “tcpdf_config_alt.php” to “tcpdf_config.php”. But as this file is so important for fetching the result I think it must be mentioned somewhere on how to use the file.
Hi,
I had posted a query in sourceforge on 17th Sep,2013 about a problem that I faced while working on REST API calls to OpenEMR. But didn’t got any responses … But I need to do some changes in the REST API section to make my project run. I am developing a widget which will fetch out the doctor’s appointment details from the OpenEMR system and display it in a calendar/scheduler. Patients can book their appointments through this calendar.
I have made two changes in REST API coding
I renamed the file “tcpdf_config_alt.php” to “tcpdf_config.php” at the location api/includes/pdflibrary/config/ (Reason: tcpdf.php file includes tcpdf_config.php but it exists in apache by “tcpdf_config_alt.php” name and hence throws an error)
Changed the sql through which the names of the facilities are fetched, added two extra fields (service_location and billing_location) to fetch along with existing fields (id, name). These two new fields are important because through them I can distinguish which one is a service location and which one is a billing location as patients will book the appointments at only service locations and not billing location.
Is anyone working on this issue ? Or can you suggest/guide me so that I can contribute my patch to incorporate these changes in the REST API
MedMasterPro is working/using this code whome don’t always see the forum posts. Send me an email to brady@sparmy.com and I’ll direct your email to them so you can directly communicate.