Isabel Rom?n Mart?nez wrote: >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 "aproximate age", when the birth date is not very clear, as Dr USM >Bish comment in his mail. All this can be reduced to include the birth date >in the model, with an additional field "confidence". This new field is >between 0 and 1. And only have value 1 when the birth date is sure. You >don?t have to include the "age" concept if you have "birth date" concept... >of course is better use birth date because this parameter doesn?t change but >age change every second Unfortunately! > >All the other concepts are not demographic but clinical and must be >registered (I think) in international codes and included as this in our >archetypes. > > > I think you are at least partly right here - for other values which need to be stored but are not date of birth should be archetyped. In fact, in the openEHR demographic model, not even date of birth (or date of death by the way) are hard-modelled - it is all archetyped.
- thomas - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
