Re: Modelling not-applicable fields

[Thomas Beale <thomas.beale@oceaninformatics.com>]

Igor,

I might be talking out of turn here, but an archetype for systemic arterial BP is still valid for a person with no arms. The measurement just has to be done with a cuff on the leg or in some other way, i.e. the protocol of the measurement is different. So if your hospital says 'there must always be a systolic BP', then for amputees, it is just a question of how, not, if, you obtain it. Now, if I read carefully below, i think you are saying that there are examination events at which a disabled person turns up, and the examining doctor is not equipped to do a BP for that kind of person. In that case, you do have a situation where the BP data won't be filled out, and instead the 'null-flavour' value needs to be set to 'not available' (or maybe some richer value as has been suggested recently). Either way, Systolic BP can still be set to mandatory, since even an ELEMENT with no value attribute but with a null-flavour will satisfy this.

- thomas beale


On 25/06/2010 11:58, Игорь Лизунов wrote:

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@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical