Re: Is OpenGroupware the solution for me?

Adam Tauno Williams <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.discuss.general
Message-ID <[email protected]>
> development, but lately I am probably a bit rusty as a developer  
> since I am now an IT manager at the Geneva University Hospital.  

I know the feeling,  I used to program but now do mostly system
administration and integration.

> I need to find a solution to manage a shared calendar for a small  
> medical practice (my wife is a physician). There are 3 physicians,  
> and 2-3 nurses for treatments (oncology). I searched a lot of the web  
> but either found pure calendar solutions (such as meeting maker) of  
> full featured (more or less) CMS (Mambo, etc...) or groupware  
> (Zimbra). I don't like PhP. I like SIMPLE solutions. 

I guess it depends on how you define "SIMPLE",  I wouldn't call
OpenGroupware or any real groupware package SIMPLE.  It is pretty simple
to administer and use.

> My first real need is therefore for a calendar for each user (3  
> physicians and 3 beds). The possibility for the secretary to enter  
> patients appointments. Same for the users (sometimes the physician  
> will take an appointment sometimes it will be the secretary).

There is one calender in OGo,  appointments have participants and access
permissions (actually a nicer model then multiple calendars once you get
used to it).  You should be able to accomplish what you want.

> It must be possible to display the day with the appointments of the 3  
> physicians and maybe the 3 beds (ideally 6 columns).

Not certain what you mean.

> The physician must be able to find the next appointment scheduled for  
> a patient and well as the previous appointment and optionnaly enter  
> some comments.

Appointments have notes.  If the patients are entered into the system as
contacts they can be tied to appointments,  the contact view I think
shows the previous and upcoming 30(?) days.

> Since the practice is small, confidentiality is not the first concern.
> In a second stage, I will need to be able to upload patient into the  
> OpenGroupware database (or vice versa) from an invoicing program.  
> Also, maybe store documents on a per contact (patient) basis.

You can import delimited files.

> 1)
> How long (easy) is it to setup an OpenGroupware server on MacOSX?  
> (taking into account my profile)

No idea, we are a SuSe shop.

> 2)
> With the basic system (e.g. no customization except accounts  
> creation) is it possible to "start working" from a Web interface?

Yes.

> 3)
> Some classes make me think of WebObjects. Does that mean I could  
> customize some templates? Are there re-usable wo-components?

Templates can be modified.

> 4)
> I am not certain I understood what process exist: is it a  single  
> process  (unix process) handling everything or is it a kind of Apache  
> module?

The OGo daemon is accessed via an Apache module.

> 5)
> I understand I need to install PostgreSQL (recommended). It probably  
> means I can get to the data quite easily?

Yes.

> 6)
> I understand it is possible to use iCal to view the calendar, however  
> is it really necessary since the HTML version seems quite nice?

It isn't necessary.

> 7)
> Considering my previous questions and context, which version should I  
> start with? and how easy is it to upgrade? (for example if I start  
> with version 1, and then want to benefit or contribute to items in  
> 1.1, is it easy to upgrade)? Put differently, is it better in my  
> situation to start with the lastest stable build for MacOSX or go for  
> a previous final release?

If you want roles for appointment particpants which are quite usefule
you need to use 1.1.x, otherwise you can use 1.0.x.
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBEQ6LMLRePpNle04MRAnV+AJ9ebQ6xKt4Dr8iFVEtVB09bf8LPXQCeI3MI
3UYoSZqr5FUV49SNi+5J2JY=
=/O8r
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.