Basically, unless you are working with an extremely small set of diseases and symptoms, what you will produce will be at best useless, and at worst positively dangerous. Prescribing drugs is regulated for good reasons: you can kill or permanently damage people if you get it wrong and you as the developer would be held responsible legally if that occurs.
From the fact that you ask this question, you are clearly a beginner: and this is not a project a beginner should get involved with. This requires a panel of expert diagnosticians and a top-of-the-line expert system, not a student developer with big ideas! A basic system will do more harm than good, and your use of "Victim" instead of "service user", "client", or "patient" is probably a lot more correct than you think ...
I'd find a simpler, safer project until you have good experience and solid backup behind you if I was you.
Having said that, if you want to proceed then first we have to get this sorted:
Quote:
Disclaimer of liability
The material and information contained in this post is for general information purposes only. You should not rely upon the material or information on the website as a basis for making any business, legal or any other decisions.
Whilst I endeavour to keep the information up to date and correct, Codeproject and I make no representations or warranties of any kind, express or implied about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services or related graphics contained on the website for any purpose. Any reliance you place on such material is therefore strictly at your own risk.
Copdeproject and I will not be liable for any false, inaccurate, inappropriate or incomplete information presented on the website, or for any loss or damage suffered as a result of the use of or access to, or inability to use or access this information whatsoever.
To the extent not prohibited by law, in no circumstances shall Codeproject or I be liable to you or any other third parties for any loss or damage (including, without limitation, damage for loss of business or loss of profits) arising directly or indirectly from your use of or inability to use, this site or any of the information contained in it.
These disclaimers and exclusions shall be governed by and construed in accordance with English law.
Liability is not limited by the above disclaimers in relation to death or personal injury arising from negligence on the part of Codeproject, OriginalGriff, or anyone using information given here.
If you are happy, then I'll give you an overview:
Treat it like any other project: Start with a requirements document which is basically your question, but with a lot more detail on how far the app is to go, what it covers, what you expect from it. This should also include the acceptance specification - what needs to be agreed in order that eth project will be deemed "completed" and ready for release.
Then use that to produce a specification: this adds details like how it appears to teh user, how he interacts with it, and what it displays. Add data storage and access methods, security requirements and recommendations (and there will be a pile of legal stuff you will have to adhere to with any medical related app as most countries apply a layer of law regarding medical data security).
That allows you to start the design document which describes in detail how the app will work: languages, technologies, classes: the nitty-gritty of the project.
Then the big one: Test specification. Details on how it's tested, what results are expected, how to determine them.
Then you can start coding.
Testing.
Debugging.
Go back to earlier stages at any point until the acceptance conditions are deemed "met" and the project can be released.
But me? I'd find something a load safer and do that instead...
Submit an article or tip