I added a patient Problem List to the patient Summary Page. It located in the lower left pane. Two files changed (stats.php, stats_full.php), one added (problems.php) in the interface/patient_file/summary directory.
I have a client who wants encounters associated with problems. This makes a lot of sense to me; why have a list of problems where you cannot see which encounters were related to them, or vice versa?
OpenEMR stores the problems, medications and allergies in the "lists" table. It seems reasonable to also associate encounters with medications and allergies.
So what I’m thinking is to create a new table that cross-references the form_encounter table (or possibly the forms table) with the lists table. In this way each problem/medication/allergy could be linked with any number of encounters, and each encounter with any number of problems (or medications or allergies).
This new table (let’s call it encounter_problems) might have the following attributes:
* problem_id: id from the lists table
* encounter_id: id from the form_encounters table
* status: one of "first occurrence", "new occurrence of old problem", or "end of problem".
Then, we can implement a new document (HTML page, which might be a pop-up window) that lets you see all problems associated with an encounter, or all encounters associated with a problem, or enter a new problem, or perform other related actions.
I am working in ‘permanent forms’
these are meant to remain and being shown from the summary.
Including things such as vaccinations, problem list and sort of quick panel where the physician can see when was the last (and previous) pap, lab, etc,
We can work on some standard subroutine which when added to the regular form save process can store some information in the permanent forms.
The problems list was orginally meant to list a patients ongoing problems (high blood pressue, diabetic, arthritis…) in order to get a quick at a glance general health of the patient. That’s why it is on the summary page.
Your ideas are good though. I guess hearing from other practioners would be helpful to make sure the new functionality is useful. Though it sounds good to me.