I rewrote the part, I think it is easier to understand now. When someone
will improve it, I am available to explain when something appears to be
unclear.
https://openehr.atlassian.net/wiki/display/spec/Terminology+Querying+for+AQL
Op 13-9-2016 om 7:21 schreef Thomas Beale:
Can everyone who has concrete ideas on ways forward make an effort to
update the wiki page
<https://openehr.atlassian.net/wiki/display/spec/Terminology+Querying+for+AQL>
we created for this, and/or add to the Questions facility
<https://openehr.atlassian.net/wiki/questions>for some of the useful
peripheral questions that have been answered along the way.
The Specifications Editorial Committee will look at these issues in
the near future, but some coherent material would be very helpful.
thanks
- thomas
On 12/09/2016 22:42, Bert Verhees wrote:
Even better, Pablo, it uses SCT, and does not stand in the way of
other terminologies, it is a parallel process which fits inside the
OpenEhr specs.
I tried to explain it before, maybe I did not well explain it. Tell
me if so.
So, you can keep on proceeding as you were already doing, but you can
add something which unlockes the SCT potential.
I explained it on my blog. Please comment on that, maybe you do not
agree, if so, then I want to hear about that.
http://www.bertverhees.nl/archetypes/needed-run-snomed-ct-expression-constraints-openehr-aql/
http://www.bertverhees.nl/archetypes/snomed-ct-expression-constraints-openehr-aql-part-2/
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
