GDL rules with "age-dependent" reference ranges

Hi there, besides of our core acitivities, we recently fiddled a little with GDL to evaluate, if it might be of use for a decision support project in the context of a pediatric ICU. One challenge with guidelines in pediatric patients is that the reference ranges of variables depent on the age

Age

Hi Karsten, The *definition* of a lightyear is *fixed*, i.e., the 'distance light travels in a year', and not directly measurable, e.g., tag a photon and measure its progress thoughout one year. The problem is that the *distance* each photon travels in a year may not be the same. You are

Antw: Re: Age, gender and more

On Fri, Feb 04, 2005 at 08:45:15AM +0930, Sam Heard wrote: My proposal is that we have a 'named quantity' class that displays a term, a quantity or a quantity range (as quantity range already has the interface for quantity). Sam, I second this proposal of a 'named qty class' with

Age

Age=: Time since an reference event took place and is expressed as: lightyears, years, months, days, minutes, seconds (and parts thereof) Lightyears is a measure of distance, not time. And not constant either, at that. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD

Age

'. Regards! -Thomas Clark David Guest wrote: Karsten Hilbert wrote: Age=: Time since an reference event took place and is expressed as: lightyears, years, months, days, minutes, seconds (and parts thereof) Lightyears is a measure of distance, not time. In fact it is *the* measurement

Age and named quantities

Sam, You mean the 'age of a person' and not 'age'. Gerard -- private -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands +31 252 544896 +31 654 792800 On 31 Jan 2005, at 23:30, Sam Heard wrote: Age is time after birth - we are not going to change that. We have

Age and named quantities

On Tue, Feb 01, 2005 at 08:00:39AM +0930, Sam Heard wrote: Age is time after birth - we are not going to change that. That's fine ... now for the second ... We have agreed that we need to record one more date in the demographic model - which is 'approximate date of conception

Age and named quantities

An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20050201/cf64f32b/attachment.html

Age - a summary

Ergin, and all ERGIN: Thanks - there is no problem working from date of birth forward to age group - it is when you are working back and times are fuzzy. In family history when the DOB is not known it is even more of an issue. The issue of FUZZY ages (and other quantities) I believe we need

Age

LR Buitenkaag The Netherlands +31 252 544896 +31 654 792800 On 27 Jan 2005, at 20:15, Philippe AMELINE wrote: Hi, In Odyssee, we have made the choice of : 1) defining the concept Age as an ellapsed time value 2) defining age related concepts (like child, old person...) as fuzzy sets I

Age

For an age, I agree that the date of birth is adequate as long as you remember people do not age after they die. It is also convenient to have a reference time mark for many things, including conception, start of a course of treatment. Adjectives and nouns are difficult to put into algorithms

Age

Dear all, It is fine for me when we can agree that we mean by 'Age' time after birth. How will we name and define concepts like: youth, post conception, post gestation, middel aged, elderly? Gerard -- private -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands +31

Age

Gerard, From all the messages, it seems to me we can define 3 kind of values : 1) Values with a genuine relationship with date of birth : youth, middle age, elderly... Those who can manage fuzzy sets will do it that way, while others will have to use simple time intervals based on date

Age

Who are you calling elderly? I still hold out for age, even if it is fuzzy. Ed Gerard Freriks gfrer at luna.nl@openehr.org on 01/31/2005 04:25:17 PM Please respond to Gerard Freriks gfrer at luna.nl Sent by:owner-openehr-technical at openehr.org To:William E Hammond hammo001

Age

I agree with using date of birth for making the determination of an individual's age, as long as we have support for relative age for concepts such as puberty, menopause, at an age of risk given their family history of a malignance with a first degree relative whose onset of illness

Age

. But the result is the same at the application level - a 0-offset age from the (approximate) moment of conception (for those patients for whom this is relevant obviously). Please forgive my density ;-) I understand what Sam's saying, but I don't see how that provides the information to which I

Age

. Also, you must keep conceptional age confidential, since it's expressed in weeks for a long time. Ergin Soysal, MD Bill Walton wrote: It seems to me, although I'm not a physician, that there are, or we might learn that, there are medical problems that crop up later in life that are related

Age

that EDD and DOB are both recorded. So EDD might be 15 sep 2000 (implying conception on 1/1/2000 - sorry to the obstetricians if I am a bit off here!); DOB might be 1 aug 2000, implying a 6-week premature birth. Then an application Age object could compute or provide: - date_of_birth : Date

Age

Thomas, What you wrote with respect to age, is absolutely true. It is a notion defined at the knowledge layer. But expressed at an information model layer. On the level of the knowledge layer 'age' is more than a set of numbers indicating the time past since an arbitrary point in time. Next

Antw: Re: Age, gender and more

(Geneva). This kind of referring to age and time is quite usual in nursing practice, (after birth, post operative, young), infant) I am now at an airport lounge and have no access to all, but do not start double work on this please. William, what vocabularies and reference ranges should we

Age

have made the choice of : 1) defining the concept Age as an ellapsed time value 2) defining age related concepts (like child, old person...) as fuzzy sets I think that it is the only way you can manage this kind of thinks. We also have a (quite) good model for cyclic events ; I can describe

Age

Hello every body, Sorry for my intrusion. I?m working with demographic models, so this discussion about the concept age is interesting for me. I think that the only demographic valid concept of age is the difference between the actual date and the birth date. We can include a very close concept

Age

Hi All, One should include mental age as well. EHRs should not presume a Patient's mental capabilities closely track their physical age. This would be a recipe for disaaster under its own terms since 'young' physical age and 'senior' physical age represent gray areas regarding mental

Age, gender and more

Hi Gerard has raised other issues - there are names for age-ranges or phases such as adolescence, neonatal, toddler. It may be too much for us to deal with but age is certainly not just a number - you just have to ask the mother of a small baby - it has units like days, weeks, months. I think

Age

On Thu, 2005-01-27 at 05:09, USM Bish wrote: I am of the view, that there is no requirement of age at all. What is needed is the date of birth in the initial record. After that every time the patient/ individual seeks medical attendance, the age is automatically calculated

Age

I too agree on this. We need to consider about these. --- Sam Heard sam.heard at bigpond.com wrote: Tom and others The idea of age as a complex notion - post-conception, gestational (LMP) ie it can involve pre-birth periods - even well into life. This apperas to be important