Hi Pablo

 

The issue is that you do not see the reference model attributes in the
archetype editor. A Quantity data type has a normal range and other
reference ranges built in.

We do not set the reference ranges in archetypes as these vary and
archetypes are the absolute statement about things (what could possibly be
true ever, anywhere).

 

So it is in the form or data that you will get access to the reference
range. You could set it in a template (not possible in our tools as yet).
Generally the reference ranges come with the results from the lab or a
dynamic depending on gender, age etc.

 

I hope this is helpful - have a look at the data type specs for
clarification. The UML is at:

http://www.openehr.org/uml/release-1.0.1/Browsable/_9_0_76d0249_110959933787
7_94556_1510Report.html

 

You will see an optional normal_range and 0..* other reference ranges as
part of a root abstract class DV_ORDERED

 

Cheers, Sam

 

From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of pablo pazos
Sent: Tuesday, 13 October 2009 8:02 AM
To: openehr-clinical at openehr.org; openehr-technical at openehr.org
Subject: Modeling reference ranges

 

Hi,

I'm playing around with archetypes trying to model an observation and its
reference ranges,
I mean something like "blood pressure" and some range to define what is
"hypertension", but
I can't found an archetype that defines a reference range for an
observation.

Any one has experience in modeling something like this? 
An archetype is the correct place to define a reference range for an
observation value?
Any ideas?


Thak you!

Cheers,
Pablo Pazos Gutierrez



  _____  

Windows Live: Keep your friends up to date with what you do online.
<http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/so
cial-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20091013/26ccfa3a/attachment.html>

Reply via email to