Hi Tom,
Is the intention that the new data type TERMINOLOGY_CODE also can contain a
post-coordinated code so it, for example, can contain a expression in SNOMED CT
compositional grammar? (See
www.snomed.org/tig?t=rfg_expression_scg<http://www.snomed.org/tig?t=rfg_expression_scg>
for more details about SNOMED CT compositional grammar.)
Greetings
Mikael
From: openEHR-technical [mailto:[email protected]] On
Behalf Of Thomas Beale
Sent: den 24 april 2013 19:03
To: Openehr-Technical
Subject: New ADL/AOM proposals to solve some old problems
In openEHR we use custom syntax in archetypes to express ordinal constraints,
quantity constraints and coded text constraints - i..e constraints on what are
probably the most ubiquitous data types in health.
I have been mulling over feedback from previous debates here and in CIMI about
the 'undesirability' of this syntax.
I have posted some new ideas on how to solve this
here<http://www.openehr.org/wiki/display/spec/ADL+1.5+Power+Syntax+Proposals>.
The executive summary is:
* let's treat 'code' as a built in type, like a Date or a Uri; this then
makes an AOM type that constrains this trivial;
* ADL can be augmented in a generic way to enable tuples to be constrained,
which would better solve the Quantity constraint problem
* The Ordinal constraint syntax would be replaced by a combination of both
of the above.
Feedback welcome.
- thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130429/c269ec58/attachment.html>
