Hi Gerard,

On Sun, Jun 24, 2018 at 4:04 AM, GF <[email protected]> wrote:

> See below
>
> GF
>
> Gerard   Freriks
> +31 620347088
>   [email protected]
>
> Kattensingel  20
> 2801 CA Gouda
> the Netherlands
>
> On 24 Jun 2018, at 01:49, Pablo Pazos <[email protected]> wrote:
>
> Hi Gerard,
>
> On Sat, Jun 23, 2018 at 6:58 PM, GF <[email protected]> wrote:
>
>> When one assumes that the all events are the same kind of events but
>> occurring at various points in time,
>>
>
> That is what is supported by the openEHR spec, no need to assume. All
> EVENTs in HISTORY.data are of the same type ~ have the same definition in
> the archetype.
>
>
>>
>> Then the period can be expressed as Frequency (n/T) or equally as Period
>> n/F).
>>
>> Where n=number of events and T= total time from begin of the first event
>> till the last (E.1 - E.n)
>> Clinical example:
>> Heart rate = 120 beats per minute.
>>
>> Or as Period (T=n/F) expressed as time units that is the time between two
>> events.
>> Clinical example:
>> Period between heart beats =  60/120 = 0,5 seconde. I.E the time between
>> E(n+1) - E(n)
>>
>> In your example
>> Period =  1 divided by Time (E2.start - Time E1.start),
>> or, Period = 1 divided by Time(E3.start) - Time(E2.start)
>> or, Period = 2  divided by Time (E3.start - Time E1.start)
>>
>
> This works with POINT_EVENT, my question is about INTERVAL_EVENT from the
> openEHR specs, where each event start and end are different.
>
>
> Any Event (process) has an end date and start date an can be small but
> never zero.
> End dates are always different from start dates.
> So what do you mean?
>

I'm talking about openEHR events by the definition of the specs, not trying
to come up with another definition. In openEHR POINT_EVENT is the record of
an event that to the record is just a point in time, doesn't really matters
if in reality the event took 10 seconds to execute, like a BP reading. That
is not clinically relevant in most contexts.


>
>
> By openEHR, the heart rate EVENT is one single measure of the hear rate,
> there is no record of individual beats.
>
>
> Its meaning can be several things.
> It can be the rate (frequency) at a real *point* in time. Time=T e.g.
> now, yesterday.
> Or it can be the average over a *period* of time.e.g. the last minute,the
> last 10 minutes, the last month.
> Actually it is a little bit more complex.
>
>
> Again, I'm following the spec definitions, not trying to create my own
interpretation. In that context, current models of heart rate, and current
information model structure for OBSERVATION don't try to model individual
beats, an EVENT is not that, is the consideration of the beat rate as one
data point.

Then the period that I'm talking about is the HISTORY.period by the openEHR
specs, that affect EVENTs in the same OBSERVATION time series. That is not
clearly defined in the specs (going back to my original question).


>
> What would make an INTERVAL_EVENT from heart rate, is to record the
> average heart rate in an hour.
>
> Frequency at *point* in a Unit Time.
>
> Not sure that I'm following. INTERVAL_EVENT by the openEHR specs is not
that. It allows to record a summarized value from an interval of time, e.g.
average (or max, or min, or mean, ...) heart rate in the last 10 minutes.


> And a periodic list of INTERVAL_EVENTs, would be records of the average of
> the heart rate that happen periodically. The issue I'm having is the specs
> don't have a concrete definition of "period" for INTERVAL_EVENT series.
>
>
> INTERVAL–EVENTs as interval between events measured over a *period* of
> time.
>
> What is NOT defined?
>

This is not correct, check the spec:
http://www.openehr.org/releases/RM/Release-1.0.2/docs/data_structures/data_structures.html#_history_package


>
>
> _______________________________________________
> openEHR-technical mailing list
> [email protected]
> http://lists.openehr.org/mailman/listinfo/openehr-
> technical_lists.openehr.org
>
>


-- 
*Ing. Pablo Pazos Gutiérrez*
[email protected]
+598 99 043 145
skype: cabolabs
Subscribe to our newsletter <http://eepurl.com/b_w_tj>
<https://cabolabs.com/>
http://www.cabolabs.com
https://cloudehrserver.com
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to