Multiple parents and max number of nested specialized archetypes?

2007-10-17 Thread Gerard Freriks
Dear Graham,

Is multiple inheritance in the use case you presented, the only  
solution?
I expect it is not.
So why use it.
When 'data integrity' is a recurring issue in several archetypes, re- 
use by inclusion of  a 'data integrity' archetype in an other  
archetypes is a better other solution.

I'm not closely following HL7 Templates.
Are the HL7 Templates a separate and diverging piece of work when  
compared to EN13606-2 or harmonising?
Do both the HL7 Templates and CEN Archetypes share identical  
requiremenets?


Gerard

-- private --
Gerard Freriks, MD
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands

T: +31 252544896
M: +31 620347088
E: gfrer at luna.nl


Those who would give up essential Liberty, to purchase a little  
temporary
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov  
1755





On Oct 16, 2007, at 11:44 PM, Grahame Grieve wrote:

 The use case is relatively simple in concept - allowing multiple
 inheritance would allow me to cross-cut concerns. I could write
 an archetype that only dealt a narrow aspect of an information
 structure, such as data integrity issues, and then use it across
 multiple archetypes, letting them focus on the big picture, not
 the minutiae of data integrity, which is mostly overlooked but
 ubiquitiously present.

-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20071017/d5d147e3/attachment.html


Multiple parents and max number of nested specialized archetypes?

2007-10-17 Thread Thomas Beale
Grahame Grieve wrote:
 At the moment we have not seen any need for multiple inheritance in 
 archetypes.
 

 I see this as very similar to multiple inheritance in objects.
 There is no *need*, but there is useful things that can be done.
 The question is whether the price is justified.

 The use case is relatively simple in concept - allowing multiple
 inheritance would allow me to cross-cut concerns. I could write
 an archetype that only dealt a narrow aspect of an information
 structure, such as data integrity issues, and then use it across
 multiple archetypes, letting them focus on the big picture, not
 the minutiae of data integrity, which is mostly overlooked but
 ubiquitiously present.
   
Hi Grahame,
in openEHR at least, data integrity is not defined or solved by 
archetypes - it is in the reference model.

- thomas





Multiple parents and max number of nested specialized archetypes?

2007-10-17 Thread Heather Leslie
Hi Koray,

A practical example of 'C' that is currently in the archetype repository is
the Histological Diagnosis archetype -
openEHR-EHR-EVALUATION.problem-diagnosis-histological.v1.ad
Problem -- specialised to Diagnosis -- specialised to Histological
Diagnosis - all of which are in the 'Specialisation' field of the Archetype
Editor.

There is no technical limit on the number of specialisations -  but from my
experience so far, it will be uncommon to have to specialise more than
twice.

The modelling required to work out the parent, and then each layer of
children becomes increasingly complex and time-consuming, reconciling back
up to the parent once the lowest level of child requirements has been
captured - I have experimented initially with mindmapping for these
problems.  To date they have been mainly related to principles of inspection
and palpation in cluster archetypes focused on capturing examination for
re-use eg an initial generic inspection cluster, specialised to inspection
of skin, to inspection of a wound or inspection of a rash.  

Regards

Heather
_
Dr Heather Leslie
Director of Clinical Modeling
Ocean Informatics
M +61 418 966 670 (in Australia)
M +44 7722 064 546 (in UK)
Skype - heatherleslie


-Original Message-
From: openehr-technical-bounces at openehr.org [mailto:openehr-technical-
bounces at openehr.org] On Behalf Of Koray Atalag
Sent: Tuesday, 16 October 2007 4:34 PM
To: openehr-technical at openehr.org
Subject: Multiple parents and max number of nested specialized archetypes?

Hi,

I have a question about the referencing of archetypes in specialization.
And also
want to know if there is a limit on the number of specializations of
archetypes.

For example:

A is top level archetype
B is specialization of A
C has to further specialize B
and there is possibility that D also has to further specialize C and so on.

So in theory all childs have to conform to A. But the question is in C
which
archetype will be written in 'specialize' section? A or A  B ? I assume it
is currently
B. But in theory, possible one in a million, a particular specialized
archetype might
conform to multiple parents...In my opinion this is perfectly possible. So
what
happens?

The other question is whether ADL or other limits the number of
specializations.

Best regards,

Koray Atalag, MD, Ph.D.

Freelance consultant and developer
http://koray.pathos-web.org
skype: atalagk



_
___
Fussy? Opinionated? Impossible to please? Perfect.  Join Yahoo!'s user
panel and
lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7


___
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical


__ NOD32 2594 (20071016) Information __

This message was checked by NOD32 antivirus system.
http://www.eset.com




Multiple parents and max number of nested specialized archetypes?

2007-10-17 Thread Thomas Beale
Andrew Patterson wrote:
 I should note that in the next generation of archetypes and tooling,
 archetype 'source' files for specialised archetypes will be
 'differential' in nature - i.e. valid ADL, but containing only added and
 changed items from the parent, just as for subclasses in an
 object-oriented programming environment.
 

 This is excellent news - I was going to launch into a tirade this
 afternoon about how archetype specialisation requires repeating
 the whole parent definition, and how much more robust OO subclassing
 is because of the differential nature! Good thing I held off on my venting.. 
 :)
   
we have actually generated differential form archetypes - we are now 
adjusting some of the parser semantics, since now it has to check up the 
specialisation lineage for codes and a few other things, not just in the 
current archetype. A few weeks away from being solid I would say. Also, 
the ADL workbench now works more like a compiler - you can see what is 
compiled, what is not, and quickly reload anything already compiled.
 A while back there was talk of a confluence wiki being set up
 for storing of some of these thoughts?? Is anything happening in
 that area? I can help out if any admin is required - I just installed Jira
 and Confluence on my own machines..
   
they are both going - as is the new website. All will be available very 
soon. For confluence, we will ust put in some minimal structure to save 
us from complete disorganisation - it will be an open wki. There will be 
plenty of opportunity for experts here to contribute and help shape 
these things - we just want them running in a basic reasonable form so 
people don't hate us when they see it ;-)

- thomas beale