Hi Ian, I am sorry for my explanation being too vague.
Temporal data management is a field of data management focusing on the temporal aspect of data. Given temporal data, i.e. data with one or more time dimensions, operations like temporal joins and temporal aggregates are different compared to their counterparts for non-temporal data. To make things clearer, the following example describes one type of temporal aggregation called instant temporal aggregation: A patient was prescribed 2 medications. The first medication was prescribed for the interval 0 to 10, the second medication was prescribed for the interval 5 to 15. Assume you want to know how many medications were prescribed for this patient over time. First, you have to compute time interval for which the data does not change in time. This operation is called time slicing. In this example the constant intervals after time slicing are: [0, 4] [5, 10] [11, 15] The second step in temporal aggregation is to calculate the aggregate value -- in this case the number of medications -- for each constant interval, which are: [0, 4], 1 [5, 10], 2 [11, 15], 1 In this example there are only two intervals but there might be a lot more with much more overlapping sections becoming a challenge regarding computing. Instant temporal aggregation is just one type of temporal aggregation, there are some more. With relational DBMSs you do temporal aggregation with using complicated SQL queries, however, those are rather inefficient. In the last two decades researchers in temporal data management came up with some temporal data models, temporal operations and corresponding efficient algorithms, mainly for the relational data model. My research focuses on temporal data management on hierarchical data, like XML. Since I like the openEHR idea and I have worked in Health Informatics for the last years, I would like to use openEHR data instances. At the moment I am looking for a sound running example, which is clinically relevant and needs temporal data management. I was thinking about some temporal aggregates over a prescription list, a problem list or some other archetyped data with potentially overlapping time intervals. If somebody has an idea, s/he is really welcome. I hope things are clearer now. Cheers Bruno Ian McNicoll wrote: > Hi Bruno, > > I think you are probably on the right track. The COMPOSITION > archetypes are containers which will include a number of different > clinical statements such as medication, diagnosis, lab results, all or > any of which might have associated overlapping timings. It would be > helpful to know a little more of what you mean by "temporal data > management of hierarchical medical data" to help us give better > advice. > > Ian > > > Dr Ian McNicoll > office +44(0)141 560 4657 > fax +44(0)141 560 4657 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > > Consultant - Ocean Informatics ian.mcnicoll at oceaninformatics.com > Consultant - IRIS GP Accounts > > Member of BCS Primary Health Care Specialist Group ? http://www.phcsg.org > > > 2008/6/18 Bruno Cadonna <cadonna at inf.unibz.it>: >> hi again, >> >> since i wrote my request to the list regarding openehr data instances i have >> browsed the archetype repository and found some archetypes of which i think >> their instances could satisfy my temporal requirements. >> >> openEHR-EHR-COMPOSITION.prescription.v1.adl: >> >> in the lower level archetype openEHR-EHR-ITEM_TREE.medication.v1 the dates >> of first and last administrations can be recorded which form an interval. an >> instance of this archetype can record more than one medication, thus, the >> administration intervals might overlap. the amount of medications and other >> calculations can be performed medications, which are aggregates. the >> administration interval might not be contained in the context time. >> >> similar applies to the archetypes below, ie they have lower level archetypes >> which can record data over time intervals and aggregates can be calculated. >> >> openEHR-EHR-COMPOSITION.problem_list.v1draft.adl >> openEHR-EHR-COMPOSITION.report.v1.adl >> openEHR-EHR-COMPOSITION.history-medical_surgical.v1draft.adl >> >> what do you think? >> are my interpretations of those archetypes right? >> does anybody have example instances of those archetypes that s/he can give >> me? >> i have some instances, but maybe somebody has better ones, maybe even real >> ones. >> >> cheers >> bruno >> >> Bruno Cadonna wrote: >>> hi list, >>> >>> for my research on temporal data management of hierarchical medical data i >>> am looking for a openEHR data instance that can be used as running example >>> to work with. >>> >>> the data instance should have following properties: >>> >>> * contain time intervals, e.g. a history of patient's symptoms, history of >>> medications etc. >>> * the time intervals should possibly overlap. >>> * aggregates like count, min, max, avg over the data (e.g. number of >>> medications taken, avg of a observed value, etc.) should be possible. >>> * the event context start time should possibly be after the time intervals >>> in the data or at least start after the first time interval in the data. >>> * the data instance should be in openEHR's XML format >>> >>> does anybody have such a data instance and the corresponding archetype? >>> or at least, can anybody give me a clue for which archetype whose >>> instances satisfy the above properties i should look for? >>> >>> cheers >>> bruno >>> >>> _______________________________________________ >>> openEHR-technical mailing list >>> openEHR-technical at openehr.org >>> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> -- >> Bruno Cadonna >> Center for Database and Information Systems (DIS) >> Faculty of Computer Science >> Free University of Bozen-Bolzano >> >> Piazza Domenicani 3 >> 39100 Bozen/Bolzano >> Italy >> >> web: http://www.unibz.it/inf >> >> _______________________________________________ >> openEHR-technical mailing list >> openEHR-technical at openehr.org >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >> >> > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- Bruno Cadonna Center for Database and Information Systems (DIS) Faculty of Computer Science Free University of Bozen-Bolzano Piazza Domenicani 3 39100 Bozen/Bolzano Italy web: http://www.unibz.it/inf -------------- next part -------------- A non-text attachment was scrubbed... Name: cadonna.vcf Type: text/x-vcard Size: 452 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080618/6c10d671/attachment.vcf>
