Sorry - didn't mean to be cryptic.
BFO = basic formal ontology - probably best mainstream reference is the
book, see here on Amazon
<https://www.amazon.co.uk/Building-Ontologies-Basic-Formal-Ontology/dp/0262527812>
RO = relations ontology - an ontology of possible relationships between
upper-level biomedical entities, including part-of, develops-from etc.
OBO ref <http://obofoundry.org/ontology/ro.html>.
IAO = Information Artefact Ontology. OBO ref
<http://obofoundry.org/ontology/iao.html>.
I'm not saying that the concrete representation of reference data has to
be an ontology (e.g. as produced by Protege), but reference information
('knowledge') is unavoidably based on an ontological viewpoint in the
same way that the contents of SNOMED CT are (should be). Drug data for
example takes the form of facts about drugs such as constituents,
interactions; units information is /should be based on an ontology of
measurement concepts (which is not very well represented in OBO right
now - as far as I can determine, people think it should be in IAO, but I
think that is incorrect. Practically, UCUM serves pretty well.)
- thomas
On 01/03/2018 14:50, GF wrote:
The metadata describing these interfaces with these services can be constructed
using archetypes resulting in Template/Compositions.
Thomas: I know what BFO is.
But what stand RO ans IAO for?
Why must they be based on an ontology?
In the case of signalling/normal values, it will be simple: item-ID, Low value
plus units, High value plus units, date of publication.
--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Team, Intermountain Healthcare
<https://intermountainhealthcare.org/>
Management Board, Specifications Program Lead, openEHR Foundation
<http://www.openehr.org>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org/category/6044>
Health IT blog <http://wolandscat.net/> | Culture blog
<http://wolandsothercat.net/>
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
