The Dispedia architecture consists of a core ontology which stores data sets for the integration of information about patients and information for patients with rare diseases. The Dispedia schema (cf. figure 2) is dereferenceable under the domain The used ontologies are structured for the application or, respectively, the instantiation of the schema. As the view on patients and their description take place in a very heterogeneous manner, according to the involved actors (e.g., doctor, therapist, health insurance), the Dispedia schema provides an integration of individual descriptions. For the example of Amytrophe Lateralsclerose, this could be the ALS-Functional Rating Scale. The disease- specific collection of suggested solutions of a particular disease is used as an additional ontology. In the case of ALS, the expertise is found under the domain. This concept enables a logical extension of knowledge for the development of further disease-specific information pools, which then can be adequately found under the respective domains. Furthermore, the server architecture can be installed both web-based and as internal alternative.



Dispedia Core Files

The Dispedia schema contains the system classes of information flows meaning classes for the description of patients as well as classes for the description of indications. The Core Ontology and extended ontologies, which leave out established development areas, are part of the Dispedia schema. For the description of the patients’ state of health, different standardized classifications can be used for evaluation. The description schemata realized so far are integrated via the respective wrapper. Hence, the disCoreWrapperAlsfrs.xml, which is a part of the ontology integrating the classification according to ALFERS, and the disCoreWrapperIcf.xml integrating the classification according to ICF belong to the Dispedia schema as well. Standardized classifications for non-medical environment categories, e.g., housing properties, do not exist up to now. These categories are integrated via the file dispediaCoreConditions.xml. This vocabulary has to be perspectively extended and standardized.