1. The various diseases and the families to which they belong are the essential concepts in this domain. The attributes and their values we distinguish can be found in attributes.txt. The relationships between diseases, ie. to what family (or subfamily) a disease belongs is described in opdracht2.pl with the family attribute.

2. The input of the diagonostic task will be all the possible attributes found in our database. Matched with the input attributes from the user. The input attribute/value of the user is then added to our secondary database to train our diagnostic task. The output of our diagnostic task consist the most likely diseases and which definately are not matched or excluded.

3. Match the input attributes with database value pairs.
   Check in database for crossreferencing.
   Build chance per matching output.
   Reference highest qualifiers back to their stored input values.
   Find best matching.
   Find non-matching.
   Based on input look for short term matching medicine, cross reference on
   output values.
   Based on later input look for long term matching medicine.

4. The knowledge is used as Expert, which can exclude or include possible diseases and prescribe medicines. Without consulting a doctor in foreign area's.

5. System starts with the historic quote:
EMH	"Please state the nature of the medical emergency;"
User	The user is now able to provide data and won't be interrupted until the system is extremely confident about the issue.
EMH	Elaborate phase, try to fill in empty spots. System asks for specific
	attribute value pairs. Fills it in with unknown or value.
EMH	Provides possible results and asks for vaccins in order to eliminate
	hot links.
	
	Until initial treathment fails, vaccins are considered working.


User	User fills in all data.
SYSTEM	System provides all possible diseases.  | Loop until match.
User	Eliminates diseases based on percentage.|

SYSTEM	System provides all possible medicine matches | Loop until match.
User	User eliminates medicines                     |