Abstract
A primary function of a health record system is to schedule medical appointments. In addition, a scheduling system should also act as a clinical decision control, automating scheduling tasks according to pre-set rules. Additionally, it should use communication tools to notify and confirm appointments, as well as acting in conjunction with a dynamic workflow or “to do” list.
The calendar module in LibreHealthEHR (highly modified, but based on the PostNuke Calendar project), is nearly 15 years old. It is the central part of the whole application. It is in need of revision, as well as the associated SMARTY template engine.
Intended Users
Clinical and Administrative Staff, Patients
Hi,
I think the problem with the HTTPS error is
" There are issues with the site’s certificate chain (net::ERR_CERT_DATE_INVALID)."
can I help you fix this ?
I am Abdur Rehman Anwar, student of BS(CS) from Department of Computer Sciences, Bahria University, Islamabad Pakistan.
I have good command in PHP, JAVASCRIPT AND MYSQL. I want to work with this project as a Google Summer Code internee 2017.
Would you like to tell me that how do I start ?
Your proposal must contain a detailed plan of how you will complete the project, along with a timeline and milestones, e.g, features that MUST be completed in order for us to pass you. Otherwise, you get failed.
Also @abdurrahman there is no need to double-post.
That XAMPP package did not get updated to the last build, and the prepared version itself is already out of date due to deployment issues. If you use that XAMPP package, replace the htdocs/libreehr directory with a download or pull from the LibreHealthEHR repository.
Hi,
This is Anup Sunni Routray.
I have got the whole source code of Librehealth EHR in my system.
I followed all the steps and now everything is well set up in my pc.
I was getting Parse error: syntax error, unexpected ‘[’
wherever arrays were declared like$args= [“a”=>1, “b”=>2];I modified it to $args= array(“a”=>1, “b”=>2) ;
Now everything is fine.
Sorry for joining a little late.
I would like contribute to the code and work on this project. I am well acquainted with PHP/MySQL.
I have not uploaded a proposal yet (but I intend to). I would first like to start working and understanding the code. Hence I need some tips to get started.
OK,
First, I need to apologize for a bit of mis-management. Apparently the LibreHealthEHR application proposals will be limited to the priority consideration, which is this Scheduling Calendar refactoring. Requests have been made to review proposals ahead of time by several candidates. Please, I encourage you all to submit a proposal on this project specifically. Furthermore, I request that you post the link to your proposal drafts here, or, if you do not want your proposal to be public while it is a work in progress, send a personal message to one or more of the project managers listed at the top of this thread. Upon receipt of the link or message(if sent to me), I will begin providing reviews immediately.
For any of you that have put extensive work into another proposal:
-Please, do not throw it away. It is valuable to us, and it could be valuable to you. It could be the key project document for another sponsored event, or even directly sponsored by someone requiring the work to be done. You are all valuable players, and we would like you to continue with this project in the future. There will be plenty of opportunities to get large projects funded in the future.
-If, in your review of this project, you have determined that there are reasons why some other proposal should be considered as a prerequisite for the Calendar replacement, or that the scope of this proposal is too broad, please make the argument for this within your proposal text. At LibreHealth, we believe in goal-oriented approaches. We don't want you to simply hit each check-box on a work-list. We want you to question whether the line items are valid at all.
References to the legacy module: Means variables and table/fields with names like pn_ referring to the postnuke calendar. Also comments in code that supply references to it, as well as documentation for developers and users.
Yes, It is a good idea to start with, and recommend as a replacement some open-source (and light-weight if possible) scheduling feature that can be made to cover the current application’s uses. The quality and support of that project is important, but maintainability and applicability are the most important. Several open-source project starting points have been identified at this point, but I have not researched these myself.
Please post on the EHR github repository, and request to be added to the team via the GSOC Coordination issue.
