This webpage describes the design and development of the BRAINTEASER Ontology (BO) whose purpose is to jointly model both Amyotrophic Lateral Sclerosis (ALS) and Multiple Sclerosis (MS).
The BO serves multiple purposes:
The BO is innovative since it relies on very few seed concepts - Patient, Clinical Trial, Disease, Event - which allow us to jointly model ALS and MS and to grasp the time dimension entailed by the progression of such diseases.
Indeed, the core idea is that a Patient participates in a Clinical Trial, suffers from some Diseases, and undergoes Events. These Events are different in nature and cover a wide range of cases, e.g. Onset, Pregnancy, Symptom, Trauma, Diagnostic Procedure (like evoked potentials or ALS-FRS questionnaires) Therapeutic Procedure (like Mechanical Ventilation for ALS or Disease-Modifying Therapy for MS), Relapse, and more. Overall, this event-based approach allows us to model ALS and MS in an unified way, sharing concepts among these two diseases, and to track what happens during their progression. Details of the design and functioning of the BO are provided in the next sections of this deliverable.
The BO plays an important role in the overall BRAINTEASER architecture, shown in Figure 1. Indeed, it informs the implementation of the BRAINTEASER Semantic Data Cloud since the data contained here will be represented according to the BO, i.e., they will be an instance of the BO.
In Figure 1 it is possible to see that all the data will be anonymized prior to being represented in the BO. This holds true for both the retrospective data, i.e., the data already held by clinical partners on the right of the figure, and the prospective data, i.e., the new data that will be collected during the project lifetime on the left.
The data held in the BRAINTEASER Semantic Data Cloud, exported in a suitable format, will then be used to train the AI models needed to predict the progression of both ALS and MS.
Finally, a subset of the data in the BRAINTEASER Semantic Data Cloud will be exported to the European Open Science Cloud (EOSC) and they will be also shared and exploited for the Open Evaluation Challenges.
Figure 2 shows an overall picture of the whole data flow associated with the BO and the BRAINTEASER Semantic Data Cloud, also in relation to Open Evaluation Challenges and the EOSC.
In summary, the BO ontology will model the following data sources:
The BO will also allow to link these data with other resources available in the Linked Open Data Cloud.
The remainder of this Section describes the background that underlies the Brainteaser ontology. Subsection 2.1 Describes the role of the ontologies, how they work and why they are so important especially in the medical domain. Subsection 2.2 Concerns RDF, the approaches actually used to define an ontology, and the serialization process. Subsections 2.3 and 2.4, on the other hand, details on the current state-of-the-art and related works. In particular, subsection 2.3 details which other efforts have been made to model the Multiple Sclerosis and the Amyotrophic Lateral Sclerosis. Furthermore, it will describe how the proposed ontology is capable of overcoming current limitations. Finally, section 2.4 contains a brief description of the main ontologies that have been exploited to build the Brainteaser ontology which grant to our ontology the required interoperability.
The Semantic Web is an extension of the World Wide Web based on standards set by the W3C [FHH+07]. At its basis, the Semantic Web is a form of network of interconnected data exploiting the Web. In particular, it provides a common framework that allows data to be shared and reused across applications, enterprises, and community boundaries.
While the original Web is mainly focused on the interchange of documents connected among them by link deprived of semantic, the aim of the Semantic Web is twofold: to go beyond the simple publication of documents by adding semantic to the links connecting them; and enabling computers to perform more useful tasks and support trusted interactions on the network [PMZ10]. In 2006 Tim Berners Lee coined the term Linked Data to indicate structured data interlinked with other data to become more useful through the use of query that exploit this presence of semantic on the edges [HB11]. Linked Data is based on a set of rules, outlined by Berners-Lee [BHBL11]:
In this context, the world “ontology” has become extremely popular since the mid nineties as a construct containing information and definitions about concepts and the relationships among them [IB14]. In particular, in the domain of medicine, different resources are used alongside ontologies. These are controlled vocabularies, taxonomies, and thesauri [IB14].
A controlled vocabulary is a closed list of named subjects, which can be used for classifications. The constituents are called terms, i.e., names assigned to certain concepts. A taxonomy is an abstract structure that presents subject-based classifications that arrange terms from a controlled vocabulary into a hierarchy. The term thesaurus may refer to various subject classification structures that extend taxonomies allowing other statements about the subjects in the hierarchy. An example is the addition of associative relationships to the parent-child one.
Ontologies, more specifically, are computer science constructs [Kon15] that provide well-defined vocabularies which, in turn, allow precise and machine-readable description of knowledge about a certain domain [CJB99]. In computer science, one of the first definitions of ontology that we found is that of an “explicit, formal specification of a shared conceptualization” [Gru95].
Independently from the formal definition of the term, there are today many artifacts called ontology that provide a series of main features, used in almost all the applications based on them [HSG15]. These are:
In the last decade they have been pervading almost all research domains [IB14], and, in particular, the biological and biomedical ones [HSG15], where multiple examples confirm their success [Kon15]. Ontologies are today often written using the Web Ontology Language (OWL) [GHM+08], a family of knowledge representation languages for authoring ontologies characterized by formal semantics and built upon the W3C Resource Description Framework (RDF) standard.
RDF is a family of specifications for the publication of information on the Web endorsed by the W3C Consortium. In recent years, it has become the de-facto standard for the publication, access and sharing of data on the Web, since it allows for the flexible manipulation, enrichment, discovery and reuse of data across applications, enterprises, and communities [SMS+17].
In RDF, a resource is represented by an IRI, a Literal value or a blank node. An IRI (Internationalized Resource Identifier) is an extension of the URI (Uniform Resource Identifier) that can also contain UNICODE characters. A literal is a string representation of a certain value such as a string, a number or a date. It may be labeled with information such as the language or the datatype of the represented value. A blank node is a URI-like string which has validity only inside the considered database [PAG09].
One RDF statement is a triple composed of a subject, a predicate and an object. Subject and predicate are IRIs, while objects can also be literals. A literal, in particular, can only be an object. A blank node can either be a subject or an object. The combination of triples, where the object of a triple becomes the subject of another triple generates a directed graph, called RDF Graph.
OWL 2 is an ontology language for the Semantic Web with formally defined meaning. It is an extension and revision of the first OWL language, and it was published by the W3C Ontology Working Group in 2004. OWL 2 ontologies provide classes, properties, individuals, and data values stored in Semantic Web documents. It is intended to represent rich and complex knowledge about things, groups of things, and relations among them. Being a computational logic-based language, the knowledge expressed in OWL can be reasoned with by computer programs either to verify the consistency of that knowledge, or to make implicit knowledge explicit through inference. OWL documents, often referred simply as ontologies, can be published in the World Wide Web, and may refer to or be referred from other OWL ontologies. OWL is part of the W3C’s Semantic Web technology stack, which also includes RDF and SPARQL [HKP+09].
Today several serialization formats are available for RDF data. Among these, some of the most famous are N-Triples, Turtle, RDF/XML, and JSON-LD. We briefly describe each of these and report a small example describing the same concept “head” (uberon:000033
) with a label, a comment, the specification of being an owl class and sub class of “Anatomical Structure” (uberon:000061
).
<http://purl.obolibrary.org/obo/UBERON_0000033> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Class> .
<http://purl.obolibrary.org/obo/UBERON_0000033> <http://www.w3.org/2000/01/rdf-schema#subClassOf> <http://purl.obolibrary.org/obo/UBERON_0000061> .
<http://purl.obolibrary.org/obo/UBERON_0000033> <http://www.w3.org/2000/01/rdf-schema#comment> "The head is the anterior-most division of the body [GO]."@en .
<http://purl.obolibrary.org/obo/UBERON_0000033> <http://www.w3.org/2000/01/rdf-schema#label> "head"@en ."
<http://purl.obolibrary.org/obo/UBERON_0000033> rdf:type owl:Class ;
rdfs:subClassOf <http://purl.obolibrary.org/obo/UBERON_0000061> ;
rdfs:comment "The head is the anterior-most division of the body [GO]."@en ;
rdfs:label "head"@en .
<owl:Class rdf:about="http://purl.obolibrary.org/obo/UBERON_0000033">
<rdfs:subClassOf rdf:resource="http://purl.obolibrary.org/obo/UBERON_0000061"/>
<rdfs:comment xml:lang="en">The head is the anterior-most division of the body [GO].</rdfs:comment>
<rdfs:label xml:lang="en">head</rdfs:label>
</owl:Class>
{
"@id" : "http://purl.obolibrary.org/obo/UBERON_0000033",
"@type" : [ "http://www.w3.org/2002/07/owl#Class" ],
"http://www.w3.org/2000/01/rdf-schema#comment" : [ {
"@language" : "en",
"@value" : "The head is the anterior-most division of the body [GO]."
} ],
"http://www.w3.org/2000/01/rdf-schema#label" : [ {
"@language" : "en",
"@value" : "head"
} ],
"http://www.w3.org/2000/01/rdf-schema#subClassOf" : [ {
"@id" : "http://purl.obolibrary.org/obo/UBERON_0000061"
} ] }
Some previous effort has been devoted to developing and exploiting ontologies related to ALS and MS. The largest part of the work has been dedicated to model Multiple sclerosis [JCS+13, JCR+14, MGR+15, DLT+19, AAA+20], or related concepts such as the EDSS [GSS+05, GSS+09], potential lesions [DE06, GFB+14], or relapses [PRP2020], and use them to predict the progression of the disease [PRP2020]. With respect to ALS, the most relevant works are about the modeling of the care pathway and service provision to patients affected by ALS [CMA+18, CMA+21]. Finally, a line of work investigates the possibility of jointly modeling several diseases, either neurodegenerative [HCD08, CJD+12, JCC+13, GMR+19] or rare [SCA+20] ones - among which authors include ALS and MS. Compared to ALS, MS has received far more attention by the research community for what concerns its modeling through ontologies. We report here the major accomplishments made in this regard. In [JCR+14] Jensen et al. developed the Multiple Sclerosis Patient Data Ontology (MSPD) to represent data from patients affected by MS in the New York State Area. Although very similar to our objective, at the time of writing the ontology is not publicly available and does not include any pieces of information about the ALS. The Multiple Sclerosis Ontology (MSO) [MGR+15] is one of the most comprehensive efforts made in order to model the MS using an ontology. The MSO is validated in the task of automatically annotating Electronic Medical Records and it is capable of achieving an adequate performance of 73% of F1 score. More recently, Alshamrani et al. in [AAA+20], even though not directly involved in the creation of an ontology, present a global overview of the efforts made to utilize ontologies to favour model-driven decision making in multiple sclerosis research. Several works do not model the MS in its entirety, but only some aspects of it. Our work, on the other hand, proposes a holistic approach to model Multiple Sclerosis. For the sake of completeness, we report the main works that model minor aspects of the MS. In [GSS+05] and later in [GSS+09], Gaspari et al. explore the possibility to compute the automatic EDSS (called AEDSS) exploiting an underlying ontology. They identify four main ontological classes: the rules used to infer the EDSS scores, the anatomical functional systems associated with each rule, the questions that allow to assess the degree of impairment, and the overall score. The ontology is therefore used to improve the performance of an expert system. [DE06], on the other hand, exploits an ontology to define rules that can be applied on the automatic categorization of images, to individuate lesions on the brain due to MS. Finally, Pappalardo et al [PRP2020] modelled the Universal Immune System Simulator (UISS), an ontology that describes the immune system activities. The authors also extend the UISS to simulate underlying MS pathogenesis and its interaction with the host immune system. Efforts have been made to ontologically model the care of patients affected by ALS [CMA+18, CMA+21]. Even though the ontologies developed are rich and detailed, they model aspects which are not directly involved in our project. In particular, the focus of both work is on the quality of life and care pathway of patients affected by ALS. Some efforts have been devoted to model multiple neurological diseases with the intent of obtaining a general ontology. An example is the Neurological Disease Ontology (NDO) [CJD+12, JCC+13]. According to The authors, NDO can provide a set of classes to describe the neurological diseases, their symptoms and possible interventions encountered during the clinical practice. Based on such effort, in [JCS+13] Jensen et al. try to adapt the NDO to the modeling of Multiple Sclerosis. Notice that, similarly to MSPD, at current time the NDO does not respect the FAIR principles, since it is neither Findable nor Accessible, thus also preventing Reusability. In [SCA+20] Subirats et al. aim at modeling several rare diseases, including multiple sclerosis, through an ontology, dubbed Holistic Rare Diseases Ontology (HORD). In such ontology it is possible to model also information derived from the patients’ social networks, in order to maintain unstructured data that can be used to assess their current state.
The use of standard identifiers for classes and relations is a key component when creating ontologies to ensure data integration across multiple disconnected databases, files or web sites. The ability to use parts of ontologies to generate new ones specifically tailored for some new application or context while, at the same time, maintaining interoperability with other datasets, is essential [HSG15]. When more ontologies are used in the process of searching for already defined entities and relations, ontology repositories can aid in finding ontologies suitable for annotating data within a specific domain. Among the main resources in the life science domain, we primarily used OntoBee [XMRH11], an ontology repository in which ontologies are presented as Linked Data.
prefix | url | ontology |
---|---|---|
https://www.brainteaser.health/ontology/schema/ | Brainteaser ontology (base prefix) | |
foaf | http://xmlns.com/foaf/spec/ | Friend of a Friend (FOAF) vocabulary |
ncit | http://purl.obolibrary.org/obo/NCIT_ | National Cancer Institute thesaurus (NCIT) |
ogg | http://purl.obolibrary.org/obo/OGG_ | Ontology of Genes and Genomes (OGG) |
oboInOwl | http://www.geneontology.org/formats/oboInOwl# | OBO in OWL |
uberon | http://purl.obolibrary.org/obo/UBERON_ | Uberon |
xsd | http://www.w3.org/2001/XMLSchema# | XML Schema |
maxo | http://purl.obolibrary.org/obo/MAXO_ | Medical Action Ontology (MAxO) |
omit | http://purl.obolibrary.org/obo/OMIT_ | Ontology for MIRNA Target (OMIT) |
snomed | http://purl.bioontology.org/ontology/SNOMEDCT/ | SNOMED Clinical Terms (SNOMED CT) |
atcc | http://purl.bioontology.org/ontology/UATC | Anatomical Therapeutic Chemical Classification (ATCC) |
umls | https://uts.nlm/nih.gov/uts/umls/concepts | Unified Medical Language System |
isco | http://data.europa.eu/esco/isco/ | International Standard Classification of Occupations |
efo | http://www.ebi.ac.uk/efo/EFO_ | Experimental Factor Ontology |
The ontologies used in this project are presented, together with the respective prefixes, in Table 1 . Among these ontologies, some of the most important ones are:
In BO we also use the International Classification of Diseases, in its tenth edition (ICD-10). This is a healthcare classification system that allows more than 55.000 different codes and permits tracking of many new diagnoses and procedures. It is maintained by the World Health Organization (WHO). Also, we use the International Classification of Primary Care (ICPC) ontology, containing the OWL version of the ICPC classification method, that allows for the classification of the patient’s reason for encounter, the problem and diagnosis being managed, the primary or general health care interventions, and the ordering of the data of the primary care session in an episode of care structure
To design the BO ontology we adopted a co-design approach, strictly collaborating with the medical partners and domain experts, in order to embed their knowledge in the BO and, at the same time, to validate all the design choices. To this end, we operated in an iterative way, producing several intermediate versions of the ontology and discussing them with our domain experts.
The design of the BO started by discussing with all the partners which kind of data have to be managed via the ontology and this ended-up on identifying the three categories mentioned above in Section 1: “raw” data, generated data, and evaluation campaigns data. The discussion was initiated during the kickoff meeting in January 2021 and finalized in the first plenary meeting in April 2021.
At this point, the work specifically focusing on retrospective data started. The UNIPD team received simplified samples of data from the medical partners in order to start understanding their features and potential issues. We then prepared forms to elicit requirements from the medical partners and collect attributes that they deemed important to describe both ALS and MS.
The requirement gathering and analysis phase ended up with a preliminary draft of the core parts of the BO and the corresponding schema. This preliminary draft of the BO was discussed face-to-face (virtually) in a dedicated meeting with medical partners in late May 2021, where we went through the overall design choices and the specific classes constituting the BO to validate them. The further feedback gathered from the domain experts led to a revision of the BO which was further discussed in another face-to-face virtual meeting in late June 2021. This additional feedback led to a further refinement of the BO which was then presented and agreed on during the overall plenary meeting in September 2021.
Just after the plenary meeting, full (and anonymized) retrospective data were received from the medical partners: Pavia for MS; Lisbon, Turin and Madrid for ALS. The inspection of the full raw data allowed to further improve and refine the ontology and also to discover some issues about the instances, related to incomplete or noisy data. These updates to the BO and the solutions to address specific issues have been then discussed in one-to-one meetings with the specific medical partner during October and November 2021.
Overall, all these iterations led to the development of the first version of the BRAINTEASER ontology as well as of the mappers for ingesting the retrospective data from the medical partners.
In the following, we describe more in detail the ontology designed to model the Multiple Sclerosis and the Lateral Amyotrophic Sclerosis according to the co-design approach defined in Section 3. In this section we present the main components and the choices that we made, whereas the complete documentation will be uploaded with the final OWL file in an open public repository as Zenodo which enables the seamless integration with EOSC services. Subsection 4.1 details the principles that guided the development of the ontology, while Subsection 4.2 describes the main semantic areas and the principal classes available in each of them.
The ontological modeling proceeded bottom-up starting from the anonymized clinical reports about the four considered diseases provided by the "Instituto de medicina molecular Joao Lobo Antunes" (iMM, Portugal) and Università degli Studi di Torino (UNITO, Italy) for ALS, and by Fondazione Istituto Neurologico Nazionale Casimiro Mondino (MNDV-PV, Italy) for MS.
We analyzed these records and worked together with the physicians and the expert researcher in the field, following shared co-design principles, to accurately identify the classes and relations to include in the ontology. We maximized the re-use of concepts defined in already available and well-known ontologies and vocabularies, thus limiting the creation of new classes and relations to a minimum.
We represent the ontology as a graph where nodes are classes and edges are typed relationships amongst the classes. Classes (nodes) represent real-world objects such as a person, a project, a tissue or an anatomical part.
Relationships (edges) describe how the classes interact one with each other. BO is composed of 362 classes, 360 named individuals, 76 object properties, 220 data properties, and EEE annotation properties. The prefixes used in the ontologies are reported in the table above. Amongst the most used external ontologies, we count the COMPLETE with statistics.
Once released, the URLs of the ontology will be secure and permanent by using the re-direction service provided by the W3 Permanent Identifier Community Group. The service works as a switchboard connecting requests for information with the true location of the information on the Web. It can be, therefore, reconfigured to point to a new location if the old location stops working.
The ontology is divided into eight "semantic areas", i.e., groups of entities and relationships that pertain to different types of concepts and aspects of our domain. Each entity is therefore classified in one of the eight semantic areas. These areas are better detailed in section 4.2, and are:
Whenever possible, we re-used classes from other ontologies to represent entities and created new classes only when unavoidable. The external ontologies used for this are described in Section 2.4.
In particular, there are some cases where we imported a subset of entities from an external ontology in order to represent taxonomies of concepts and their rdfs:subClassOf
relationships. We only imported from these taxonomies the classes that are useful to model the data necessary for the project, i.e. we never import the full taxonomies, but only subsets of them. Some of the classes that work as roots of their respective taxonomies in the Brainteaser ontology are:
ncit:C21480
) This class represents a generic relative of a patient, and is the root of the taxonomy containing different degrees of kinship (such as Father, Mather, Sister, etc.)esco:Occupation
) The class representing a generic job or other type of occupation of the patient.SNOMED:Ethnic_group
) Represents the ethnicity of the patient.ncit:C4876
) The root class of the taxonomy describing the possible symptoms related to a patient.ogg:0000000002
) Root of the gene taxonomy.uberon:0000061
) Root of the taxonomy of the human body locations where events, symptoms and traumas are located.ncit:C1909
) the root of the clinical drugs that may be prescribed to patients as result of a Therapeutic Procedure or as response to a Relapse or Inflammation.ncit:C2991
) the root of the taxonomy with the possible diseases (not only MS and ALS) that a patient, or one of their relatives, may manyfest.We relate each single concept in the BO with the respective concepts in the Unified Medical Language System (UMLS) metathesaurus with the oboInOwl:equivalentClass
relationship. This connection allows us to retrieve all relevant information about a concept as reported in the rich and widely-used UMLS meta-thesaurus. UMLS comprehends alternative naming for the concepts, relationships with other relevant classification schemes such as the International Statistical Classification of Diseases and Related Health Problems, Tenth Revision (ICD-10) and multilingual information when available.
As an example, the "multiple sclerosis" concept is inherited from the MONDO ontology with URI http://purl.obolibrary.org/obo/MONDO_0005301 and in the BO definition for this concept we also report that it is the same as umls:C0026769
. From the UMLS identifier we can retrieve all the information about other classifications such as ICD-10 that identifies multiple sclerosis with the id G35
.
For the classes contained in some of these taxonomies, i.e., the ones with root in Occupation, Ethnic Group, Anatomical Structure, and Pharmacological Substance, it is the case that, when they are the range of properties, no other information needs to be registered. For instance, when registering the presence of a symptom in a particular anatomical location, it is only necessary to know the location, without any further information about it.
The consequence is that each time a new triple with an object in one of these taxonomies is created, we would be forced to create a new instance.
To avoid an explosion in the number of instances of these classes, and due to the fact that no other information about them needs to be modeled, we decided to create named individuals, one for each class in these taxonomies. These named individuals are used as objects of the corresponding object properties every time a new triple needs to be instantiated.
In the remainder of this section, we describe the elements characterizing each semantic area individuated in section 4.1. We use the bold font to indicate ontological classes, monospace font to represent their URI and italic to represent their properties. In case of uri derived from other ontologies, prefixes are defined in Table 1.
The patient semantic area, represented in Figure 3, contains classes and relations pertaining to a patient participating in the clinical trials and general information about this patient, their relatives with diseases, their disease and the participation in a clinical trial.
Central to this area is the Patient class (ncit:C16960
), subclass of foaf:Person
, that presents different properties describing the Patient instance. These are: dateOfDeath (with range xsd:gYear
), genomeSequencing (xsd:string
), educationLevel (rdf:langString
), maritalStatus (rdf:langString
), dextricity (xsd:string
), retiredAtDiagnosis (xsd:string
), menopause (xsd:int
), MSInPaediatricAge (xsd:boolean
), alive (xsd:boolean
).
Patient inherits from foaf:Person
the properties birthplaceCharacteristics (rural or urban areas), and birthplace (defined as an enumeration among village, country town, small town, middle torn, and large town). The Patient is further linked to two additional attributes, gender through the foaf:gender
property, and birthday, via foaf:birthday
property. In order to preserve the anonymity of the patients, real instances will only present the birth year, and not the birth date.
Patient is connected through the ethnicity property to class Ethnic Group (SNOMEDCT:Ethnic_Group
), representing a generic ethnic group. This class is the root of a taxonomy of ethnicities whose classes are taken from other ontologies.
To model the familial predisposition, it is necessary to register the presence of a patient's relatives that may have the studied diseases of their own. To do so, we considered the class Relative (ncit:C21480
) that models a generic relative of a patient. Relative, in turn, is the root class of a taxonomy of kingship classifications such as Parent, FirstDegreeRelative, Father and Mother (these classes are imported directly from the ncit
ontology).
A relative may or may not be a patient in the database. In the first case, the relative instance is connected to its corresponding patient instance through the isPerson property. In the other case, an instance of the class foaf:Person
is created, and the relative instance is connected through isPerson to this instance. One patient or one generic person can be a relative of more than one patient, and for this reason multiple instances of relative may be instantiated, one for each degree of kinship occurring for that patient/person in the database. Each of these instances will be connected through isPerson to the corresponding instance of Patient or foaf:Person
.
Figure 3. Patient semantic area, including the classes Patient, Person, Relative, Clinical Trial, Clinical Trial Participation, and Disease or Disorder.
The class Occupation (ESCO:Occupation
) represents the job of the user. It is the root class of a taxonomy of classes representing different types of jobs, and a patient instance is connected to Occupation through hasOccupation.
foaf:Person
is connected through the property enrolledIn to Clinical Trial Participation (:ClinicalTrialParticipation
), representing the fact that a patient is participating in a clinical trial. A clinical trial instance may have a startDate property, an endDate property and an ending reason, provided by the endReason property.
Each instance of clinical trial participation is part of a Clinical Trial (ncit:C71104
) and connected to this class through the participate property. In turn, a clinical trial pertains to a certain hospital, and therefore the property connects the class Clinical Trial to the class Clinics and Hospitals (ncit:C19326
).
Finally, a person (thus both a patient and a relative who is not present in a trial) can have a disease. foaf:Person
is connected to Disease or Disorder (ncit:C2991
) through hasDisease. Also, the class Clinical Trial is connected to Disease or Disorder through isAboutDisease to indicate which is the disease studied in the specific trial.
Figure 4. Semantic Area containing the information about a patient's gene and their mutations.
A Patient may be associated with data concerning their genetic heritage. To do so, the ontology links the Patient, via the property hasGene, to the class Gene (ogg:0000000002
), as shown in Figure 4. Instances of this class can have two properties: kind and open box. The former allows to express the type of mutation present on the gene, while the latter allows to add further information via unstructured text. The Gene instance can be instantiated either using the Gene class, or one of its relevant subclasses for this specific domain: SOD1 (ogg:3000006647
), FUS (ogg:3000002521
), C9orf72 (ogg:3000203228
), and tardbp (ogg:3000023435
).
Figure 5. Behaviour and Lifestyle semantic area, including the subclasses Smoking, Physical Activity and Lifestyle.
Different aspects of the behaviour of the patient during the passing of time are modeled with classes in this semantic area.
As reported in Figure 5, the main class is Behaviour (ncit:C19683
), presenting the properties startYear and endYear (both with range xsd:gYear
), describing the starting and ending dates of said behaviour. Each instance of the subclasses of Behaviour therefore offers the possibility to register the time span in which such behaviour was sustained. The class Event is connected to Behaviour through hasRegisteredBehaviour.
Different types of behaviours are modeled through the use of subclasses of this main class.
Smoking (ncit:C154329
) represents the patient's habit of smoking. It presents the relations packYear (a quantification of lifetime tobacco exposure defined as: (number of cigarettes smoked per day) x (number of years smoked)/20. Thus, one pack-year corresponds to smoking 20 cigarettes a day for one year), and dailyCigarettes (the number of cigarettes smoked in one day on average).
The class Physical Activity (ncit:C17708
) describes the physical activity usually exerted by the patient. Its properties are intensity (xsd:string
), weeklyFrequence (xsd:integer
) and activityType (xsd:string
).
The class Lifestyle (ncit:C16795
) acts as a container where to put different types of behavioral information concerning the patient. Such behaviors are modeled as properties of the Lifestyle instance, and are: sunExposure (with range xsd:int
), diet (xsd:int
), fatigue (xsd:int
), sexuality (rdf:langString
), femalePeriodStartDate (xsd:date
), and menopause (xsd:boolean
).
Figure 6. Events Semantic Area, including the class Event and its subclasses: Protocol Event, Diagnosis, Before Onset and Onset.
This Events semantic area, depicted in Figure 6, contains some of the most important classes of the ontology, as one of the goals of the ontology itself is to model the events pertaining to the patient and their evolution through time.
Main class here is Event (ncit:C25499
), describing a generic event that can happen to a patient in a medical environment. The Event class is characterized by the two data properties endDate and startDate (both with range xsd:date
), describing the period in which this Event manifested.
Different types of Event are represented through the use of subclasses.
Protocol Event (ncit:C74589
) represents a planned protocol activity such as randomization and study completion, and occurrences, conditions, or incidents independent of planned study evaluations occurring during the trial (e.g., adverse events) or prior to the trial (e.g., medical history). Its subclass is Patient Visit (ncit:C39564
), describing a specific type of protocol event, i.e., a visit of the patient in a hospital.
The event Diagnosis (ncit:C25279) represents the moment in which the patient is officially diagnosed with the disease.
The last two types of Event are the Onset (ncit:C25279
) and Before Onset (:BeforeOnset
). The first one represents the event in which the first symptoms are manifested for the first time to the patient. The Onset, in particular, may be of different types, which are represented as boolean (xsd:boolean
) properties: limbs, bulbar, axial, and generalized. An onset may also present the property cerebrospinalOligloconalBands, which indicates, if the test has been carried out, the presence of such bands in the patient's blood flow. The onset is located in a part of the human body, and thus the Onset event is connected to the class Anatomical Structure (uberon:0000061
) through the site property. The second one, Before Onset, describes an event that happened before the onset, whatever its nature may be. The property howLong registers how much time before the onset this event happened, and it may assume only two string values, defining an event that happened in the last five years, or before the last five years.
An Event instance, in turn, may be linked to various other classes. Event is linked through hasPregnancy to Pregnancy, describing the presence of a pregnancy; to Trauma through hasTrauma, describing the registration of a traumatic event happened to the patient; to Symptom through hasSymptom, describing the presence of symptoms being registered during an event, to Recurrent Disease through hasRelapse, and finally to one or more Intervention or Procedure that may be applied to the patient, through the consist property.
The Contingencies semantic area, represented in Figure 7, contains classes representing "things that may happen": occurrences to the patient that may or may not be related to the disease. They correspond to phenomena in the patient body that cannot be directly planned. We also included a pregnancy among contingencies since, even though partially plannable, it represents a change in the patient body that cannot be ascribed among the medical procedures. These contingencies are still registered during an Event and therefore are linked to the Event in which they are registered via a specific property each.
Figure 7. Contingencies semantic area, composed of classes Recurrent Disease, Trauma, Pregnancy, and Comorbidity.
The classes in this section are:
ncit:C3671
), that describes the presence of a trauma to the body of the patient. It also reports the properties traumaDate (xsd:date
) and traumaDescription (rdf:langString
). The Trauma class is connected to the Anatomical Structure class through the traumaArea object property. It is furthermore linked to the Event during which it is registered via the hasMajorTrauma property.ncit:C25742
) describes the presence of a pregnancy. Event is connected to this class through the hasPregnancy property. This class presents a series of properties about the pregnancy itself: startDate and endDate (xsd:date
), endEvent (rdf:langString
, it describes how the pregnancy ended), complications (rdf:langString
). ncit:C38155
) describes a relapse that may happen to the patient. This class has, in turn, a series of properties describing the relapse, such as relapseStartDate, sequela, recovery, length, etc. The Event object is connected to the Relapse class through the hasRelapse property. Relapse, in turn, may be associated to a Pregnancy (hasAssociatedPregnancy), to a prescribed Pharmacologic Substance (associatedSubstance), to a requested MRI (requiresMRI), and to a possible Intervention (relapseAssessment) required to assess the presence of the relapse itself.ncit:C16457
) represents the presence of two or more diseases or medical conditions in a patient. The Comorbidity is characterized by the startYear and endYear property, together with treatment (xsd:string
), reporting the prescribed treatment, and severity, describing the severity of the comorbidity from a set of string values (slight, moderate, serious, life risk). A Comorbidity is registered during an Event, and the two classes are connected through hasRegisteredComorbidity.This semantic area contains the classes describing the interventions done to a patient to understand, keep under control, and intervene on their clinical condition.
The class Event is connected to the main class of this area, Intervention or Procedure (ncit:C25218
), through the consists object property. This class represents "a general activity that produces an effect, is meant to clinically assess, or is intended to alter the course of a disease in a patient" (from its NCI Thesaurus definition).
Instances of the Intervention or Procedure class can have two properties: startDate and endDate. Such dates allow us to register the starting and ending moment of the intervention, if this is something continued in time. Notice that, thanks to an abuse of notation, by leaving empty the endDate, we can also represent interventions and procedures that are atomic in time, i.e., are not distributed through more days. The ontology contains different subclasses for Intervention, and each of them supersedes a semantic sub-area depending on the nature of the procedure itself. We describe the characteristics of the main intervention and procedures in the remainder of this subsection.
Figure 8. Therapeutic Procedure semantic area, sub-area of the Intervention or Procedure area.
The subclass Therapeutic Procedure (ncit:C49236
), depicted in Figure 8, represents the action or administration of therapeutic agents to produce an effect that is intended to alter or stop a pathologic process.
We considered three possible types of therapeutic procedures: a generic therapy (the Therapeutic Procedure class itself), a Disease Modifying Therapy (DMT) and a Mechanical Ventilation (NIV) (ncit:C171457
).
DMT presents the property seriousAdversarialEvent (also referred to in the documents as SAE), which indicates the occurrence of a serious adverse reaction to a specific Disease modifying therapy.
All the possible therapeutic procedures might involve the prescription or the associated usage of one or more pharmacological substances. The administration of these substances is modeled here through the use of the class Administration (ncit:C25409
), characterized by properties describing the administration itself: administrationRoute (rdf:langString
), endReason (rdf:langString
), dose (xsd:float
), medicineName (xsd:string
), frequency (rdf:langString
).
An Administration is related to the administered substance, here represented through the class Pharmacological Substance (ncit:C1909
), through the object property isRelated.
Among the possible substances that may be administered (subclasses of Pharmacological Substance), the following have been identified as particularly relevant to the domain: Vaccine (ncit:C923
), Agent Affecting Nervous System (ncit:C78927
) (and especially its subclass Riluzole (ncit:C47704
)), and cortisone treatment (:cortisone_treatment
).
Figure 9.a. Part 1 of the Diagnostic Procedure semantic area, a sub-area of the Intervention or Procedure area. This figure reports the subclasses Pulmonary Function Test, Blood Test and EDSS.
Diagnostic Procedure (ncit:C18020
) is another subclass of Intervention or Procedure, and it represents any procedure or test to diagnose and assess the progression of a disease or disorder. This, in turn, presents many subclasses. Due to this, we further divided the graphical representation of this sub-area in different Figures: Figure 9.a, 9.b and 9.c, to help their readability.
Starting from Figure 9.a, we see the Pulmonary Function Test (ncit:C38081
). As the name suggests, it is used to store information about pulmonary function tests carried out on the patient. Instances of such class have several properties associated, each of which correspond to a parameter used to assess the quality of the respiratory functions of the patient (i.e., VC, FVC, etc. …). Another subclass here is the Blood Test (ncit:C49286
), representing a test to measure hematopoietic components and investigate hematologic disorders. The relevant parameters assessed via a blood test are represented through the use of properties of this class.
The Expanded Disability Status Scale (EDSS) (ncit:C98302
) is a subclass describing a system for quantifying the level of disability for multiple sclerosis. The EDSS is traditionally computed considering 12 different items: each of these items is represented by a property of this class with range xsd:float
.
Figure 9.b. Part 2 of the Diagnostic Procedure semantic area, a sub-area of the Intervention or Procedure area. This figure reports the subclasses Questionnaire and clinical assessment.
We continue with the classes belonging to this sub-area in Figure 9.b. The Questionnaire (ncit:C17048
) class represents a questionnaire that is submitted to the patients at each visit. In turn, different types of questionnaires may be submitted, with different sets of questions.
The class Clinical Assessment (maxo:0000487
) represents a measurement performed in a clinical setting using clinicians' observations and instrument data to inform patient care and research. The instances of this class may contain different fields with the data collected during the assessment itself, as can be seen in the figure.
Figure 9.c. Part 3 of the Diagnostic Procedure semantic area, a sub-area of the Intervention or Procedure area. This figure reports the subclasses Evoked Potentials and Diagnostic Imaging, together with the properties connecting them to other classes of the ontology belonging to different semantic areas.
Finally, Figure 9.c reports the last classes of this sub-area. With Evoked Potentials (omit:0006295
) we mean a class of tests used to measure the electrical activity in certain areas of the brain and spinal cord. Evoked potentials test and record how quickly and completely the nerve signals reach the brain. These types of tests are helpful in diagnosing such conditions as multiple sclerosis and other neurological disorders. Key properties for this type of Procedures are the potentialValue (a value among normal and altered), and the location. Electrical activity is produced by stimulation of specific sensory nerve pathways. In the ontology there are subclasses describing the different types of Evoked Potentials: Visual Evoked Potentials (omit:0006298
), Motor Evoked Potentials (omit:0019166
), Auditory Evoked Potentials (omit:0006296
) and the Somatosensory Evoked Potential (omit:0006297
).
With Diagnostic Imaging (ncit:C16502
) we refer to various techniques of viewing the inside of the body to help figure out the cause of an illness or injury, and thus confirm a diagnosis. Doctors also use it to see how well a patient's body is responding to treatment for a fracture or illness. Subclasses of Diagnostic Imaging are the Magnetic Resonance Imaging, also known as MRI (ncit:C16809
), characterized by properties describing its results, and the Positron Emission Tomography, also known as PET (ncit:C17007
).
Figure 10. Surgical Procedure semantic area, sub are of the Intervention or Procedure area.
The Surgical Procedure class describes a generic surgical operation performed on the patient. As seen in Figure 10, Its subclasses represented in the ontology are: Percutaneous Endoscopic Gastrostomy (PEG, ncit:C10604
), a procedure in which a flexible feeding tube is placed through the abdominal wall and into the stomach, allowing nutritions, fluids and medications to be put directly into the stomach, thus bypassing mouth and esophagus; tracheotomy (or tracheostomy, ncit:C15341
), an opening surgically created through the neck into the trachea to allow direct access to the breathing tube; Cerebrospinal fluid examination (CSF Analysis, ncit:C173272
), the analysis of the cerebrospinal fluid, a clear, colorless liquid found the the brain and spinal cord, acting like a cushion against sudden impact or injury to the brain or spinal cord. This last class is characterized by the properties cerebrospinalFluid and lymphocytes, describing aspects of the test's results.
This area, shown in Figure 11, contains the Anatomical Structure (uberon:0000061
) class. Such class, due to its nature and function, cannot be assimilated to any other already available classes and semantic areas.
The class Anatomical Structure is the root of a taxonomy containing classes representing parts of the human anatomy used throughout the ontology. To avoid creating new instances of a certain location every time it is required, we define a named individual for each of the required anatomical structures: all the resources that need to be associated with one or more anatomical structures will point to the same name individual.
The Anatomical Structure is the range of many object properties in the Brainteaser ontology. Some examples are site (connecting the Onset to the Anatomical Location), traumaArea (connecting the class Trauma and indicating where it happened), area (connecting the class Diagnostic Imaging), surgicalArea (connecting Anatomical Structure to the class Surgical Procedure), and symptomArea (connecting it to the class Symptom).
Figure 11. Anatomical Structure Semantic Area
The Symptoms semantic area, shown in Figure 12, contains classes describing the symptoms that may happen to a patient and be registered during an Event.
The class Event is connected to the main class of this area, Symptom (ncit:C4876
), through the hasSymptom object property. The Symptom class, in turn, is connected to the Anatomical Structure class through the symptomArea property, allowing to specify the area associated with a specific symptom.
The resources will be rarely of type Symptom, since it is too generic to describe any real characteristic of the patient's disease course. Among symptom instances, we list here the Nervous System Finding (ncit:C36280
) and its subclass, the Fasciculation (ncit:C34606
) and the Inflammation (ncit:C3137
). These symptoms are among the most relevant concerning the diseases modeled in this ontology. For the case of Inflammation, in particular, we register the Pharmacologic Substance being administered, through the associatedSubstance object property.
Figure 12. Symptoms semantic area.
IRI: http://purl.obolibrary.org/obo/NCIT_C28397
IRI: http://purl.obolibrary.org/obo/UBERON_0013493
IRI: http://purl.obolibrary.org/obo/NCIT_C26682
IRI: http://purl.bioontology.org/ontology/ATC/N06BX12
IRI: http://purl.bioontology.org/ontology/ATC/J05AB01
IRI: http://purl.obolibrary.org/obo/NCIT_C35204
IRI: http://purl.obolibrary.org/obo/NCIT_C2852
IRI: http://data.europa.eu/esco/isco/C12
IRI: http://data.europa.eu/esco/isco/C92
IRI: http://purl.bioontology.org/ontology/ATC/L04AA34
IRI: http://purl.bioontology.org/ontology/ATC/V04CL
IRI: http://purl.bioontology.org/ontology/ATC/N05BA12
IRI: https://w3id.org/brainteaser/ontology/schema/ALSFRS
IRI: https://w3id.org/brainteaser/ontology/schema/ALSFRS-R
IRI: http://purl.bioontology.org/ontology/ATC/N04BB01
IRI: http://purl.bioontology.org/ontology/ATC/C01BD01
IRI: http://purl.bioontology.org/ontology/ATC/N06AA09
IRI: http://purl.bioontology.org/ontology/ATC/C08CA01
IRI: http://purl.obolibrary.org/obo/MONDO_0004976
IRI: http://purl.obolibrary.org/obo/UBERON_0000061
IRI: http://purl.obolibrary.org/obo/NCIT_C2869
IRI: http://purl.obolibrary.org/obo/NCIT_C8668
IRI: http://purl.obolibrary.org/obo/NCIT_C2878
IRI: http://data.europa.eu/esco/isco/C03
IRI: http://purl.bioontology.org/ontology/SNOMEDCT/315280000
IRI: http://purl.obolibrary.org/obo/NCIT_C34932
IRI: http://data.europa.eu/esco/isco/C82
IRI: http://purl.bioontology.org/ontology/ATC/C07AB03
IRI: http://purl.bioontology.org/ontology/ATC/C10AA05
IRI: http://purl.obolibrary.org/obo/NCIT_C50466
IRI: http://purl.obolibrary.org/obo/NCIT_C51224
IRI: http://purl.obolibrary.org/obo/NCIT_C71405
IRI: http://purl.obolibrary.org/obo/NCIT_C2889
IRI: http://purl.bioontology.org/ontology/ATC/L04AX01
IRI: http://purl.bioontology.org/ontology/ATC/M03BX01
IRI: http://purl.obolibrary.org/obo/NCIT_C34935
IRI: http://purl.bioontology.org/ontology/ATC/N03AA04
IRI: http://purl.obolibrary.org/obo/NCIT_C156767
IRI: https://w3id.org/brainteaser/ontology/schema/Before_Onset
IRI: http://purl.bioontology.org/ontology/ATC/H02AB01
IRI: http://purl.bioontology.org/ontology/ATC/C07AB07
IRI: http://purl.bioontology.org/ontology/SNOMEDCT/18167009
IRI: http://purl.obolibrary.org/obo/NCIT_C112183
IRI: http://purl.obolibrary.org/obo/NCIT_C118723
IRI: http://purl.obolibrary.org/obo/UBERON_0013706
IRI: http://purl.bioontology.org/ontology/ATC/M03AX01
IRI: https://w3id.org/brainteaser/ontology/schema/Bowel_and_Bladder
IRI: http://purl.obolibrary.org/obo/NCIT_C9175
IRI: http://purl.obolibrary.org/obo/UBERON_0000955
IRI: http://purl.obolibrary.org/obo/NCIT_C12441
IRI: https://w3id.org/brainteaser/ontology/schema/Brainstem_Symptom
IRI: http://purl.bioontology.org/ontology/ATC/N05BA08
IRI: http://purl.obolibrary.org/obo/NCIT_C25289
IRI: http://purl.obolibrary.org/obo/NCIT_C84601
IRI: http://data.europa.eu/esco/isco/C71
IRI: http://data.europa.eu/esco/isco/C33
IRI: http://data.europa.eu/esco/isco/C24
IRI: http://purl.obolibrary.org/obo/OGG_3000203228
IRI: http://purl.bioontology.org/ontology/ATC/C09DA06
IRI: http://purl.bioontology.org/ontology/ATC/N02BG10
IRI: http://purl.bioontology.org/ontology/ATC/N03AF01
IRI: http://purl.obolibrary.org/obo/NCIT_C2931
IRI: http://purl.obolibrary.org/obo/NCIT_C70911
IRI: http://purl.bioontology.org/ontology/SNOMEDCT/14045001
IRI: https://w3id.org/brainteaser/ontology/schema/Cerebellar_Symptom
IRI: http://purl.obolibrary.org/obo/UBERON_0006072
IRI: http://purl.obolibrary.org/obo/UBERON_0002726
IRI: http://data.europa.eu/esco/isco/C11
IRI: http://purl.bioontology.org/ontology/ATC/N07CA02
IRI: http://purl.bioontology.org/ontology/ATC/N07CA52
IRI: http://purl.bioontology.org/ontology/ATC/N06AB04
IRI: https://uts.nlm.nih.gov/uts/umls/concept/C0008848
IRI: http://purl.bioontology.org/ontology/ATC/L01BB04
IRI: http://data.europa.eu/esco/isco/C91
IRI: http://purl.obolibrary.org/obo/MAXO_0000487
IRI: http://purl.obolibrary.org/obo/NCIT_C71104
IRI: https://w3id.org/brainteaser/ontology/schema/Clinical_Trial_Participation
IRI: http://purl.bioontology.org/ontology/ATC/N03AE01
IRI: http://purl.bioontology.org/ontology/ATC/B01AC04
IRI: http://data.europa.eu/esco/isco/C01
IRI: http://purl.obolibrary.org/obo/NCIT_C34360
IRI: https://w3id.org/brainteaser/ontology/schema/cortisone_treatment
IRI: https://w3id.org/brainteaser/ontology/schema/Critical_Episode
IRI: http://purl.obolibrary.org/obo/NCIT_C173272
IRI: http://data.europa.eu/esco/isco/C42
IRI: http://purl.bioontology.org/ontology/ATC/L01AA01
IRI: http://purl.obolibrary.org/obo/NCIT_C25165
IRI: http://purl.obolibrary.org/obo/NCIT_C49343
IRI: http://purl.bioontology.org/ontology/ATC/H02AB13
IRI: http://purl.bioontology.org/ontology/ATC/M05BX04
IRI: http://purl.obolibrary.org/obo/NCIT_C2982
IRI: http://purl.bioontology.org/ontology/ATC/H02AB02
IRI: http://purl.obolibrary.org/obo/NCIT_C2985
IRI: http://purl.obolibrary.org/obo/NCIT_C15220
IRI: http://purl.obolibrary.org/obo/NCIT_C16502
IRI: http://purl.obolibrary.org/obo/NCIT_C18020
IRI: http://purl.bioontology.org/ontology/ATC/N05BA01
IRI: http://purl.bioontology.org/ontology/ATC/L04AX07
IRI: https://w3id.org/brainteaser/ontology/schema/Disease_Modifying_Therapy
IRI: http://purl.obolibrary.org/obo/NCIT_C37943
IRI: http://data.europa.eu/esco/isco/C83
IRI: http://purl.bioontology.org/ontology/ATC/N06AX21
IRI: http://purl.obolibrary.org/obo/NCIT_C80385
IRI: http://data.europa.eu/esco/isco/C74
IRI: http://data.europa.eu/esco/isco/C9
IRI: http://purl.bioontology.org/ontology/ATC/C09AA02
IRI: http://purl.obolibrary.org/obo/NCIT_C3014
IRI: http://purl.obolibrary.org/obo/NCIT_C3134
IRI: http://purl.obolibrary.org/obo/NCIT_C3478
IRI: http://purl.obolibrary.org/obo/OMIT_0006295
IRI: http://purl.obolibrary.org/obo/OMIT_0006296
IRI: http://purl.obolibrary.org/obo/OMIT_0019166
IRI: http://purl.obolibrary.org/obo/OMIT_0006297
IRI: http://purl.obolibrary.org/obo/OMIT_0006298
IRI: http://purl.obolibrary.org/obo/NCIT_C98302
IRI: http://purl.obolibrary.org/obo/NCIT_C12401
IRI: https://w3id.org/brainteaser/ontology/schema/Eye_Symptom
IRI: http://purl.obolibrary.org/obo/NCIT_C26769
IRI: http://purl.bioontology.org/ontology/ATC/N07XX07
IRI: http://purl.obolibrary.org/obo/NCIT_C25174
IRI: http://purl.obolibrary.org/obo/NCIT_C3036
IRI: http://purl.obolibrary.org/obo/NCIT_C3038
IRI: http://purl.bioontology.org/ontology/ATC/L04AA27
IRI: http://purl.obolibrary.org/obo/NCIT_C21481
IRI: http://purl.obolibrary.org/obo/NCIT_C78302
IRI: http://purl.bioontology.org/ontology/ATC/N06AB03
IRI: http://data.europa.eu/esco/isco/C94
IRI: http://data.europa.eu/esco/isco/C75
IRI: http://purl.bioontology.org/ontology/ATC/C03CA01
IRI: http://purl.obolibrary.org/obo/OGG_3000002521
IRI: http://purl.bioontology.org/ontology/ATC/N03AX12
IRI: http://purl.obolibrary.org/obo/OGG_0000000002
IRI: http://data.europa.eu/esco/isco/C41
IRI: http://purl.bioontology.org/ontology/ATC/L03AX13
IRI: http://purl.obolibrary.org/obo/NCIT_C26782
IRI: http://purl.obolibrary.org/obo/NCIT_C71388
IRI: http://purl.obolibrary.org/obo/NCIT_C71397
IRI: http://purl.obolibrary.org/obo/NCIT_C71385
IRI: http://data.europa.eu/esco/isco/C73
IRI: http://purl.obolibrary.org/obo/NCIT_C27191
IRI: http://purl.obolibrary.org/obo/UBERON_0000033
IRI: http://data.europa.eu/esco/isco/C32
IRI: http://data.europa.eu/esco/isco/C22
IRI: http://purl.obolibrary.org/obo/NCIT_C3079
IRI: http://purl.obolibrary.org/obo/NCIT_C50577
IRI: http://purl.obolibrary.org/obo/NCIT_C49286
IRI: http://purl.obolibrary.org/obo/NCIT_C3096
IRI: http://purl.obolibrary.org/obo/NCIT_C34685
IRI: https://w3id.org/brainteaser/ontology/schema/Herniated_Disk
IRI: https://w3id.org/brainteaser/ontology/schema/Herpes_Labialis
IRI: http://purl.obolibrary.org/obo/NCIT_C71079
IRI: https://w3id.org/brainteaser/ontology/schema/Herpetic_Keratitis
IRI: http://purl.bioontology.org/ontology/SNOMEDCT/414408004
IRI: http://data.europa.eu/esco/isco/C14
IRI: http://purl.bioontology.org/ontology/ATC/D07AA02
IRI: http://purl.bioontology.org/ontology/ATC/H02AB09
IRI: http://purl.bioontology.org/ontology/ATC/P01BA02
IRI: http://purl.obolibrary.org/obo/NCIT_C3117
IRI: http://purl.obolibrary.org/obo/NCIT_C3123
IRI: http://purl.obolibrary.org/obo/NCIT_C26800
IRI: http://purl.obolibrary.org/obo/NCIT_C79750
IRI: http://purl.obolibrary.org/obo/NCIT_C34726
IRI: http://purl.obolibrary.org/obo/NCIT_3137
IRI: http://data.europa.eu/esco/isco/C35
IRI: http://data.europa.eu/esco/isco/C25
IRI: https://dbpedia.org/ontology/institution
IRI: http://purl.bioontology.org/ontology/ATC/L03AB07
IRI: http://purl.bioontology.org/ontology/ATC/L03AB08
IRI: http://purl.obolibrary.org/obo/NCIT_C27006
IRI: http://purl.obolibrary.org/obo/NCIT_C34736
IRI: http://purl.obolibrary.org/obo/NCIT_C84484
IRI: https://w3id.org/brainteaser/ontology/schema/Kings
IRI: http://data.europa.eu/esco/isco/C93
IRI: http://purl.bioontology.org/ontology/ATC/N03AX09
IRI: http://purl.obolibrary.org/obo/NCIT_C3107
IRI: http://data.europa.eu/esco/isco/C26
IRI: http://data.europa.eu/esco/isco/C34
IRI: http://purl.bioontology.org/ontology/ATC/C08CA13
IRI: http://purl.obolibrary.org/obo/NCIT_C26816
IRI: http://purl.bioontology.org/ontology/ATC/N03AX14
IRI: http://purl.bioontology.org/ontology/ATC/N04BA02
IRI: http://purl.bioontology.org/ontology/ATC/H03AA01
IRI: http://purl.obolibrary.org/obo/NCIT_C16795
IRI: http://purl.obolibrary.org/obo/NCIT_C12429
IRI: https://w3id.org/brainteaser/ontology/schema/Lumbar_Hernia
IRI: http://purl.obolibrary.org/obo/UBERON_0001815
IRI: http://purl.obolibrary.org/obo/NCIT_C26823
IRI: http://purl.obolibrary.org/obo/NCIT_C16809
IRI: http://purl.obolibrary.org/obo/NCIT_C2920
IRI: http://data.europa.eu/esco/isco/C61
IRI: http://data.europa.eu/esco/isco/C62
IRI: http://purl.obolibrary.org/obo/NCIT_C7570
IRI: http://data.europa.eu/esco/isco/C72
IRI: http://purl.bioontology.org/ontology/ATC/L01BA01
IRI: http://purl.bioontology.org/ontology/ATC/D07AA01
IRI: http://purl.bioontology.org/ontology/ATC/H02AB04
IRI: http://purl.obolibrary.org/obo/NCIT_C117005
IRI: http://purl.bioontology.org/ontology/ATC/N06AX11
IRI: https://w3id.org/brainteaser/ontology/schema/Mitos
IRI: http://purl.bioontology.org/ontology/ATC/L01DB07
IRI: http://purl.bioontology.org/ontology/ATC/N06BA07
IRI: http://purl.obolibrary.org/obo/NCIT_C35548
IRI: http://purl.obolibrary.org/obo/NCIT_C25189
IRI: http://purl.obolibrary.org/obo/MONDO_0005301
IRI: http://purl.obolibrary.org/obo/NCIT_C29888
IRI: http://purl.obolibrary.org/obo/NCIT_C60989
IRI: http://purl.obolibrary.org/obo/NCIT_C3390
IRI: http://purl.bioontology.org/ontology/ATC/N07BB04
IRI: http://purl.bioontology.org/ontology/ATC/L04AA23
IRI: http://purl.bioontology.org/ontology/ATC/C07AB12
IRI: http://purl.obolibrary.org/obo/UBERON_0000974
IRI: http://purl.obolibrary.org/obo/NCIT_C50667
IRI: https://w3id.org/brainteaser/ontology/schema/Neoplasia
IRI: http://purl.obolibrary.org/obo/NCIT_C71409
IRI: http://purl.obolibrary.org/obo/NCIT_C36280
IRI: http://purl.obolibrary.org/obo/NCIT_C71408
IRI: https://w3id.org/brainteaser/ontology/schema/NMSC
IRI: http://data.europa.eu/esco/isco/C02
IRI: http://purl.obolibrary.org/obo/NCIT_C171457
IRI: http://data.europa.eu/esco/isco/C43
IRI: http://purl.obolibrary.org/obo/NCIT_C3283
IRI: http://data.europa.eu/esco/model#Occupation
IRI: http://purl.bioontology.org/ontology/ATC/L04AA36
IRI: http://purl.bioontology.org/ontology/ATC/C09CA08
IRI: http://purl.obolibrary.org/obo/NCIT_C25279
IRI: http://purl.obolibrary.org/obo/NCIT_C3298
IRI: http://data.europa.eu/esco/isco/C44
IRI: http://purl.bioontology.org/ontology/ATC/J07BX
IRI: http://purl.bioontology.org/ontology/ATC/N03AF02
IRI: http://purl.bioontology.org/ontology/ATC/G04BD04
IRI: http://purl.bioontology.org/ontology/ATC/N05AX13
IRI: http://purl.bioontology.org/ontology/ATC/N06AB05
IRI: http://purl.obolibrary.org/obo/NCIT_C122812
IRI: http://purl.obolibrary.org/obo/NCIT_C16960
IRI: http://purl.obolibrary.org/obo/NCIT_C39564
IRI: http://purl.bioontology.org/ontology/ATC/L03AB13
IRI: http://purl.obolibrary.org/obo/UBERON_0010709
IRI: http://purl.obolibrary.org/obo/NCIT_C34911
IRI: http://purl.obolibrary.org/obo/NCIT_C106040
IRI: http://purl.bioontology.org/ontology/ATC/C09BB04
IRI: http://www.w3.org/2000/10/swap/pim/contact#Person
IRI: http://data.europa.eu/esco/isco/C53
IRI: http://data.europa.eu/esco/isco/C51
IRI: http://purl.obolibrary.org/obo/NCIT_C34922
IRI: http://purl.bioontology.org/ontology/ATC/N03AA02
IRI: http://purl.obolibrary.org/obo/NCIT_C17708
IRI: http://purl.obolibrary.org/obo/NCIT_C3329
IRI: http://purl.obolibrary.org/obo/NCIT_C157959
IRI: http://purl.obolibrary.org/obo/NCIT_C17007
IRI: https://w3id.org/brainteaser/ontology/schema/Postoperative_Hypothyroidism
IRI: http://purl.bioontology.org/ontology/ATC/N04BC05
IRI: http://purl.bioontology.org/ontology/ATC/B01AC22
IRI: http://purl.bioontology.org/ontology/ATC/N05BA11
IRI: http://purl.bioontology.org/ontology/ATC/H02AB07
IRI: http://purl.bioontology.org/ontology/ATC/N03AX16
IRI: http://purl.obolibrary.org/obo/NCIT_C8509
IRI: http://data.europa.eu/esco/isco/C13
IRI: http://purl.bioontology.org/ontology/ATC/C07AA05
IRI: http://data.europa.eu/esco/isco/C54
IRI: http://purl.obolibrary.org/obo/NCIT_C74589
IRI: http://purl.obolibrary.org/obo/NCIT_C3346
IRI: http://purl.obolibrary.org/obo/NCIT_C50713
IRI: http://purl.obolibrary.org/obo/NCIT_C38081
IRI: http://purl.obolibrary.org/obo/NCIT_C34997
IRI: https://w3id.org/brainteaser/ontology/schema/Pulmonary_Thromboembolism
IRI: https://w3id.org/brainteaser/ontology/schema/Pyramidal_Symptom
IRI: http://purl.obolibrary.org/obo/NCIT_C17048
IRI: http://purl.bioontology.org/ontology/ATC/C09AA05
IRI: http://data.europa.eu/esco/isco/C96
IRI: http://purl.obolibrary.org/obo/NCIT_C78593
IRI: http://purl.obolibrary.org/obo/NCIT_C26874
IRI: http://purl.obolibrary.org/obo/NCIT_C2884
IRI: http://purl.bioontology.org/ontology/ATC/N07XX02
IRI: http://purl.bioontology.org/ontology/ATC/L01XC02
IRI: http://purl.bioontology.org/ontology/ATC/B01AF01
IRI: http://purl.bioontology.org/ontology/ATC/N06DA03
IRI: https://uts.nlm.nih.gov/uts/umls/concept/C0178837
IRI: http://data.europa.eu/esco/isco/C52
IRI: http://purl.obolibrary.org/obo/NCIT_C94575
IRI: http://data.europa.eu/esco/isco/C31
IRI: http://data.europa.eu/esco/isco/C21
IRI: http://purl.obolibrary.org/obo/NCIT_C19811
IRI: http://purl.obolibrary.org/obo/NCIT_C3020
IRI: http://purl.obolibrary.org/obo/NCIT_C63711
IRI: http://purl.bioontology.org/ontology/ATC/N06AB06
IRI: http://purl.obolibrary.org/obo/NCIT_C55098
IRI: http://purl.obolibrary.org/obo/NCIT_C35020
IRI: http://purl.obolibrary.org/obo/NCIT_C25204
IRI: http://purl.bioontology.org/ontology/ATC/L04AA42
IRI: http://purl.obolibrary.org/obo/NCIT_C25680
IRI: http://purl.bioontology.org/ontology/ATC/A10BH01
IRI: http://purl.obolibrary.org/obo/NCIT_C26883
IRI: http://purl.obolibrary.org/obo/NCIT_C154329
IRI: http://purl.obolibrary.org/obo/OGG_3000006647
IRI: http://purl.obolibrary.org/obo/NCIT_C25205
IRI: http://purl.obolibrary.org/obo/UBERON_0002240
IRI: https://w3id.org/brainteaser/ontology/schema/Spinal_Cord_Symptom
IRI: http://data.europa.eu/esco/isco/C81
IRI: http://data.europa.eu/esco/isco/C95
IRI: http://www.ebi.ac.uk/efo/EFO_0000712
IRI: http://data.europa.eu/esco/isco/C63
IRI: http://purl.bioontology.org/ontology/ATC/A07EC01
IRI: https://w3id.org/brainteaser/ontology/schema/Supratentorial_Symptom
IRI: http://purl.obolibrary.org/obo/NCIT_C15329
IRI: http://purl.obolibrary.org/obo/NCIT_C170740
IRI: http://purl.obolibrary.org/obo/NCIT_C35053
IRI: http://purl.bioontology.org/ontology/ATC/L02BA01
IRI: http://purl.obolibrary.org/obo/OGG_3000023435
IRI: http://data.europa.eu/esco/isco/C23
IRI: http://purl.bioontology.org/ontology/ATC/C09CA07
IRI: http://purl.bioontology.org/ontology/ATC/L04AA31
IRI: http://purl.bioontology.org/ontology/ATC/H01AA02
IRI: http://purl.obolibrary.org/obo/NCIT_C35069
IRI: http://purl.obolibrary.org/obo/NCIT_C49236
IRI: http://purl.bioontology.org/ontology/ATC/H03BB02
IRI: http://purl.obolibrary.org/obo/UBERON_0014477
IRI: http://purl.obolibrary.org/obo/UBERON_0003038
IRI: http://purl.obolibrary.org/obo/NCIT_C28195
IRI: http://purl.obolibrary.org/obo/NCIT_C26893
IRI: http://purl.obolibrary.org/obo/NCIT_C26894
IRI: http://purl.bioontology.org/ontology/ATC/B01AC05
IRI: http://purl.bioontology.org/ontology/ATC/M03BX02
IRI: https://uts.nlm.nih.gov/uts/umls/concept/C0920367
IRI: http://purl.bioontology.org/ontology/ATC/N03AX11
IRI: https://uts.nlm.nih.gov/uts/umls/concept/C0557750
IRI: http://purl.obolibrary.org/obo/NCIT_C15341
IRI: http://purl.obolibrary.org/obo/NCIT_C50781
IRI: http://purl.bioontology.org/ontology/ATC/N06AX05
IRI: http://purl.bioontology.org/ontology/ATC/G04BD09
IRI: http://purl.obolibrary.org/obo/NCIT_C2986
IRI: http://purl.obolibrary.org/obo/NCIT_C26747
IRI: http://purl.obolibrary.org/obo/NCIT_C71404
IRI: http://purl.bioontology.org/ontology/ATC/N03AG01
IRI: http://purl.bioontology.org/ontology/ATC/N06AX16
IRI: https://w3id.org/brainteaser/ontology/schema/Vertebral_Hernia
IRI: http://purl.bioontology.org/ontology/ATC/N03AG04
IRI: http://purl.bioontology.org/ontology/ATC/B01AA03
IRI: http://purl.bioontology.org/ontology/ATC/N05CF02
IRI: http://purl.bioontology.org/ontology/ATC/N05AF05
IRI: https://w3id.org/brainteaser/ontology/schema/area
IRI: https://w3id.org/brainteaser/ontology/schema/associatedSubstance
IRI: https://w3id.org/brainteaser/ontology/schema/consists
IRI: https://w3id.org/brainteaser/ontology/schema/determinedBy
IRI: https://w3id.org/brainteaser/ontology/schema/employs
IRI: https://w3id.org/brainteaser/ontology/schema/enrolledIn
IRI: https://w3id.org/brainteaser/ontology/schema/ethnicity
has characteristics: functional
IRI: https://w3id.org/brainteaser/ontology/schema/hasAdministration
IRI: https://w3id.org/brainteaser/ontology/schema/hasAssociatedPregnancy
IRI: https://w3id.org/brainteaser/ontology/schema/hasBirthplace
IRI: https://w3id.org/brainteaser/ontology/schema/hasDisease
IRI: https://w3id.org/brainteaser/ontology/schema/hasGene
IRI: https://w3id.org/brainteaser/ontology/schema/hasOccupation
has characteristics: functional
IRI: https://w3id.org/brainteaser/ontology/schema/hasPregnancy
IRI: https://w3id.org/brainteaser/ontology/schema/hasRegisteredBehaviour
IRI: https://w3id.org/brainteaser/ontology/schema/hasRegisteredComorbidity
IRI: https://w3id.org/brainteaser/ontology/schema/hasRelapse
IRI: https://w3id.org/brainteaser/ontology/schema/hasRelative
IRI: https://w3id.org/brainteaser/ontology/schema/hasResidence
IRI: https://w3id.org/brainteaser/ontology/schema/hasSymptom
IRI: https://w3id.org/brainteaser/ontology/schema/hasTrauma
IRI: https://w3id.org/brainteaser/ontology/schema/isAboutDisease
IRI: https://w3id.org/brainteaser/ontology/schema/isPerson
IRI: https://w3id.org/brainteaser/ontology/schema/isRelated
IRI: https://w3id.org/brainteaser/ontology/schema/partecipate
IRI: https://w3id.org/brainteaser/ontology/schema/pertain
IRI: https://w3id.org/brainteaser/ontology/schema/relapseAssessment
IRI: https://w3id.org/brainteaser/ontology/schema/requiresMRI
IRI: https://w3id.org/brainteaser/ontology/schema/sameAs_ICD10
IRI: https://w3id.org/brainteaser/ontology/schema/sameAsUMLS
IRI: https://w3id.org/brainteaser/ontology/schema/site
IRI: https://w3id.org/brainteaser/ontology/schema/surgicalArea
IRI: https://w3id.org/brainteaser/ontology/schema/symptomArea
IRI: https://w3id.org/brainteaser/ontology/schema/traumaArea
IRI: https://w3id.org/brainteaser/ontology/schema/undergo
IRI: https://w3id.org/brainteaser/ontology/schema/activityType
IRI: https://w3id.org/brainteaser/ontology/schema/administrationRoute
IRI: https://w3id.org/brainteaser/ontology/schema/age_onset
IRI: https://w3id.org/brainteaser/ontology/schema/albumin
IRI: https://w3id.org/brainteaser/ontology/schema/Albumin_level
IRI: https://w3id.org/brainteaser/ontology/schema/Albumin_lower_range
IRI: https://w3id.org/brainteaser/ontology/schema/Albumin_upper_range
IRI: https://w3id.org/brainteaser/ontology/schema/alive
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs-r-tot
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs-tot
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_1
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_10
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_11
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_12
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_2
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_3
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_4
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_5
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_6
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_7
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_8
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_9
IRI: https://w3id.org/brainteaser/ontology/schema/alsfrs_old10
IRI: https://w3id.org/brainteaser/ontology/schema/ambulation
IRI: https://w3id.org/brainteaser/ontology/schema/anti-chickenpox_antibody_test
IRI: https://w3id.org/brainteaser/ontology/schema/anti-Tg
IRI: https://w3id.org/brainteaser/ontology/schema/anti-TgNormal
IRI: https://w3id.org/brainteaser/ontology/schema/AOPabsolute
IRI: https://w3id.org/brainteaser/ontology/schema/AOPrelative
IRI: https://w3id.org/brainteaser/ontology/schema/axial
IRI: https://w3id.org/brainteaser/ontology/schema/before20Years
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAbTMS
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAbTMSNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAlbuminNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAlkalinePhosphatase
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAlkalinePhosphataseNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAMA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAMANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAmylaseNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodANA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodANANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodANCA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodANCANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-cardiolipin
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-cardiolipinNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-DNA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-DNANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-LKM
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-LKMNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-SSA_Ro
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-SSA_RoNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-transglutaminase
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAnti-transglutaminaseNormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAPCA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodAPCANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodASMA
IRI: https://w3id.org/brainteaser/ontology/schema/bloodASMANormal
IRI: https://w3id.org/brainteaser/ontology/schema/bloodBasophil
IRI: https://w3id.org/brainteaser/ontology/schema/bloodBasophilNormal