Dear All

Age is time after birth - we are not going to change that.

We have agreed that we need to record one more date in the demographic 
model - which is 'approximate date of conception', or 'expected date of 
birth'

Which do people prefer - I chose the latter as it will probably be a cut 
and paste from the mothers record and does not get into the when did I 
conceive stuff.

What do others think?


Finally....I am proposing that we think about a new class (?datatype) 
such as 'DV_Textural_Ordered' for dealing with named quantities - which 
have DV_ORDERED or DV_INTERVAL as their value - a fuzzy quantity.

Examples in XML might be something like:

<DV_Textural_ordered>
        <text>"Birth"</text>
        <value type="DV_QUANTITY">
                <magnitude>0<magnitude>
                <units>"days"</units>
        </value>
</DV_Textural_ordered>

<DV_Textural_ordered>
        <text>"Adolescence"</text>
        <value type="DV_INTERVAL">
                <lower type="DV_QUANTITY">
                        <magnitude>12<magnitude>
                        <units>"years"</units>
                </lower>
                <upper type="DV_QUANTITY">
                        <magnitude>18<magnitude>
                        <units>"years"</units>
                </upper>
        </value>
</DV_Textural_ordered>

<DV_Textural_ordered>
        <text>"Three times a day"</text>
        <value type="DV_TIME_SPECIFICATION">
                <repeat>"FREQ=BYDAY;OCCURRENCES=3"</repeat>
        </value>
</DV_Textural_ordered>


<DV_Textural_ordered>
        <text>"Three times a day"</text>
        <value type="DV_TIME_SPECIFICATION">
                <repeat>"0800;1400;2000"</repeat>
        </value>
</DV_Textural_ordered>


<DV_Textural_ordered>
        <text>"Last night"</text>
        <value type="DV_INTERVAL">
                <lower type="DV_TIME">
                        <value>20:00<value>
                </lower>
                <upper type="DV_TIME">
                        <value>06:00<value>
                </upper>
        </value>
</DV_Textural_ordered>


The problem is that they would not be available through inheritence - so 
the possibility of entering these classes would have to be constrained.

This is just thinking out loud.

Cheers, Sam


Gerard Freriks wrote:
> 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 252 544896
> +31 654 792800
> On 31 Jan 2005, at 19:10, William E Hammond wrote:
> 
>     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 unless the definitions are precise.
> 
>     Ed Hammond
> 
-
If you have any questions about using this list,
please send a message to d.lloyd at openehr.org

Reply via email to