Christoph Rinner wrote: > Hi, > > I am writing my diploma thesis at the Vienna Medical University. I have > two questions concerning the openEHR-EHR-OBSERVATION.blood_pressure.v1 > Archetype (Date 22/03/2006) and would be very thankful if someone could > answer them briefly. > > 1st: > I read in the "The openEHR Reference Model - EHR Information Model" > (openehr_ehr_im.pdf Revision: 5.1.0) in chapter "8.2.3.4 Two ways of > Recording State" that there are two ways to record States inside a History. > In this Blood pressure measurement Archetype they have chosen the way > where the state is recorded outside data History. > Isn?t it necessary to correlate a blood pressure measurement [at0003] to a > position [at0008] (Systolic: 120, Diastolic: 80, Position: Standing)? > Actually, this archetype has been remodelled using the other method. Both methods make sense, depending on what you are doing, but the state-on-Event method is more likely with normal GP and hospital recording, whereas the other one would be more likely used in sport medicine, or maybe in conjunction with ECG etc in general fitness testing. > What is the medical reason for modelling it like that? Even if it is made > the other way the problem still occurs with the protocol. When we try to > match an Instrument [at0012] (from Protocol) to a certain blood pressure > measurement (Systolic: 120, Diastolic: 80, Instrument: XYZ) we don?t know > which instrument belongs to which blood pressure. Am I wrong? Is there a > way to correlate them? Is there no need to correlate them? > No, protocol (i.e. method of measurement) is the same for the whole history - this is definitional. You can't safely change how you record something in mid-series - you have to record a new time series. > 2nd: > Why does the "state" begin with an ITEM_LIST[at0007] and not with a > History? In the documentation it looks as if "state" and "data" have the > same structure. > they do; this was an error in the Archetype Editor which has now been fixed, but the archetypes have not being upgraded yet.
- thomas beale _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
