Regarding the readability of the URI's containing SNOMED expressions, one can always consider adding a comment line containing the long (textual) expression format without URI encodings.
Maybe it is also possible to formalize that comment/description in a special ODIN tag. Also other terminology-codings do not explain themselves very well and an explanation/description can be very useful for the reader of plain text ADL I think that SNOMED constraints and post coordinated expressions will soon become unavoidable in an EHR application, and that it is urgent to find a solution for this. Best regards Bert Verhees Op 3 mei 2017 16:45 schreef "Diego Boscá" <[email protected]>: well, nothing stops you for not encoding the query in definition time, most services are ok with that e.g. http://diebosto2.pc.upv.es:8888/SnomedQuery/ws/JSONQuery?query= <404684003:363698007=39057004 2017-05-03 16:31 GMT+02:00 Thomas Beale <[email protected]>: > > On 03/05/2017 13:31, Diego Boscá wrote: > >> Or just use the "Long syntax" as described in point 5.2 from Expression >> Constraint Language, which keeps things readable enough >> http://snomed.info/ecl/descendantOrSelfOf 73211009 |Diabetes mellitus| >> >> > at the very least, a %20 is needed for the spaces, and %7C for the pipes, > i.e. > > http://snomed.info/ecl/descendantOrSelfOf%2073211009%20%7CDi > abetes%20mellitus%7C > > i.e. ... not readable... > > - thomas > >
_______________________________________________ openEHR-technical mailing list [email protected] http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
