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 On Tue, Dec 6, 2016 at 5:31 AM, Ian McNicoll <i...@freshehr.com> wrote: > 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 > > Dr Ian McNicoll > mobile +44 (0)775 209 7859 <+44%207752%20097859> > office +44 (0)1536 414994 <+44%201536%20414994> > skype: ianmcnicoll > email: i...@freshehr.com > twitter: @ianmcnicoll > > > Co-Chair, openEHR Foundation ian.mcnic...@openehr.org > Director, freshEHR Clinical Informatics Ltd. > Director, HANDIHealth CIC > Hon. Senior Research Associate, CHIME, UCL > > On 5 December 2016 at 19:23, Pablo Pazos <pablo.pa...@cabolabs.com> wrote: > >> 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. >> >> On Sun, Dec 4, 2016 at 5:37 AM, Bert Verhees <bert.verh...@rosa.nl> >> wrote: >> >>> A Rest service for terminology needs to be defined per terminology, >>> because they are all of different features. >>> >>> There is one good source of inspiration for a SNOMED terminology. >>> https://dev-term.ihtsdotools.org/snowowl/snomed-ct/v2/ >>> >>> I say, source of inspiration, because not everybody needs editing >>> capacity, most use-cases just want to query. >>> And the swagger/openapi is not optimal, there are some errors in the >>> data-models on technical level, but these are very few. >>> >>> When you look at it, and leave out all the branch-things (which are for >>> editing and versioning), then you have a decent interface for a SNOMED >>> service. >>> An then, it is also very obvious (afterwards) and it reflects good >>> thinking in its simplicity. >>> >>> As you may know, there are mappings for SNOMED and LOINC, ICDxx and >>> other terminologies (also local), and others, on the way, or already >>> finished, so this interface can also used for these mappings which gives in >>> this way a route to query other terminologies. >>> >>> good luck >>> Bert Verhees >>> >>> >>> >>> On 04-12-16 01:53, Pablo Pazos wrote: >>> >>> Hi Daniel, >>> >>> Did your team publish any articles about the demonstration? I'm >>> interested in the technical aspects of querying expansion of results. >>> >>> Thanks! >>> >>> On Fri, Dec 2, 2016 at 10:01 AM, Daniel Karlsson <daniel.karls...@liu.se >>> > wrote: >>> >>>> Hi All, >>>> >>>> so I'll start: >>>> At Linköping University we did a demonstrator in 2012 using a homebrew >>>> REST interface to an expression repository based on the SNOMED CT query >>>> language at the time. The demonstrator showed querying over EHR content >>>> including both AQL and the SNOMED CT query language. The terminology server >>>> per default did expansion of results of the SNOMED CT queries, i.e. it >>>> returned a set of SCTID:s+expression id:s. The aim of this experiment was >>>> to show that some very complex quality indicators could be expressed as >>>> queries on a structured health record. >>>> >>>> /Daniel >>>> >>>> >>>> On 2016-12-02 11:33, Grahame Grieve wrote: >>>> >>>> hi Daniel >>>> >>>> I'll listen to this discussion with interest. I expect that the answer >>>> will be: same functional needs as already covered by FHIR terminology >>>> services, but there's some additional information features that are needed >>>> to enable seamless integration. >>>> >>>> Grahame >>>> >>>> >>>> On Fri, Dec 2, 2016 at 7:50 PM, Daniel Karlsson <daniel.karls...@liu.se >>>> > 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 <%2B46%20708350109>, Skype: imt_danka, Hangout: >>>>> daniel.e.karls...@gmail.com >>>>> >>>>> >>>>> _______________________________________________ >>>>> openEHR-technical mailing list >>>>> openEHR-technical@lists.openehr.org >>>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >>>>> lists.openehr.org >>>>> >>>> >>>> >>>> >>>> -- >>>> ----- >>>> http://www.healthintersections.com.au / grah...@healthintersections.co >>>> m.au / +61 411 867 065 <+61%20411%20867%20065> >>>> >>>> >>>> -- >>>> Daniel Karlsson, PhD, sr lecturer >>>> Department of Biomedical Engineering/Health informatics >>>> Linköping university >>>> SE-58185 Linköping >>>> Sweden >>>> Ph. +46 708350109 <+46%2070%20835%2001%2009>, Skype: imt_danka, Hangout: >>>> daniel.e.karls...@gmail.com >>>> >>>> >>>> _______________________________________________ >>>> openEHR-technical mailing list >>>> openEHR-technical@lists.openehr.org >>>> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >>>> lists.openehr.org >>>> >>> >>> >>> >>> -- >>> Ing. Pablo Pazos Gutiérrez >>> Cel:(00598) 99 043 145 <099%20043%20145> >>> Skype: cabolabs >>> <http://cabolabs.com/> >>> http://www.cabolabs.com >>> pablo.pa...@cabolabs.com >>> >>> >>> _______________________________________________ >>> openEHR-technical mailing >>> listopenEHR-technical@lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org >>> >>> >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> openEHR-technical@lists.openehr.org >>> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >>> lists.openehr.org >>> >> >> >> >> -- >> Ing. Pablo Pazos Gutiérrez >> Cel:(00598) 99 043 145 <+598%2099%20043%20145> >> Skype: cabolabs >> <http://cabolabs.com/> >> http://www.cabolabs.com >> pablo.pa...@cabolabs.com >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical@lists.openehr.org >> http://lists.openehr.org/mailman/listinfo/openehr-technical_ >> lists.openehr.org >> > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical@lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr- > technical_lists.openehr.org > -- ----- http://www.healthintersections.com.au / grah...@healthintersections.com.au / +61 411 867 065
_______________________________________________ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
