Basic PHP/SQL Symptom Diary Website (Patient Support Group)
$100-550 USD
货到付款
Users of the site suffer difficult-to-manage physical symptoms (pain), and the purpose of the website is to help them keep an online symptom diary to help them to determine what factors might be immediately triggering their symptoms (diet, weather, and other candidates are possible for different people). Users register, select what (binary) questions they will be asked to check off in their daily symptom diary. The website sends them a daily email containing a unique link. When they click the link, their browser will take them to the website, and without logging in, they will be asked to check off which of a list of both symptoms, and potential symptom triggers, that they have experienced during the previous 24 hours. All questions are binary yes-or-no questions asked through check-boxes. All the information provided by each user each day will be stored in the database. Whenever the user requests it, a script on the website will perform simple algebraic computations (fully specified by employer-provided pseudocode) using quantities retrievable from the database to summarize the rate at which symptoms are occurring, and to show how potential triggers may be associated with the later appearance of symptoms. Inserting the resulting values into an employer-provided text template, the website will create a report for the user. This will be displayed in the form of an html page displayed through the browser (and, if user requests it, a .pdf file that the user can download).
## Deliverables
**Structure of Website**. The home page will feature a .gif image provided by the employer, which will be the main visual aspect of the home page. Home page will display this graphic, a brief statement of what the site is about, and a login and returning users page, as well as tabs.
All pages on the website will utilize a CSS and will display the same set of tabs: Home, About, MySettings, MyReports, and Contact Information. About and Contact Information will display html code provided by employer. About will have 3 tabbed html subpages provided by employer (called Mission Statement, FAQ, and a third page, still to be named).
MySettings and MyReports will be accessible only to users who have logged in (they should either be absent, or displayed but grayed out, for others).
MySettings will display the user?€™s basic login information, and choices made by the user as to (a) whether the user should be receiving daily emails, (b) what time he should be contacted in a daily email and what his time zone is, and (c) how often he should be reminded when he has not done so. It also lists his choices about what questions the user is to be asked in the daily emails (with checkboxes checked off for all selected questions, and room for up to 8 user-created questions). At the bottom, there is a Submit button which allows user to enter new selections at any time.
MyReports contains buttons allowing the user to request four different types of displays or files: (1) Show symptoms on calendar (display standard month calendar of 3 months at a time, with any days for which the user has not reported information displayed in gray, days with symptoms in red, and days without symptoms in green. (2) Upload pdf file of the calendar information just described; (3) Summarize the relationship between symptom triggers (as mentioned above, pseudocode for the simple computations required here will be provided); (4) Upload pdf of the same results.
**Sequence of Operations for New Users**
When a new user signs up, he is led through a series of four pages (full mockups will be provided by employer) that ask him to (1) select which yes/no questions should be asked about the triggers; (2) allow user so specify the wording of up to 8 additional yes-or-no questions to be asked in the daily surveys; (3) select any questions to be asked about symptoms (from a list of about 8 provided by employer); and (4) set user options for email times and reminder frequency and launch the email process. (These settings are reflected in the pages displayed in MySettings, naturally.)
**Returning Users**
** **
Returning users who have previously registered can sign in, and possibly visit MySettings and MyReports pages. If a user has signed in, but has not launched the daily emailings, a message is displayed asking the user if he would like to launch the daily emailings now. If so, he is returned to the sequence described above.
Returning users can alter their settings at any time. Naturally, if they change the set of questions that they are asked, this may mean that in the database there may be, more or perhaps fewer bits of information stored for some days than for others. The statistical computations for which pseudocode will be provided (see above) will be robust to these kinds of variations, and it should not cause problems.
**Communications**
** **
After login, users are sent an email confirming their registration, and providing a link to return to the website. When a user launches the daily emailings, another confirmation email is sent to the user, with text reminding them of how the process will work, and providing a link to return to the site. There is also a standard Lost Password function: If a user has lost his password, he can provide his email and his password is emailed to him.
** **
**Admin and Testing Functions**
** **
To facilitate testing, when user Admin999 signs in, two additional tabs will be made visible, labeled **Testing** and **View Users**. The Testing page contains a switch to turn on Test Mode. In test mode, the cron job schedules outgoing emails to user Admin999 every 10 minutes, instead of every 24 hours. (Developer may have suggestions for other ways to facilitate testing, if this is not the best approach.) The View Users page displays a list of all users.
**Installation of Website on Server**
** **
Employer will be happy to do preliminary testing on the developer?€™s website, if requested, but the developer will install the completed website on a host selected by employer, and employer will have the chance to test it running on that server.
项目ID： #3926019
关于项目
有14名威客正在参与此工作的竞标，均价$417/小时
