openEHR and terminology servers

Technical (archive)
21

Works fine in Firefox, does not work in Chrome, both in Linux.

(maybe that helps analyzing the problem)

22

By the way, looks like a very interesting software, but I must study it better. Is there some documentation also?

Bert

23

I would argue the FHIR provides such an API. It also includes the SNOMED Expression Constraint Language (ECL) as part of the spec. This is why we chose it as the basis I for our terminology server, Ontoserver, which is now the basis for Australia's National Clinical Terminology Service (www.healthterminologies.gov.au)

We also built a little UI to demonstrate use of ECL through FHIR at https://ontoserver.csiro.au/shrimp-fhir/ecl.html click on the help link for a range of simple and more complex query examples.

Michael

24

Seems a problem with language settings/preferences to Dutch in browser. It also appears on Mac.

So, some work to do :wink:

Bert

25

Hi Bert,

Made a change that I believe it should have fixed the issue. Can you test it? :slight_smile:

Very nice subsumption testing, I think just as I learned it last year in the implementation course from IHTSDO.

I could check it in detail, but I trust it looks good.

Thanks for sharing

Bert

26

Hi Bert,

I think the idea of the CTS2 is to define an abstraction layer over many terminologies to have a common way to access them event if they have different features or internal structure.

I’m sure others here will know more about it.

ref http://www.omg.org/spec/CTS2/1.2/

Cheers,

Pablo.

27

Hi Pablo,

The FHIR terminology service has a similar aim and has been described as “CTS2-lite”. It is much more implementer orientated than CTS2 but, of course, lacks many of the aspects directed at the authoring community.

Ian

28

yes. that’s deliberate. We’ve always said that the requirements for authoring are outside our scope. But that may change in the version after the one we’ll publish in a few months

Grahame

29

Thanks Pablo, I never heard about it. A common interface to several terminologies seems useful for implementing a simple access layer .

I will read about it later to see how the good intentions reflect in the results

Bert