New SQL database - looking for help/comments

[oTAL]

Hi! I'm starting a new database for a medical office (one doctor only) which I'm thinking of doing in PostgreSQL in a Suse 10 instalation. It's supposed to hold every client file and be used by totally non-tech ppl (like the receptionist). It must be pretty secure and very reliable. It must also be flexible in terms of backups, and software/hardware changes... This database will have to last at least 15 years, so it'll run through many computers and OSs.

I've just graduated, and I'm not a big Linux fan (hence SUSE), but I guess it's the best tool for the job.
I'm planing to learn as I go, but I'd prefer not to make any crude mistakes that would force me to loose many hours redoing work (it will happen but I'm trying to minimize the amount of times...).

So.. I learned how to work with PostgreSQL and PhpPgAdmin, and that's what I'm planning on using.

The computer to install the database on is an Athlon K7 1700+ on an MSI K7T266 Pro2-RU. Since it has Raid I'm thinking of setting up a mirror so I can avoid weekly backups and resort to biannual ones... anything that saves me work after the system is set up is a big plus.

I'd like to know your opinions on distro, postgres (instead of MySQL...), PhpPgAdmin, Raid, and everything else... only a first idea and I do appretiate comments with just "I used that before ant it's a good choice for begginers", but if you disagree with something, please fundament your comments. I REALLY appretiate feedback, as it may potencially save me tens of hours of work. It would be a disaster if, for example, I discovered that SUSE 10 runs to slowly on a 1700+....

I plan on later expanding the database and interface, so that clients can schedule appointments on-line (instead of the current phone method) and eventually allow clients to view test results and maybe more... but I'll start off simple...
I'm very open to sugestions and I trully appreciate comments from ppl in the know. Thanks in advance.

 

[Thyme]

I don't know of any problems with that configuration, but you'll need something else if you want non-tech people using it. PHP will work for that.

Also, you'll want to be careful doing things on-line with HIPAA.

 

[kamper]

Yeah, you haven't mentioned anything about user interface. You certainly don't want your users using a database administration tool for day to day stuff. As mentioned, php is handy if you're familiar with html because you'll never have to install client software which means that your server hardware/operating system could conceivably survive the 15 years (if isolated safely).

Just having a raid mirror in the server is not really a good enough reason to pull back to biannual backups. Theoretically the backup should be automated enough that it's not really a hassle for you anyway.

I like postgres personally and suse is probably about as good as anything else if you're familiar enough with it.

One other thought, are you sure it's the best idea to develop something by hand? It sounds like a bit of hassle and could be expensive. Have you looked for software packages from companies that can give you support?

 

[tfinch2]

Originally posted by: oTAL
Hi! I'm starting a new database for a medical office (one doctor only) which I'm thinking of doing in PostgreSQL in a Suse 10 instalation. It's supposed to hold every client file and be used by totally non-tech ppl (like the receptionist). It must be pretty secure and very reliable. It must also be flexible in terms of backups, and software/hardware changes... This database will have to last at least 15 years, so it'll run through many computers and OSs.

I've just graduated, and I'm not a big Linux fan (hence SUSE), but I guess it's the best tool for the job.
I'm planing to learn as I go, but I'd prefer not to make any crude mistakes that would force me to loose many hours redoing work (it will happen but I'm trying to minimize the amount of times...).

So.. I learned how to work with PostgreSQL and PhpPgAdmin, and that's what I'm planning on using.

The computer to install the database on is an Athlon K7 1700+ on an MSI K7T266 Pro2-RU. Since it has Raid I'm thinking of setting up a mirror so I can avoid weekly backups and resort to biannual ones... anything that saves me work after the system is set up is a big plus.

I'd like to know your opinions on distro, postgres (instead of MySQL...), PhpPgAdmin, Raid, and everything else... only a first idea and I do appretiate comments with just "I used that before ant it's a good choice for begginers", but if you disagree with something, please fundament your comments. I REALLY appretiate feedback, as it may potencially save me tens of hours of work. It would be a disaster if, for example, I discovered that SUSE 10 runs to slowly on a 1700+....

I plan on later expanding the database and interface, so that clients can schedule appointments on-line (instead of the current phone method) and eventually allow clients to view test results and maybe more... but I'll start off simple...
I'm very open to sugestions and I trully appreciate comments from ppl in the know. Thanks in advance.

You're kidding right?

 

[n0cmonkey]

RAID isn't a replacement for good backups.

Make sure your system is HIPAA compliant before putting it in place.

 

[tfinch2]

Originally posted by: n0cmonkey
Make sure your system is HIPAA compliant before putting it in place.

Tell that to a client I'm working on right now. They've been running for a good year or so with no regards to HIPAA, and now they are getting in trouble, so they hired me to fix it.

 

[cleverhandle]

As others have stated, a PHP-driven HTML front-end to a Postgres system would be a long-term, OS-indepedent solution to the problem. But honestly, you seem about an inch shy of totally clueless. You don't know Linux, you don't understand backups, you don't appear to be aware of HIPAA, and you don't appear to have any experience writing database frontends. There's nothing wrong with learning on the job, but there are limits beyond which you shouldn't go. Somebody trusts you enough to give you this job. Even if that person is a family member and not a full-paying regular client, you should respect them enough to tell them you're out of your league. Pick a few of the skills involved here and practice them at home for a while before you offer them to others. Please.

 

[oTAL]

I forgot to mention that I am going to use a PHP-driven HTML front-end to the system.
I've done 2 such databases w/ PHP interface before, but they had no use other than academic learning. I did a computer shop that worked pretty nicelly but did not accept online payments. I want to do a real thing now and trust me it will be pretty good when it's done... I'm just hoping I don't take me 6 months to do it, and that's why I'm asking for advice. Furthermore, the dbs I made were created on fully installed systems already in place at my university, so this time I have this new task, and that is my first concern.

Originally posted by: kamper
One other thought, are you sure it's the best idea to develop something by hand? It sounds like a bit of hassle and could be expensive. Have you looked for software packages from companies that can give you support?

What do you mean? Comercial database software? Those are very expensive for a small office and I want to make my own fully costumizable one... Or do you mean something else?

I don't live in the US, but even if I did, I'm under the impression HIPAA wouldn't cover this, since it is not to be used by the costumers. It is to be used by the emplyees and the doctor.

cleverhandle: I know linux, I just don't like it very much. I've worked with some distros and I can solve most simple problems that get in my way, and even some mildly complicated ones, even though I do that googling for info. I really do appretiate your advice and honnesty, but the reason for starting on a small thing is exactly the inexperience you mentioned. I'll make sure I don't screw up badly and I'll gain experience for more complicated stuff. If/when I eventually add some costumer services to the site, then I'll have to worry a lot more, and I will again start slowly, like scheduling appointments.
Right now, the office has everything in paper, the appointments are taken on a book and the only use for the computer is to register the insurance covered costumers (which are a minority where I live) to the insurance company website. Anyway, I REALLY appreciate your concern, and I'll make sure to drop some links to a temporary frontend of the site before deploying, so that any obvious screwup may be detected.
I trust myself enough to know I'll do a good job. I just don't trust them enough to do it without help and advice, either from friends or online.

I do appreciate further feedback, especially on good easy to use and easy to secure backup systems. I think that having to record a DVD every 3 times a week is not the kind of option I want, and that's why I considered RAID to keep my info safe. Of course that would only keep it safe from HD failure, which is what is is supposed to do. I somebody knows any good alternatives, then by all means give me the knowledge .

Thanks for all the feedback guys. Very helpfull thus far.