Hi, About age; A notice: Gestational age is a part of obstetrical records (e.i. of mother, or at least strongly related), and usually started by the 1st day of last mensturation, although real ovulation (thus conception) is about 2 weeks later. So, a simple date data type would be ok. After birth, time to delivery is a part of personal history of the person. e.g. borned at 41st week, 3300gr, ... Keeping date of birth as a datetime field would be enough to calculate the both age and age group whenever required, even some pediatrical requirements like 3/365 (3 days old), 2/12 (2 months old), and so on..
About sex, I believe, standard records must only include M/F/Indetermined as it's written on the passport of the person. Any other details other than above for sex and age, will express something different (like diagnosis or classification..) than our intension: data. Ergin Soysal, MD. > 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 for decision support. > > I wonder if we need to model this as an archetype for demographics - but > it needs to be in the EHR - age crops up in lots of evaluations > (problem, family history) so we might need to have it as a formal TYPE! > That is - we can use it consistently in various settings. > > > I would argue that gender is of the same nature - with social gender, > physical gender and genetic gender as the key concepts. > > No doubt there are others but these two are worth thinking about > carefully. > > Sam > > - > If you have any questions about using this list, > please send a message to d.lloyd at openehr.org > Pleksus Bili?im Teknolojileri http://www.pleksus.com.tr Tel: +90 (312) 435 5343 Fax: +90 (312) 435 4006 - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
