Thank you all for your answers.
It's clear to me that Archetypes are not the place.
And that openEHR does not offer any particular solution. But since we 
are developing a system which should provide alerts and messaging for 
abnormal results and "dangerous" combinations of data values, we need to 
solve it in some way. Any links or reference material on possible 
approaches to this issue would be very welcome.

thank you all again

Dipak Kalra wrote:

> Dear All,
>
> Pathologists and laboratory message standards developers have over 
> many years made clear to me that it is always good practice to include 
> the applicable normal range with individual instances of observed 
> values, since those ranges are not fixed across measurement methods, 
> devices, organisations or over time. Published reference ranges in 
> clinical textbooks etc. are only a guide for those tests in which the 
> variation is nowadays quite small.
>
> For this reason, right from Synapses days - a decade ago! - , we have 
> not sought to put reference ranges into the archetype specification, 
> but (as Tom has stated) only to ensure that the archetype caters for 
> the inclusion of reference range instances along with the observed 
> value(s). 
>
> With best wishes,
>
> Dipak
> ________________________________________________________
> Dr Dipak Kalra
> Clinical Senior Lecturer in Health Informatics
> CHIME, University College London
> Holborn Union Building, Highgate Hill, London N19 5LW
> Direct Line: +44-20-7288-3362
> Fax: +44-20-7288-3322
> Web site: http://www.chime.ucl.ac.uk <http://www.chime.ucl.ac.uk/>
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>openEHR-technical mailing list
>openEHR-technical at openehr.org
>http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20060901/339b22c5/attachment.html>

Reply via email to