I think this thread has gone a little off the rails.

There are predefined (by FHIR) URIs for value sets that are defined just as 
descendants of a single concept, or members of a reference set.

For an enumeration of concepts and/or a snomed ECL expression, then you can use 
a Fhir ValueSet and give it a URI.  ValueSets also generalise beyond just 
SNOMED (LOINC for example).

Furthermore, there are existing tools to expand them to the set of member 
concepts, you can include metadata, manage versions etc.  This is much more 
than you get just by encoding ECL in a URI.

In case anyone wants to play with ECL expressions and their evaluation you can 
go here for an interactive page:

Also, some brief documentation and click-through examples here



Sent from my iPhone

On 3 May 2017, at 9:08 pm, Diego Bosc? 
<yamp...@gmail.com<mailto:yamp...@gmail.com>> wrote:

Seems like the only way right now is creating refsets and referencing them with 
standard URIs...

2017-05-03 13:02 GMT+02:00 Bert Verhees 
On 03-05-17 12:53, Thomas Beale wrote:
On 03/05/2017 11:40, Bert Verhees wrote:
On 03-05-17 12:36, Thomas Beale wrote:

The only missing part, now that I look at the SNOMED Compositional 
Grammar<https://confluence.ihtsdotools.org/display/DOCSCG> and Expression 
Constraint Language<https://confluence.ihtsdotools.org/display/DOCECL> specs, 
is how to create a URI (which is the type of a term binding in 
 from a post-coordinated expression or constraint expression. This should be 
trivial, but I don't see where SNOMED has specified it.

True, I was looking for that also, a few days ago. I don't have time to read 
much now, but there is a document on the SNOMED site on URI's, maybe it is in 
I can take a look later or look in my documentation, I have course materials. I 
come back to this tomorrow if not someone else already has.

The URI spec is 
but it doesn't address URIs for expressions either.

(All the SNOMED language specs appear to be 
 these days - nice and convenient, and also nicely published. We probably 
should go back to linking to them somewhere on the openEHR site).

I checked my course materials from last year, lucky I found it quickly, there 
is not any mentioning of URI's for expressions, so I guess it does not yet 



openEHR-technical mailing list


[VeraTech for Health SL]<https://htmlsig.com/t/000001C268PZ>

[Twitter] <https://htmlsig.com/t/000001C47QQH>  [LinkedIn]  
<https://htmlsig.com/t/000001C4DPJG>  [Maps]  


Diego Bosc? Tom?s / Senior developer

VeraTech for Health SL
+34 961071863<tel:+34%20961%2007%2018%2063> / +34 

Su direcci?n de correo electr?nico junto a sus datos personales forman parte de 
un fichero titularidad de VeraTech for Health SL (CIF B98309511) cuya finalidad 
es la de mantener el contacto con usted. Conforme a La Ley Org?nica 15/1999, 
usted puede ejercitar sus derechos de acceso, rectificaci?n, cancelaci?n y, en 
su caso oposici?n, enviando una solicitud por escrito a 

openEHR-technical mailing list
openEHR-technical mailing list

Reply via email to