Hi Bert,
I hope to get back on the spec in the next couple of weeks. With respect
to your specific question below, can you be a bit more precise? There
are ways to express this kind of thing, but we need to be clear on
distinguishing references to:
* elements in the same archetype - as in a rule like:
o /path/to/systolic/pressure/value >
/path/to/diastolic/pressure/value
* elements in data elsewhere in the same EHR like:
o $date_of_birth:ISO8601_DATE ::= query("ehr", "date_of_birth")
o this is still being finalised, so don't depend on it;
however it is the left hand side that matters, i.e.
$date_of_birth
* environmental values, like
o $current_date
o $current_time
Some of this is still being finalised, but the general syntax will look
like Xpath and the object model will be what you would expect from that.
- thomas
On 10/03/2011 15:48, Bert Verhees wrote:
> Hi,
>
> I am sorry, but I am to busy to read all the discussions on future
> ADL-versions.
> So, now I have a small question, which possible is already explained,
>
> Is it possible to write conditional constraints in future ADL?
>
> The question is about implementing care-protocol into an archetype.
>
> For example, if blood-pressure is> 200, force to use another entry, for
> example also look at heartbeat
>
> Is there any idea when this new specifications will be in final version?
>
> Thanks
> Bert
>
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
*
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110316/11d179c4/attachment.html>
