PHP + MYSQL - Membership card tracking for our patients
This is a fairly straightforward application design.
It is not a complicated application and a skilled developer should be able to complete it within few days.
The application will have a multi-language interface.
Much like in OSCommerce, where every word is pulling from a 'dictionary' of variables, and then, based on
the language, the 'correct' language file is used.
You only need to be concerned with English.
However, this application will also address Right-To-Left languages, so provide an RTL variable.
I need a web application that does the following:
Step One: Initial Registration
Step Two: Fill Address Books
Step Three: Initiate an Order
Step Four: Finalize an Order and Pay
Step Five: Export New and Modified data to local database
Step Six: Print Order
Please note, this is a web application that is intended to run on a server.
However, at step Five it needs to export the changes to a local database (every modified record has a flag attribute).
It then needs to be loaded to a local database that Microsoft Word can connect to and be able to print locally.
The purpose is so that
Please do not suggest to use MS-ACCESS for the web server nor for the local application.
I explictly need it to run of MySQL.
Users register to the service and fill out their client's data (name, email etc) which is their unique data that doesn't change (like
Clients need to fill out 4 sections of data:
A. Residence Address
B. Shipping Address
C. Billing Address
D. Emergency Contact Info
The user has an interface that lets him see the differnt address books and copy records from one address book to the next.
Finally, the client can initiate an Order.
The client basically 'builds' his own Order using the information he has already provided.
Buy building an order, the Order itself is doing a Copy of the data from the previously created sections.
Order Table will have a full replica of all the fields in the various address books.
Yes,. it is redundent, it is duplicating the data, but that is how I want and need it.
Then, after the client has built the order, he can then add 'Items' to the order using the OrderDetails.
The items that the client adds are his prescription medication that he needs to take usually on daily basis.
Each medication will be an OrderDetailitem record. On the website it will be using a DropDownListBox to
select the information.
And finally, once an Order with the OrderDetails has been compiled it needs to be saved.
Saved,. is not the final process of the Order.
The user can modify the order later. He can log out, then Log back in and modify every detail in the order.
The client decides that he is ready to print the order.
He is presented with a Preview of the order and OrderDetails and being asked to approve and pay for the order.
He approves the order and then he makes a payment for the order.
Once the payment is approved, the order cannot be modified or changed. It is locked.
An Export process will create an SQL dump for New and Modified (flagged as modified) records.
It will also 'clean' the Web database from Credit Card information, so no credit card information is stored on the server.
That information will be stored only on the local database (using the SQL dump).
The 'cleaning' process will leave only the 4 last digits of the credit card number and all previous numbers will be replaced with '*'.
Step Six: - Bonus - separate pay!
Once we have the SQL dump, it needs to be loaded and do an OverWrite / Update of the local database.
The Order is being compiled to a word doc and then printed.
Considerations, Timelines, other:
This entire application is very simple and does not have extensive 'smart' logic to it.
It is primarily data-entry for the end user.
I would like to see nice GUI for the web app. It needs to have clear graphic design that has both Text and Images.
Navigation should be easy and simple.
I expect to see the completion of this application within 7-10 days.- At least the Web Portion with the Export option.
I will provide you with an MS-ACCESS database so that you can see the table structure, but it is just used instead of a CASE tool.
Do not design or plan anything that is MS-ACCESS related.
I pay 10% of the project in advance and remaining amount will be paid on a development phase basis.
Do not ask for 50% or any other amount in advance. I've been burned once and have no intention of repeating that again.
STEP SIX is a bonus:
In Step Five, you created an Export SQL dump. This project explains what will happen or how the SQL dump will be used.
Hoever, it is NOT part of this project, and separate budget will be made available for the Step Six phase, so you have a chance to earn more money from the continuation phase.
If you have any questions, please do not hesitate to ask in PM.
I'm compling with GAF rules of not providing any contact information outside of the GAF system.
Please do not try to bypass GAF. It doesn't look good when someone is trying to cheat the very system that tries to help them find a job.