Because of the work that I am doing and it requires that the system is able to distiquish between multiple appointments in the same day. I found it necessary to add the encounter to the appointment calendar so that when I needed to pull the data in relationship to the appointment. I could get the right one even if there where 3 appointments cause each event would be tagged to an encounter.
It’s just couple lines of code and a slot in the table.
That seems reasonable. How/where would you populate the encounter ID? Can it be relied on to be set for all appointments with a matching encounter?
Also there are some places like the Appointments and Encounters report that match these up by date, and those should probably be changed to be aware of the new column. So more than a couple lines of code I think.
Concept of linking will be good in standard codebase. However rather than a column, an entry in gprelations will be one line code (gprelations.inc.php) and lot more flexible.
Note the patient tracker entry already has a place to map the encounter with the appointment. And a patient tracker entry is created for every appt. This is how the encounter is mapped to an appointment for when a patient is set as arrived etc:
As OEMR moves away from it’s first mission to service the solo practitionar, there are other fields that have multiple appointments for the same patient in the same day. So being able to corrilate data is becoming more an more of a challenge.
Thanks for the heads up on a better way to match the data.