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. Gerard Freriks +31 620347088 [email protected] > On 01 Mar 2018, at 15:33, Thomas Beale <[email protected]> wrote: > > > On 01/03/2018 11:05, Seref Arikan wrote: >> Hi Diego, >> >> I'd like to hear how you'd address the requirement via a call to an external >> service. >> > > I don't think it should be that complicated - after all, a call out to a > terminology service is already a call out to a service; terminology is just > one kind of reference knowledge that a query language / engine needs to get > at; we can assume that a units service (as Bert and others were discussing > earlier), lab results reference ranges, drug DB and so on may all be needed > by the query service. > > So I think it mainly comes down to the syntax and programming model of > talking out to such interfaces. We might potentially assume that they are all > based on a common ontology meta-model of some kind (e.g. based on BFO, RO, > IAO etc) in which case a common underlying style could be established. > > - thomas > > > _______________________________________________ > openEHR-technical mailing list > [email protected] > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org _______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
