Hi Igor,

This is a common issue and is a good argument for not mandating data entry
in electronic clinical systems!! There is no equivalent mandation for paper
records - clinicians would normally just leave the fileds blank and make
some sort of comment in the margin of the form.

In your example I will assume that it is the systolic and diastolic elements
that are mandatory and set as such at template level. It is still
permissible for the element to be left empty and for a null flavour to be
set, in this case 'not applicable' see:

http://www.openehr.org/wiki/display/spec/Null+Flavours+and+Boolean+data+in+openEHR


The reason for the null could be documented in the Blood pressure archetypes
Comment element.

We recognise a need to find a way of easily adding a comment to any node,
when a null is recorded - a similar issue arose recently with  the Glasgow
Coma Scale when e.g. Eyes could not be observed.

There are 2 potential solutions..

1. Add a 'reason for null' text attribute in the Reference model alongside
the null itself.

2. Use the link attribute available to every node to attach an 'annotation'
- this will be recorded in a separate archetype, which allows considerable
flexibility as to whether a simple text field is required or perhaps more
complex, structured  'reasons for null' are required. This approach is being
investigated as a means of annotating data elements for quality or
'fitness-for-purpose'. e.g. Is a device obtained blood pressure valid fro
graphing or should it be excluded?

Ian

Dr Ian McNicoll
office / fax  +44(0)141 560 4657
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com
ian at mcmi.co.uk

Clinical Analyst  Ocean Informatics openEHR Archetype Editorial Group
Member BCS Primary Health Care SG Group www.phcsg.org / BCS Health Scotland



2010/6/25 ????? ??????? <i.lizunov at infinnity.ru>

> Hi all!
>
> I'm modelling "Blood Circulation System Examination" archetype and it's
> components like "Arterial Pressure" archetype.
>
> The arterial pressure measurement is required for every examination in my
> particular hospital.
> So, I need to enforce constraint for this archetype from [0..*] to [1..*]
> in my template .
> But I have counterargument for this.
>
> Some of the hospital's patients are disabled armless people, so arterial
> pressure couldn't bee measured at examination. And this must became empty.
>
> There are many examples like this. So my question is: How I can model it
> with openEHR?
>
> Thank you for answers.
>
> --
> Best Regards
> Igor Lizunov
>
> _______________________________________________
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20100626/dcc92d96/attachment.html>

Reply via email to