On 26/03/2012 19:49, pablo pazos wrote: > Hi Thomas, > > A while ago, we gave this issue a big thought when designing the > EHRGen framework. > > Periodic event records are needed when recording certain studies and > when monitoring a patient, but this can be recorded as single point > events, and using a query to get all the points in a series.
it can but that's very inefficient, and doesn't correctly represent what is happening, when you are talking about multiple samples in a series, e.g. coming from vital signs monitors, orthostatic BP, apgar, and many others. > > From the GUI perspective is very difficult to record periodic events, > because you have to login, select a patient, select a record, select > the section of that record that contains the periodic data, enter a > new item to the time series. and presumably enter another, and another. That doesn't sound like a problem - it's how normal GUI for Apgar and multi-sample manual BP collection work. Don't forget, we are talking about time series in the seconds to minutes domain here. Although Glucose tolerance test data would make more sense to be entered as one time series, after the fact. > The other option is to have the patient's record always open, and that > is not possible in all scenarios (for technical or security reasons). well ifyou are talking about long period of time, like repeated nursing observations, you should be committing those 1 sample at a time. > > In the other hand, in the majority of cases of clinical record through > a GUI, the data is recorded as a single point event, e.g. at a patient > visit. So we design the EHRGen just to use point events, and if you > want to record a series of events, a service should be provided to get > the data from other systems (e.g. a LAB system), but not from the GUI. that and vital signs monitors are certainly a common source of time-based data. But whether the source of the data is the GUI or somewhere else doesn't change the semantics of the model, or the need for it. Like I said elsewhere, I have no problem with adding a single-event Observation as well. But having only that will completely cripple many hospital apps and efficient data representation and querying related to this data. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20120326/09b309e7/attachment.html>
