Architectural analysis of clinical ontologies for pHealth interoperability.
Identifieur interne : 000272 ( PubMed/Corpus ); précédent : 000271; suivant : 000273Architectural analysis of clinical ontologies for pHealth interoperability.
Auteurs : Gustavo A. Uribe ; Diego M. L Pez ; Bernd BlobelSource :
- Studies in health technology and informatics [ 0926-9630 ] ; 2012.
English descriptors
- KwdEn :
- Database Management Systems (organization & administration), Electronic Health Records (organization & administration), Germany, Health Records, Personal, Hospital Information Systems (organization & administration), Information Storage and Retrieval (methods), Medical Record Linkage (methods), Precision Medicine (methods).
- MESH :
- geographic : Germany.
- methods : Information Storage and Retrieval, Medical Record Linkage, Precision Medicine.
- organization & administration : Database Management Systems, Electronic Health Records, Hospital Information Systems.
- Health Records, Personal.
Abstract
Comprehensive interoperability between eHealth/pHealth systems requires properly represented shared knowledge. Formal ontologies allow specifying the semantics of health knowledge representation in a well-defined and unambiguous manner. The objective of this paper is to formally analyze - from a system-theoretical architectural perspective - existing clinical ontologies. The paper defines important ontology requirements for semantically interoperable pHealth/eHealth systems. Then, based on those requirements, 17 criteria are defined and used for analyzing 129 clinical ontologies. Statistical results confirm that most ontologies do not meet the defined criteria. OBO foundry defines a good approach to meet all defined criteria, but it does not cover yet the clinical domain as a whole. SNOMED CT was found the more comprehensive one, despite several restrictions.
PubMed: 22942051
Links to Exploration step
pubmed:22942051Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">Architectural analysis of clinical ontologies for pHealth interoperability.</title>
<author><name sortKey="Uribe, Gustavo A" sort="Uribe, Gustavo A" uniqKey="Uribe G" first="Gustavo A" last="Uribe">Gustavo A. Uribe</name>
<affiliation><nlm:affiliation>Telematics Engineering Research Group, University of Cauca, Colombia.</nlm:affiliation>
</affiliation>
</author>
<author><name sortKey="L Pez, Diego M" sort="L Pez, Diego M" uniqKey="L Pez D" first="Diego M" last="L Pez">Diego M. L Pez</name>
</author>
<author><name sortKey="Blobel, Bernd" sort="Blobel, Bernd" uniqKey="Blobel B" first="Bernd" last="Blobel">Bernd Blobel</name>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">PubMed</idno>
<date when="2012">2012</date>
<idno type="RBID">pubmed:22942051</idno>
<idno type="pmid">22942051</idno>
<idno type="wicri:Area/PubMed/Corpus">000272</idno>
<idno type="wicri:explorRef" wicri:stream="PubMed" wicri:step="Corpus" wicri:corpus="PubMed">000272</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en">Architectural analysis of clinical ontologies for pHealth interoperability.</title>
<author><name sortKey="Uribe, Gustavo A" sort="Uribe, Gustavo A" uniqKey="Uribe G" first="Gustavo A" last="Uribe">Gustavo A. Uribe</name>
<affiliation><nlm:affiliation>Telematics Engineering Research Group, University of Cauca, Colombia.</nlm:affiliation>
</affiliation>
</author>
<author><name sortKey="L Pez, Diego M" sort="L Pez, Diego M" uniqKey="L Pez D" first="Diego M" last="L Pez">Diego M. L Pez</name>
</author>
<author><name sortKey="Blobel, Bernd" sort="Blobel, Bernd" uniqKey="Blobel B" first="Bernd" last="Blobel">Bernd Blobel</name>
</author>
</analytic>
<series><title level="j">Studies in health technology and informatics</title>
<idno type="ISSN">0926-9630</idno>
<imprint><date when="2012" type="published">2012</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>Database Management Systems (organization & administration)</term>
<term>Electronic Health Records (organization & administration)</term>
<term>Germany</term>
<term>Health Records, Personal</term>
<term>Hospital Information Systems (organization & administration)</term>
<term>Information Storage and Retrieval (methods)</term>
<term>Medical Record Linkage (methods)</term>
<term>Precision Medicine (methods)</term>
</keywords>
<keywords scheme="MESH" type="geographic" xml:lang="en"><term>Germany</term>
</keywords>
<keywords scheme="MESH" qualifier="methods" xml:lang="en"><term>Information Storage and Retrieval</term>
<term>Medical Record Linkage</term>
<term>Precision Medicine</term>
</keywords>
<keywords scheme="MESH" qualifier="organization & administration" xml:lang="en"><term>Database Management Systems</term>
<term>Electronic Health Records</term>
<term>Hospital Information Systems</term>
</keywords>
<keywords scheme="MESH" xml:lang="en"><term>Health Records, Personal</term>
</keywords>
</textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en">Comprehensive interoperability between eHealth/pHealth systems requires properly represented shared knowledge. Formal ontologies allow specifying the semantics of health knowledge representation in a well-defined and unambiguous manner. The objective of this paper is to formally analyze - from a system-theoretical architectural perspective - existing clinical ontologies. The paper defines important ontology requirements for semantically interoperable pHealth/eHealth systems. Then, based on those requirements, 17 criteria are defined and used for analyzing 129 clinical ontologies. Statistical results confirm that most ontologies do not meet the defined criteria. OBO foundry defines a good approach to meet all defined criteria, but it does not cover yet the clinical domain as a whole. SNOMED CT was found the more comprehensive one, despite several restrictions.</div>
</front>
</TEI>
<pubmed><MedlineCitation Owner="NLM" Status="MEDLINE"><PMID Version="1">22942051</PMID>
<DateCreated><Year>2012</Year>
<Month>09</Month>
<Day>03</Day>
</DateCreated>
<DateCompleted><Year>2012</Year>
<Month>09</Month>
<Day>27</Day>
</DateCompleted>
<DateRevised><Year>2015</Year>
<Month>11</Month>
<Day>19</Day>
</DateRevised>
<Article PubModel="Print"><Journal><ISSN IssnType="Print">0926-9630</ISSN>
<JournalIssue CitedMedium="Print"><Volume>177</Volume>
<PubDate><Year>2012</Year>
</PubDate>
</JournalIssue>
<Title>Studies in health technology and informatics</Title>
<ISOAbbreviation>Stud Health Technol Inform</ISOAbbreviation>
</Journal>
<ArticleTitle>Architectural analysis of clinical ontologies for pHealth interoperability.</ArticleTitle>
<Pagination><MedlinePgn>176-82</MedlinePgn>
</Pagination>
<Abstract><AbstractText>Comprehensive interoperability between eHealth/pHealth systems requires properly represented shared knowledge. Formal ontologies allow specifying the semantics of health knowledge representation in a well-defined and unambiguous manner. The objective of this paper is to formally analyze - from a system-theoretical architectural perspective - existing clinical ontologies. The paper defines important ontology requirements for semantically interoperable pHealth/eHealth systems. Then, based on those requirements, 17 criteria are defined and used for analyzing 129 clinical ontologies. Statistical results confirm that most ontologies do not meet the defined criteria. OBO foundry defines a good approach to meet all defined criteria, but it does not cover yet the clinical domain as a whole. SNOMED CT was found the more comprehensive one, despite several restrictions.</AbstractText>
</Abstract>
<AuthorList CompleteYN="Y"><Author ValidYN="Y"><LastName>Uribe</LastName>
<ForeName>Gustavo A</ForeName>
<Initials>GA</Initials>
<AffiliationInfo><Affiliation>Telematics Engineering Research Group, University of Cauca, Colombia.</Affiliation>
</AffiliationInfo>
</Author>
<Author ValidYN="Y"><LastName>López</LastName>
<ForeName>Diego M</ForeName>
<Initials>DM</Initials>
</Author>
<Author ValidYN="Y"><LastName>Blobel</LastName>
<ForeName>Bernd</ForeName>
<Initials>B</Initials>
</Author>
</AuthorList>
<Language>eng</Language>
<PublicationTypeList><PublicationType UI="D016428">Journal Article</PublicationType>
<PublicationType UI="D013485">Research Support, Non-U.S. Gov't</PublicationType>
</PublicationTypeList>
</Article>
<MedlineJournalInfo><Country>Netherlands</Country>
<MedlineTA>Stud Health Technol Inform</MedlineTA>
<NlmUniqueID>9214582</NlmUniqueID>
<ISSNLinking>0926-9630</ISSNLinking>
</MedlineJournalInfo>
<CitationSubset>T</CitationSubset>
<MeshHeadingList><MeshHeading><DescriptorName MajorTopicYN="N" UI="D003628">Database Management Systems</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000458">organization & administration</QualifierName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" UI="D057286">Electronic Health Records</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000458">organization & administration</QualifierName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" Type="Geographic" UI="D005858">Germany</DescriptorName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="Y" UI="D055991">Health Records, Personal</DescriptorName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" UI="D006751">Hospital Information Systems</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000458">organization & administration</QualifierName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" UI="D016247">Information Storage and Retrieval</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000379">methods</QualifierName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" UI="D008498">Medical Record Linkage</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000379">methods</QualifierName>
</MeshHeading>
<MeshHeading><DescriptorName MajorTopicYN="N" UI="D057285">Precision Medicine</DescriptorName>
<QualifierName MajorTopicYN="Y" UI="Q000379">methods</QualifierName>
</MeshHeading>
</MeshHeadingList>
</MedlineCitation>
<PubmedData><History><PubMedPubDate PubStatus="entrez"><Year>2012</Year>
<Month>9</Month>
<Day>4</Day>
<Hour>6</Hour>
<Minute>0</Minute>
</PubMedPubDate>
<PubMedPubDate PubStatus="pubmed"><Year>2012</Year>
<Month>9</Month>
<Day>4</Day>
<Hour>6</Hour>
<Minute>0</Minute>
</PubMedPubDate>
<PubMedPubDate PubStatus="medline"><Year>2012</Year>
<Month>9</Month>
<Day>28</Day>
<Hour>6</Hour>
<Minute>0</Minute>
</PubMedPubDate>
</History>
<PublicationStatus>ppublish</PublicationStatus>
<ArticleIdList><ArticleId IdType="pubmed">22942051</ArticleId>
</ArticleIdList>
</PubmedData>
</pubmed>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/TelematiV1/Data/PubMed/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000272 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/PubMed/Corpus/biblio.hfd -nk 000272 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= TelematiV1 |flux= PubMed |étape= Corpus |type= RBID |clé= pubmed:22942051 |texte= Architectural analysis of clinical ontologies for pHealth interoperability. }}
Pour générer des pages wiki
HfdIndexSelect -h $EXPLOR_AREA/Data/PubMed/Corpus/RBID.i -Sk "pubmed:22942051" \ | HfdSelect -Kh $EXPLOR_AREA/Data/PubMed/Corpus/biblio.hfd \ | NlmPubMed2Wicri -a TelematiV1
![]() | This area was generated with Dilib version V0.6.31. | ![]() |