Imagine instead the example was using the corresponding AMT concepts (since 
snomed pure doesn't have any concrete domain modelling -- I.e. numeric values).

Then the focus concept would be the AMT amoxycillin Medicinal Product concept 
21415011000036100 and the constraint matches would be MPUUs and TPUUs with 
capsule form and between 500 and 800 mg of amoxycillin as an active ingredient

Michael

Sent from my iPhone

On 30 Sep 2015, at 4:34 PM, Thomas Beale 
<thomas.be...@oceaninformatics.com<mailto:thomas.be...@oceaninformatics.com>> 
wrote:


Hi Michael,

in that case, to what information base or DB could the amoxycillin query be 
applied? What is it for?

thanks

- thomas

On 29/09/2015 23:19, michael.law...@csiro.au<mailto:michael.law...@csiro.au> 
wrote:
Hi Thomas,

These constraints are essentially queries over the snomed definitional content 
(ie the Relationships), not queries over external data (ie not EHRs).  The 
intent is to identify sets of snomed concepts that satisfy the constraint 
criteria. These sets could be subsequently used to join against/filter records 
in an EHR/EMR.

Work is ongoing for a full featured query language to address this larger 
problem, but the expression constraint language can be used to great effect 
when combined with SQL or other database tech to query health records.


_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org<mailto:openEHR-technical@lists.openehr.org>
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to