were shown.
I recently did a file based appointment system using apache tomahawk / myfaces
as a frontend , but it only stored a list of providers , and the appointments for a provider
for a given day if there was one. there was no worries with object relational mapping,
as it used java's internal object serialization to do save and load, so it just saved
the AddressBook object which was the root object to all the appointments, and the
java system just traverses its contents and stores the associated objects.
BTW python does that too, but people want relational mapping I suppose for searchability
and explicit transaction safety. What was missing was scheduling of provider sessions,
recurring and unusual, and scheduling of holidays .
Tim Churches says that scheduling/appointments is such a rehashed wheel, that there
is bound to be some stock system people can use, ? any available for free and source code
available.
FYI, the mapping from the user concept of an appointment system to the basic computer
concepts of maps(aka dictionaries) and lists ( aka sequences ) is not hard .
e.g. There is : - a list of providers. For any given day and provider, there is a map of appointments
whose key is the appointment start time . To store the entire appointment system, you therefore
need a map keyed by day and provider , whose values are the map of appointments for
the particular day and provider. After that, you can just do straight forward manual
object relational mapping, if you want it stored in a sql relational database.
On Mon Oct 2 23:06 , Oliver Frank
Horst Herb wrote:
> I have posted draft "birds eye" specifications for the RoR Appointment system
> on Ozdocit:
> http://ozdocit.org/tiki-index.php?page=appointments+system
I can't see anything on that page, other than the WIKI menu at the left.
One thing that is causing us a problem with our Pracsoft appointment
system is that if a patient changes an existing future appointment to an
earlier date, and doesn't mention that they they already have the
original appointment on the later date, the appointment system does not
warn our receptionists about this. What happens then is that the
patient attends on the earlier date, and when the later date arrives we
are sitting wondering why they are not there.
What I would like to see is that every time that we make an appointment
for a patient, the system checks on whether they have another
appointment in the future, displays it in a pop up window and asks
whether we want to delete that other future appointment.
--
Oliver Frank, general practitioner
255 North East Road, Hampstead Gardens, South Australia 5086
Phone 08 8261 1355 Fax 08 8266 5149 Mobile 0407 181 683
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
_______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
