I
igarber
I'm planning to implement an appointment booking system for a small
medical office. Here's the plan:
The system will consist of 4-6 client PCs running WinXP and Outlook
2003. 2-4 PC will be used by the receptionists to book the appointments
for the 2 doctors working in this office. The system also includes
Windows Small Business Server, which in turn includes Exchange.
Both doctors will have thier own calendars, which will be shared. The
receptionists will open the shared calendars and book appointments for
the requested doctor. The doctors can then review the appointments on
their own workstations.
The actual appointments will be made by using custom forms that I will
create based on the standard appointment form. (Q1: Can Exchange server
store information gathered custom forms, or can I only use standard
"Appointment" form?)
Future implementation will also include doctors using Outlook Web to
view their schedules, as well as PDAs compatible with Outlook.
Does anyone see any problems with this approach? Someone recommended
that I use SharePoint Services instead of Outlook, but this approach
seems like overkill to me.
Any input appreciated!
medical office. Here's the plan:
The system will consist of 4-6 client PCs running WinXP and Outlook
2003. 2-4 PC will be used by the receptionists to book the appointments
for the 2 doctors working in this office. The system also includes
Windows Small Business Server, which in turn includes Exchange.
Both doctors will have thier own calendars, which will be shared. The
receptionists will open the shared calendars and book appointments for
the requested doctor. The doctors can then review the appointments on
their own workstations.
The actual appointments will be made by using custom forms that I will
create based on the standard appointment form. (Q1: Can Exchange server
store information gathered custom forms, or can I only use standard
"Appointment" form?)
Future implementation will also include doctors using Outlook Web to
view their schedules, as well as PDAs compatible with Outlook.
Does anyone see any problems with this approach? Someone recommended
that I use SharePoint Services instead of Outlook, but this approach
seems like overkill to me.
Any input appreciated!