Improvement to specify more than one archetype on ACTIVITY.arction_archetype_id [Archetype Editor]

2013-01-06 Thread Ian McNicoll
Hi Pablo,

This seems sensible but, to be honest, I have never used this constraint
feature in any real-world applications. My experience has been to leave
most of these options open as it can be very difficult to predict
appropriate future matching archetypes.

Ian


On 5 January 2013 20:09, pablo pazos pazospablo at hotmail.com wrote:

  Hi all,

 When editing an INSTRUCTION archetype, setting the action_archetype_id
 attribute of an ACTIVITY, the AE only gives the possibility of selecting
 one archetype, but this should support more than one archetype using
 regexes as said on the specs (ehr_im.pdf setion 8.3.7).

 A solution could be to support the selection of more than one action
 archetype (using the [...] button, see screen capture here:
 https://plus.google.com/109540968085207927247/posts/f33Hs2rHoto) and
 creating a regex from the selected archetypes like archid1|archid2|archid3

 What do you think?

 --
 Kind regards,
 Ing. Pablo Pazos Guti?rrez
 LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
 Blog: http://informatica-medica.blogspot.com/
 Twitter: http://twitter.com/ppazos http://twitter.com/ppazos

 ___
 openEHR-technical mailing list
 openEHR-technical at lists.openehr.org

 http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org




-- 
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com

Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation  www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
SCIMP Working Group, NHS Scotland
BCS Primary Health Care  www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130106/718e832e/attachment.html


Improvement to specify more than one archetype on ACTIVITY.arction_archetype_id [Archetype Editor]

2013-01-06 Thread pablo pazos

Hi Ian,
I agree for general use archetypes, like the ones published on the CKM, this 
may constraint more that is needed. But for us that build systems things like 
these help us building spec-compliant archetypes to test our systems. With this 
functionality in particular I need to test an UI that can show a form for each 
action_archetype_id on the activity to record the correspondent action. I know 
I can edit the ADL by hand, but that's a practice I try to avoid since it's 
error prone.
This AE constraint (and others, e.g. couldn't create COMPOSITION archetypes 
without slots i.e. the complete structure defined on the same archetype, or the 
imposibility of add constraints to ISM_TRANSITION.transition) makes testing a 
little difficult for us (of course these are drops in a sea of things to test 
on an openEHR system).
Just thinking out loud, if such functionalities could be enabled in the AE, but 
you're affraid that clinical modelers start to use the AE in a wrong way, maybe 
a developers version of the AE could help here. What do you think?
-- 
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez
Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos

From: ian.mcnic...@oceaninformatics.com
Date: Sun, 6 Jan 2013 14:33:41 +0100
Subject: Re: Improvement to specify more than one archetype on  
ACTIVITY.arction_archetype_id [Archetype Editor]
To: openehr-technical at lists.openehr.org

Hi Pablo,
This seems sensible but, to be honest, I have never used this constraint 
feature in any real-world applications. My experience has been to leave most of 
these options open as it can be very difficult to predict appropriate future 
matching archetypes.


Ian

On 5 January 2013 20:09, pablo pazos pazospablo at hotmail.com wrote:






Hi all,
When editing an INSTRUCTION archetype, setting the action_archetype_id 
attribute of an ACTIVITY, the AE only gives the possibility of selecting one 
archetype, but this should support more than one archetype using regexes as 
said on the specs (ehr_im.pdf setion 8.3.7).


A solution could be to support the selection of more than one action archetype 
(using the [...] button, see screen capture here: 
https://plus.google.com/109540968085207927247/posts/f33Hs2rHoto) and creating a 
regex from the selected archetypes like archid1|archid2|archid3



What do you think?

-- 
Kind regards,
Ing. Pablo Pazos Guti?rrez
LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez


Blog: http://informatica-medica.blogspot.com/
Twitter: http://twitter.com/ppazos

  

___

openEHR-technical mailing list

openEHR-technical at lists.openehr.org

http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org




-- 
Dr Ian McNicoll
office +44 (0)1536 414 994
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com



Clinical Modelling Consultant, Ocean Informatics, UK
Director openEHR Foundation  www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL


SCIMP Working Group, NHS Scotland
BCS Primary Health Care  www.phcsg.org



___
openEHR-technical mailing list
openEHR-technical at lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org   
  
-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130106/05e366d3/attachment-0001.html


csingleattribute and existence

2013-01-06 Thread Bert Verhees
Excuse me the following question, maybe I am just looking over the 
answer all the time

What is the use of both together existence and occurences in case of a 
CSingleAtttribute.

And what if both have conflicting information?

For example, existence gives REQUIRED and occurrences gives minOccurs=0

Thanks for a short answer

Bert



csingleattribute and existence

2013-01-06 Thread Thomas Beale

Hi Bert,

existence is a property of CAttribute (multiple or single). It indicates 
if the attribute value (i.e. some object) must exists or can be null.

occurrences is a property of a CObject, and indicates how many instances 
of that object constraint can exist in the data.

It can be used on CObjects under CMultipleAttributes to indicate how 
many instances of each CObject (there can be multiple CObjects, e.g. 
systolic bp, diastolic bp etc, each of which could potentially have more 
than one instance in the data). Commonly, many objects under a 
CMultipleAttribute can only have one or zero occurrences, so occurrences 
is set to {0..1}

Occurrences on an object under a CSingleAttribute can only indicate 0..0 
or 1..1 (based on an original value of 0..1). In theory, occurrences on 
an object under a CSingleAttribute could conflict with existence on the 
CSingleAttribute. Tools can easily check this (and they do).

hope this helps.

- thomas

On 06/01/2013 15:51, Bert Verhees wrote:
 Excuse me the following question, maybe I am just looking over the 
 answer all the time

 What is the use of both together existence and occurences in case of a 
 CSingleAtttribute.

 And what if both have conflicting information?

 For example, existence gives REQUIRED and occurrences gives minOccurs=0

 Thanks for a short answer




csingleattribute and existence

2013-01-06 Thread Bert Verhees
On 01/06/2013 08:44 PM, Thomas Beale wrote:
 Occurrences on an object under a CSingleAttribute can only indicate 
 0..0 or 1..1 (based on an original value of 0..1). In theory, 
 occurrences on an object under a CSingleAttribute could conflict with 
 existence on the CSingleAttribute. Tools can easily check this (and 
 they do).

I formulated the question a bit sloppy, but you picked it well up.

Your answer helps, Now I know that this is an acknowledged risk.
It is not a misunderstanding from my side.

:)

thanks
Bert



csingleattribute and existence

2013-01-06 Thread Bert Verhees
On 01/06/2013 08:44 PM, Thomas Beale wrote:

 Hi Bert,

 existence is a property of CAttribute (multiple or single). It 
 indicates if the attribute value (i.e. some object) must exists or can 
 be null.


How about this:

Since its function in CSingleAttribute is also done by CObject-attribute 
occurences, it could be removed from the CSingleAttribute. This would 
make tools that check this superfluous.

Bert