Multiple archetypes in a single concept as a way to create an archetype collaborative

2011-08-03 Thread Abbas Shojaee
Hi Joaquin

OpenEHR  is a language and ontology neutral, standard. Archetype class is
ready for translations via its ancestor: AUTHORED_RESOURCE that has
unbounded instances of TRANSLATION_DETAILS. Several phrases (words)
pertaining to a sole concept can be implemented via Terminology package that
helps with assigning terminologies of any kind to map to Archetype parts.

Regards


On Tue, Aug 2, 2011 at 9:59 PM, Blaya, Joaquin Andres 
joaquin_blaya at hms.harvard.edu wrote:

  Hi,
 Apologies in advance if this is the incorrect email list for this topic,
 but I thought it was the most relevant.

 I'm a member of OpenMRS and there we are discussion a way to have users
 share the concepts (a limited form of an archetype) created in their
 systems. This means that for a single concept you could have many concepts
 from different implementations. This could be because of language or because
 different words refer to the same concept. For example, Gender in the US
 might be Sex in another country and Sexo in spanish.

 I would like to see if OpenEHR has solved this problem so that perhaps
 OpenMRS could begin to use archetypes.

 Thanks

 Joaquin



 -Original Message-
 *From:* openehr-technical-request at openehr.org [
 openehr-technical-request at openehr.org]
 *Received:* Monday, 01 Aug 2011, 18:27
 *To:* openehr-technical at openehr.org [openehr-technical at openehr.org]
 *Subject:* openEHR-technical Digest, Vol 61, Issue 1

 Send openEHR-technical mailing list submissions to
 openehr-technical at openehr.org

 To subscribe or unsubscribe via the World Wide Web, visit
 http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
 or, via email, send a message with subject or body 'help' to
 openehr-technical-request at openehr.org

 You can reach the person managing the list at
 openehr-technical-owner at openehr.org

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of openEHR-technical digest...


 Today's Topics:

1. Multiple values in C_DV_ORDINAL constraints (Ian McNicoll)
2. Re: Multiple values in C_DV_ORDINAL constraints (Thomas Beale)
3. AUTO: Amnon Shabo is out of the office. (returning
   11/08/2011) (Amnon Shabo)
4. Re: Multiple values in C_DV_ORDINAL constraints (Ian McNicoll)


 --

 Message: 1
 Date: Mon, 1 Aug 2011 16:17:16 +0100
 From: Ian McNicoll Ian.McNicoll at oceaninformatics.com
 Subject: Multiple values in C_DV_ORDINAL constraints
 To: For openEHR technical discussions
 openehr-technical at chime.ucl.ac.uk,For openEHR clinical
 discussions
 openehr-clinical at chime.ucl.ac.uk
 Message-ID:
 CAG-n1KyO==
 CMadsWqE6D1OLoRXNqp4jhKm8rX0ANAqiEave-HQ at mail.gmail.com
 Content-Type: text/plain; charset=ISO-8859-1

 I have come across an interesting example of where we might want to
 model an ordinal constraint where the values associated with each term
 are not unique.

 The example is the Waterlow Score

 http://www.judy-waterlow.co.uk/downloads/Waterlow%20Score%20Card-front.pdf

 If you look at the bottom-right corner Major surgery / Trauma you
 will se that two terms have identical values.

 Currently the openEHR Archetype Editor will not let me add duplicate
 values with separate terms. It is not clear (at least to me) from the
 specifications that this behaviour is correct.

 Is this a CR for the Archetype Editor, a CR to the Ref Model, or a
 clever alternative modelling suggestion to me?

 Regards,

 Ian
 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
 openEHR Clinical Knowledge Editor www.openehr.org/knowledge
 Honorary Senior Research Associate, CHIME, UCL
 BCS Primary Health Care ?www.phcsg.org



 --

 Message: 2
 Date: Mon, 01 Aug 2011 17:04:14 +0100
 From: Thomas Beale thomas.beale at oceaninformatics.com
 Subject: Re: Multiple values in C_DV_ORDINAL constraints
 To: openehr-clinical at openehr.org,   Openehr-Technical
 openehr-technical at openehr.org
 Message-ID: 4E36CE7E.8070707 at oceaninformatics.com
 Content-Type: text/plain; charset=iso-8859-1

 If we consider this an ordinal based model, in which numbers which have
 multiple possible values, e.g. skin type: 1 is for tissue paper dry,
 oedematous, etc - this would be modelling using terminological synonyms
 for a notional term whose meaning was something like 'waterlow skin type
 1'.

 - thomas

 On 01/08/2011 16:17, Ian McNicoll wrote:
  I have come across an interesting example of where we might want to
  model an ordinal constraint where the values associated with each term
  are not unique.
 
  The example is the Waterlow Score
 
 
 http://www.judy-waterlow.co.uk/downloads/Waterlow%20Score%20Card-front.pdf
 
  If you look at the 

Multiple archetypes in a single concept as a way to create an archetype collaborative

2011-08-03 Thread Hugh Leslie
An HTML attachment was scrubbed...
URL: 
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110803/71e07b6c/attachment.html


Multiple archetypes in a single concept as a way to create an archetype collaborative

2011-08-03 Thread Ian McNicoll
Hi Joaquim,

Just to add to Hugh's excellent comments. One of the issues you will
find is that it is sometimes impossible to harmonise all the competing
perspectives, even for something as seemingly simple as demographics.
The archetype driven approach, with maximal dataset philosophy, allows
these competing views to co-exist, very visibly and acts as a spur for
future harmonisation. 'Minimal dataset' philosophies lose this
knowledge and any future attempts at rationalisation essentially have
to start from scratch. So, as well, as capturing shared, agreed
requirements, we are also capturing dissent, which we can try again to
resolve in the future.

You should have a look at the Demographics model archetypes on CKM at
www.openehr.org/knowledge

e.g. Person http://www.openehr.org/knowledge/OKM.html#showArchetype_1013.1.479

We have had a few discussions with openMRS people in the past, and I
am sure there is real value in collaboration. I think the archetype
methodology and review process would be of great value, even if
openEHR was not used formally at the back-end of openMRS systems.

Ian



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
openEHR Clinical Knowledge Editor www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care ?www.phcsg.org




On 3 August 2011 08:44, Hugh Leslie hugh.leslie at oceaninformatics.com wrote:
 Hi Joaquin

 Just to add another? view...

 The issue of openMRS implementations having different representations of the
 same thing is a common problem across clinical systems everywhere.? Its this
 problem that is one of the things that we are trying to solve with
 archetypes.? In general, what we find is that most clinical concept
 representations in clinical systems are subsets (based on a use case) of a
 fully specified concept.? What we try to do in the archetypes is produce the
 fully specified concept and then constrain it for all the use cases.? The
 different names that you see used for different concepts are not just
 language dependent, but are also region and usage dependent.? This is also
 usually a? matter of constraining the archetype or using a particular
 terminology subset to represent the information.

 What openEHR offers openMRS is a single way of representing clinical
 information that becomes a logical record architecture.? If openMRS adopted
 this approach, then any openMRS system could immediately share information
 with any other even if the other system hadn't seen the information before.
 It also means that the burden of developing high quality, clinician
 validated information models is shifted away from the application developer
 to a global or regional space.? This is going to become more and more
 critical, as we try to capture more complex clinical information and compute
 on it as well as share it.

 regards Hugh

 On 3/08/2011 3:29 AM, Blaya, Joaquin Andres wrote:

 Hi,
 Apologies in advance if this is the incorrect email list for this topic, but
 I thought it was the most relevant.

 I'm a member of OpenMRS and there we are discussion a way to have users
 share the concepts (a limited form of an archetype) created in their
 systems. This means that for a single concept you could have many concepts
 from different implementations. This could be because of language or because
 different words refer to the same concept. For example, Gender in the US
 might be Sex in another country and Sexo in spanish.

 I would like to see if OpenEHR has solved this problem so that perhaps
 OpenMRS could begin to use archetypes.

 Thanks

 Joaquin

 om

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






Multiple archetypes in a single concept as a way to create an archetype collaborative

2011-08-03 Thread Stef Verlinden
Just to add to this. Another great aspect of openEHR is the separation of the 
technical and medical (content) aspect. 

In the clinical knowlegde manager (which Thomas already referred to) clinicians 
can cooperate to create archetype without have to think about the technical 
aspects. As for the technical people: whatever the clinicians come up with, 
they don't have to change any code, unless it would require a change in the 
reference model, which is extremely rare.

Cheers,

Stef


Op 3 aug 2011, om 09:44 heeft Hugh Leslie het volgende geschreven:

 Hi Joaquin
 
 Just to add another  view...
 
 The issue of openMRS implementations having different representations of the 
 same thing is a common problem across clinical systems everywhere.  Its this 
 problem that is one of the things that we are trying to solve with 
 archetypes.  In general, what we find is that most clinical concept 
 representations in clinical systems are subsets (based on a use case) of a 
 fully specified concept.  What we try to do in the archetypes is produce 
 the fully specified concept and then constrain it for all the use cases.  The 
 different names that you see used for different concepts are not just 
 language dependent, but are also region and usage dependent.  This is also 
 usually a  matter of constraining the archetype or using a particular 
 terminology subset to represent the information.
 
 What openEHR offers openMRS is a single way of representing clinical 
 information that becomes a logical record architecture.  If openMRS adopted 
 this approach, then any openMRS system could immediately share information 
 with any other even if the other system hadn't seen the information before.  
 It also means that the burden of developing high quality, clinician validated 
 information models is shifted away from the application developer to a global 
 or regional space.  This is going to become more and more critical, as we try 
 to capture more complex clinical information and compute on it as well as 
 share it.
 
 regards Hugh
 
 On 3/08/2011 3:29 AM, Blaya, Joaquin Andres wrote:
 
 Hi,
 Apologies in advance if this is the incorrect email list for this topic, but 
 I thought it was the most relevant.
 
 I'm a member of OpenMRS and there we are discussion a way to have users 
 share the concepts (a limited form of an archetype) created in their 
 systems. This means that for a single concept you could have many concepts 
 from different implementations. This could be because of language or because 
 different words refer to the same concept. For example, Gender in the US 
 might be Sex in another country and Sexo in spanish.
 
 I would like to see if OpenEHR has solved this problem so that perhaps 
 OpenMRS could begin to use archetypes.
 
 Thanks
 
 Joaquin
 
 om 
 
 ___
 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/20110803/3141c7b3/attachment.html