Possible PHP project.

A

Anonymous

Guest
Hello all.

I am at a road block with a client. I am not sure where to go so I will just describe what I am trying to do and see if I can get some direction from the PHP/MySQL folks.

Our client a medical doctor is needing to be able to upload files such as pdfs and word documents to what I am assuming will be an ftp. The doctor is not computer savy so she will need to be able to log in and easily locate a certain patient.

The doctor is uploading files to specific users or patients. Patients will be able to either create an account or log in and few whatever files are present in their account.

The important thing to remember is that the doctor is not computer savy. Trying to make the upload process very simple.

Any ideas or thoughts are welcome.

Thank you.
:help:
 
My thoughts, this seems like a bad idea. There are a TON of laws (HIPAA) in regards to accessibility to patient files. A miss-click on the part of the not very computer savvy doctor could cause someone's patient information to be made available to others.
 
This is a private practice. There is no worry about HIPPA. This issue has already been discussed.


Any helpful ideas on how to accomplish this??? :help:
 
Well, how would you do it on a regular basis? Let's say, you have a website, with users, and they want to upload a file, a picture perhaps. You give them the option to upload, and when they do, you save it on the database for example, in a 'user_images' table. in that table you would have something like, imgid, userid, imgname, imgpath. Something like that, in order to be able to link each image with the correct user.

So, in basic, you would need a users(patients) table with patid username, firstname, lastname etc...
Then you can have a pdf_file table, with fileid, patid, filename, filepath and anything else relevant to that file and the user or patient.
 
I see....

I have only worked briefly with databases through school and it was only updating txt files from form fields. The user (patient) side makes sense and it was what I envisioned. The part that is tripping me up is from the Doctors angle. I suppose a form she can only access that would provide perhaps a drop down menu of all current users on the data base and then a browse... file area allowing her to upload to the database.

One other item I am trying to figure out is how would a new user or patient create an account. I am already working to figure out what vital information is used by the Doctor to identify certain patients. I am assuming your typical name, email, address, ss#.

Am I in the right direction?
:oops:
 
Yeaup. I remember, I had worked on a similar project for a doctors office before. It had so many tables, and so many fields. It was really tedious.

So creating a new user, I suggest that job should be done by the doctors secretary or someone who works in that office. It shouldn't be just anyone, give the users an initial password, which will require a password change when logging in for the first time.

For the patients fields, you're gonna need a lot more than email, ss, name. You will most likely need, height, weight, eye color, hair color, skin color maybe, medications, treatments, previous checkup date, next scheduled date, medical insurance plan, payments.. etc. I can keep on. You just need to know what does that doctor do with patients, and figure out that doctors needs.
 
I am going to have to dig up my php book from last term. We never did get into that much with tables. How many tables were you using for your particular setup?

Are there any good tutorials on setting up complex tables? I am looking through lynda.com and I am checking out joomla though I think joomla might be complicated for the secretary.

You are right about needing to use more vitals for the patient creation. Any more thoughts before I take the plunge?

I am curious as to why you had so many tables. Why did you have so many of them?


Your comments are very helpful!!! :)
 
You must log in or register to reply here.
Back
Top