Hi,
I want to ask your opinion about the way to work internally a software that i'm developing as end of degree project.
The thing is that, in essence i want to develope a desktop aplicaction for medical issues, that, basically and in a very reduced mode is a program to make diagnostics. The user introduce some parameters (symtomps, clinic signs, laboratory test, etc) and the program will make a posible diagnostic from the parameters.
The main idea was store all the data in a BD (embedded probably), and with SQL consults obtain the posible options, but my project director consider this "poor computing" and recommend me to search alternatives to give to the program more power (in computing terms).
The first option that comment me was to use ontologys, in order to create (or search if exists.. (*)) a medical ontology, where will introduce the inference rules needed for every disease, in order to make the posible diagnostic(s) from the given data (symtomps, etc.).
The problem is that with these subjects i'm very lost, i can't understand very well the concept and working of ontologys and i'm not sure if use this in my software is the best way to solve my problem.
(*): Exists medical ontolgys like:
diseaseontology in sourceforge dot net
But i think that is not exactly that i'm looking for.
Apart from the existence of this ontology, and to finish, i want your opinion about how to cover the project, how do you think ghat is the best option: Use a relational BD and complete the software with other things to give it more power (in computing terms)? Continue with ontologys? Other options?
Very thanks and sorry for my english.


LinkBack URL
About LinkBacks




Reply With Quote




Bookmarks
Algorithms and Data Structures
Java tutorials
Algorithms Forum