Hi Danial,

Very timely questions for us at Operon - we are working with
terminology service providers to provide tight integration with
openEHR services.

 We definitely need to be able to expand valuesets in the context of
an openEHR query

e.g Give me any patients with a problem/diagnosis of diabetes mellitus
type 2 or children. i.e is_a relationships

We need to be able to channel this via AQL or other opeNEHR query languages.

We need to be able to manage and query over termsets/resultsets.

I'm not so sure about the need for more complex queries over other
relationships / SNOMED concept model right now.

We definitely need some sort of vendor-agnostic API against which the
majority of terminlogy service calls can be run. The FHIR service
looks 'good enough' to me although I don't pretend to be an expert.

Ian



Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: [email protected]
twitter: @ianmcnicoll


Co-Chair, openEHR Foundation [email protected]
Director, freshEHR Clinical Informatics Ltd.
Director, HANDIHealth CIC
Hon. Senior Research Associate, CHIME, UCL


On 2 December 2016 at 08:50, Daniel Karlsson <[email protected]> wrote:
> Dear All,
>
> while thinking about terminology server requirements for openEHR systems
> I would like to ask all openEHR implementers about experiences of
> different solutions. Are there any experiences of using openEHR systems
> with e.g. the FHIR terminology services, CTS2, Ocean TQL, homebrew, etc?
> What are the use cases when the terminology servers are used (e.g.
> design time, data entry, querying, etc.)? What are the "terminological
> queries" that are used/needed (e.g. subsumption testing, subset
> membership, subset expansion, etc.)?
>
> Thanks,
> Daniel
>
> --
>
> Daniel Karlsson, PhD, sr lecturer
> Department of Biomedical Engineering/Health informatics
> Linköping university
> SE-58185 Linköping
> Sweden
> Ph. +46 708350109, Skype: imt_danka, Hangout: [email protected]
>
>
> _______________________________________________
> 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

Reply via email to