Coder Social home page Coder Social logo

ontoneo's Introduction

Obstetric and Neonatal Ontology

The Obstetric and Neonatal Ontology is a structured controlled vocabulary to provide a representation of the data from electronic health records (EHRs) involved in the care of the pregnant woman, and of her baby.

This ontology has been created to provide a consensus representation of salient electronic health record (EHR) data in this medical specialties, in order to serve EHR interoperability of the associated data and information systems. Interoperability of EHR data in woman and child care is important to ensuring continuity of care during the prenatal and postnatal periods for both mother and child.

OntONeo is a collection of entities related to anatomy, embryology and medical specialties related to care of woman and child (gynecology, obstetric, pediatric, neonatology).

The current version of OntONeo is version 1.6 deployed on 04-29-2021.

The previous versions are located at releases folder according to the version deployed date.

There is a Google Group for discussing the project at http://groups.google.com/group/ontoneo-discuss. Click the "Apply for Membership" link to join.

ontoneo's People

Contributors

fernandafarinelli avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

ontoneo's Issues

'role in human social processes' (OMRSE:00000024) has been deprecated and replaced

In the future we plan on reaching out to developers of ontologies that import our classes to get their input prior to making such changes, but we have replaced this class with another one with the same label: 'role in human social processes' (OMRSE:00002072). The only change to the class was to the subClassOf axiom, which we changed from "inheres-in only human or organization" to "inhere-in only 'material entity'."

Possible problems with import statements

In ontoneo.owl (any probably elsewhere) these imports use uppercase "BFO" and "FMA":

    <owl:imports rdf:resource="http://purl.obolibrary.org/obo/ontoneo/import/BFO_import.owl"/>
    <owl:imports rdf:resource="http://purl.obolibrary.org/obo/ontoneo/import/FMA_import.owl"/>

https://github.com/ontoneo-project/Ontoneo/blob/master/ontoneo.owl#L24-L25

but the actual file names are consistently lowercase: https://github.com/ontoneo-project/Ontoneo/tree/master/import

The names in the imports should exactly match the file names, or the import might fail.

In general, it's best practise for the release version of your ontology to merge together all imports, so there are no owl:imports left to cause problems.

'human parturition procedure': subclass does not categorically match axiom

'human parturition procedure' is the superclass of 'caesearean section' (implying that they are both processes), but 'human parturition procedure' is given the axiom:

realizes some (concretizes some
('caesarean section' or 'human parturition'))

which implies 'caesarean section' is a plan specification.

OBO Foundry: Normalise PURLs?

Hello! In our great OBO foundry ontology QC cleaning effort, we noticed that ONTONEO is using irregular PURLs.

There are, at least, two different IRI conventions in ONTONEO:
http://purl.obolibrary.org/obo/ontoneo/ONTONEO_1000002
http://purl.bioontology.org/OntONeo/ONTONEO_00000066

The one recognised by the OBO foundry would be:
http://purl.obolibrary.org/obo/ONTONEO_1000002

I know this is a long-shot, but would you be willing to normalise the ONTONEO IRIs in this way to make it easier to use with OBO Foundry tooling?

Create OSRD of iteration 1

Define the scope of the iteration and create the requirements specification document of the iteration 1.

Syntax error in ontoneo.owl

I tried to open the main ontoneo.owl file in Protege, but it failed due to a syntax error on this line:

<owl:versionIRI rdf:datatype="&xsd;string">v1.2</owl:versionInfo>

The start and end XML tags must match: owl:versionIRI.

Ontology uses rdf:comment instead of rdfs:comment

There are multiple occurrences in the OWL source file where rdf:comment is used instead of rdfs:comment, e.g., this line.

This caused an issue with our application (BioPortal), which hosts the ontology at this URL:

http://bioportal.bioontology.org/ontologies/ONTONEO

We were unable to load the ontology into our triplestore with errors like the following:

rdf:comment is an unknown RDF namespaced element

We modified all occurrences of rdf:comment to rdfs:comment and were able to load the ontology successfully, as detailed in this issue.

For the moment, we've disabled the functionality that looks for new versions of your ontology at the designated pull URL, pending modification of the rdf:comment tags.

Import only selected subsets of other ontologies

The import directory contains a number of subsets from other ontologies, which is good practise. However the main ontoneo.owl file is importing the full versions of those ontologies, not the subsets.

One solution is to have a partial entry in your PURL configuration that will redirect a directory of files. Here is an example from DOID: https://github.com/OBOFoundry/purl.obolibrary.org/blob/master/config/doid.yml In their OWL file they use those PURLs to redirect http://purl.obolibrary.org/obo/doid/imports/uberon_import.owl to their subsets in GitHub.

To make these imports work when doing local development, they use a catalog file that tells Protege to use the local versions. See the first several lines of this file: https://github.com/DiseaseOntology/HumanDiseaseOntology/blob/master/src/ontology/catalog-v001.xml

I wish this was easier, but it's the best way to get the behaviour that (I think) you want.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.