Re: Terminology bindings ... again

2018-03-12 Thread Pablo Pazos
Thanks Mikael, that's what I suspected. I'm seeing a convergence in terms of clinical terminology towards SNOMED CT. On Mon, Mar 12, 2018 at 3:57 AM, Mikael Nyström wrote: > Hi, > > > > Yes, it is correct that expressions include single code binding. Those > kinds of

Re: Terminology bindings ... again

2018-03-12 Thread Diego Boscá
Probably we should have a look at https://confluence.ihtsdotools.org/display/SLPG/SNOMED+CT+URI+Standard FHIR also uses the same base uri, but builds the URI using a custom syntax such as http://snomed.info/sct?fhir_vs=isa/138875005 But looking at the Snomed URI standard I assume they will just go

Re: Terminology bindings ... again

2018-03-12 Thread GF
The scope of LOINC is NOT the same as the scope of SNOMED. Gerard Freriks +31 620347088 gf...@luna.nl Kattensingel 20 2801 CA Gouda the Netherlands > On 12 Mar 2018, at 08:39, Mikael Nyström wrote: > > Hi, > > I do that too. It seems like more and more people are

SV: Terminology bindings ... again

2018-03-12 Thread Mikael Nyström
Hi, It depends on what you mean by scope … There is an agreement between SNOMED International and Regenstrief Institute to not batch include concepts that directly match LOINC codes in SNOMED CT. However, in general SNOMED CT can have concepts that represent the same or similar ideas as LOINC

Re: Templates for application form development

2018-03-12 Thread Pablo Pazos
Hi all, I manage to translate / update part of the work we did some years ago in terms of UI definition and generation for the openEHR stack. Here is the doc, feedback is very welcome! https://docs.google.com/document/d/13rJMLoW-2tJtl9ejKAIkJbWe-_T9H6UMsGNkiZoU7Iw/edit?usp=sharing On Wed,

SV: Terminology bindings ... again

2018-03-12 Thread Mikael Nyström
Hi, I do that too. It seems like more and more people are moving away from the position that SNOMED CT is complex and expensive to a position that SNOMED CT is manageable and an affordable way of getting rid of local terminologies and add value. Regards

SV: Terminology bindings ... again

2018-03-12 Thread Mikael Nyström
Hi, Yes, it is correct that expressions include single code binding. Those kinds of bindings are just the simplest variants of expressions. :-) I think that in a few years’ time nearly all implementations of SNOMED CT not only implement the international version, but also one are a few

Re: Templates for application form development

2018-03-12 Thread Thomas Beale
Pablo, Good work - I've included a reference to this doc in the original wiki page , and added a few ideas about how to use it. It is very close to what I was thinking of. - thomas On 12/03/2018 07:31,

Re: Terminology bindings ... again

2018-03-12 Thread Michael.Lawley
FHIR also supports the expression language in the URL with, for example, http://snomed.info/sct?fhir_vs=ecl/<<123464:474748=<<84848484 But note that these URIs (the above and your isa/ one below) are defined by HL7 FHIR, not SNOMED International. Technically

Re: Terminology bindings ... again

2018-03-12 Thread Michael.Lawley
Yes, it wasn’t part of STU3 (aka 3.0.1) but is now in the R4 spec - see http://build.fhir.org/snomedct.html#implicit Michael Sent from my iPhone On 12 Mar 2018, at 8:39 pm, Diego Boscá > wrote:https://www.hl7.org/fhir/snomedct.html#implicit

[Troll] Terminology bindings ... again

2018-03-12 Thread Philippe Ameline
Le 12/03/2018 à 01:38, Pablo Pazos a écrit : > IMO we should focus on SNOMED. Hi, There is currently some kind of interesting momentum against Snomed. It can come from governments that refuse to pay for it (current mood in France), of from practitioners who, after having been asked by their

Re: Templates for application form development - should probably explain our EtherCIS/QEWDjs/PulseTile stack here

2018-03-12 Thread Tony Shannon
ok thanks Tom T On 12 March 2018 at 13:46, Thomas Beale wrote: > Tony, > this post was very useful; I've referenced it and copied bits of it to the > wiki > page > > . > > - thomas

SV: [Troll] Terminology bindings ... again

2018-03-12 Thread Mikael Nyström
Hi, Have anybody ever heard about a health-it-project that hadn't a smaller or larger group of sceptic people that try to build momentum against the project? :-) For SNOMED CT the trend at least seems to be that fewer and fewer people belongs to the sceptic group, and about half of the

Re: Templates for application form development - should probably explain our EtherCIS/QEWDjs/PulseTile stack here

2018-03-12 Thread Thomas Beale
Tony, this post was very useful; I've referenced it and copied bits of it to the wiki page . - thomas On 18/02/2018 18:34, Tony Shannon wrote: Hi all, This might be a useful time to briefly explain why

Re: [Troll] Terminology bindings ... again

2018-03-12 Thread Pablo Pazos
In Latin America is all the contrary, more countries are becoming SNOMED members and adopting SNOMED at the govt level. On Mon, Mar 12, 2018 at 10:18 AM, Philippe Ameline wrote: > Le 12/03/2018 à 01:38, Pablo Pazos a écrit : > > > IMO we should focus on SNOMED. > >

Re: SV: [Troll] Terminology bindings ... again

2018-03-12 Thread Birger Haarbrandt
Please never underestimate the Germans... Am 12.03.2018 um 14:54 schrieb Mikael Nyström: Hi, Have anybody ever heard about a health-it-project that hadn't a smaller or larger group of sceptic people that try to build momentum against the project? :-) For SNOMED CT the trend at least seems

Re: Templates for application form development

2018-03-12 Thread Erik Sundvall
Hi! I have also updated the https://openehr.atlassian.net/wiki/spaces/spec/pages/175276035/Application+Data-sets wikipage to include - references to some previous GUI discussions and - Region Östergötlands current use case and initial Ethercis-OPT-introspector+Angular-based design plans

Re: Templates for application form development

2018-03-12 Thread Pablo Pazos
Thanks Thomas, I added a paragraph about the UI generation modes at the end, I forgot to mention that yesterday. On Mon, Mar 12, 2018 at 9:40 AM, Thomas Beale wrote: > Pablo, > > Good work - I've included a reference to this doc in the original wiki > page >