Archetype has collection of rules. I can add assertions to this collection. Is there a possibility to associate assertion with human readable text?
I only found function which serializes rule statement to adl string form.
Sorry, I only just saw this one. Currently, assertions (‘rules’ in ADL 1.5) have a human readable tag, but there is no other place for putting human readable text. What are your requirements here?
- thomas beale
Hi Thomas,
I would support this. Part of the knowledge around an archetype may well involve complex rules which are not expressable in a formalism, or which involve data points from other archetypes / other complex conditionality. It would be useful to have a place where this could be captured as part of the knowledge gathered.
Ian
Dr Ian McNicoll
office +44 (0)1536 414 994
+44 (0)2032 392 970
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll@oceaninformatics.com
Clinical Modelling Consultant, Ocean Informatics, UK
openEHR Clinical Knowledge Editor www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care www.phcsg.org
2011/5/2 Thomas Beale <thomas.beale@oceaninformatics.com>
the current requirements for annotations (which are implemented in the current ADL 1.5 WB) allow multiple comments on each node in the definition part of an archetype. I have not included an ability to do that for the ‘rules’ (assertions). However, large tracts of design information don’t really belong in the archetype - they belong in an archetype design document in my view…
- thomas
(attachments)
I want to display validation summary in UI for a user who filled data. I validate the entered data with archetype and its asssertions. I don’t want to show formalism in validation summary. Assertions tag is acceptable for me in this case, but there is one small disadvantage that assertions tag is not localizable.
(attachments)
I want to display validation summary in UI for a user who filled data. I validate the entered data with archetype and its asssertions. I don’t want to show formalism in validation summary. Assertions tag is acceptable for me in this case, but there is one small disadvantage that assertions tag is not localizable.
yes, good point. I will have a look at this. For the record, so we don’t forget this issue, can you make a Problem Report at http://www.openehr.org/issues/browse/SPECPR (specify component ADL/AOM).
thanks
- thomas
(attachments)
I filled problem report: http://www.openehr.org/issues/browse/SPECPR-63