Opened 6 years ago

Closed 5 years ago

Last modified 5 years ago

#914 closed defect (fixed)

HERON patients seem to age after they die

Reported by: rwaitman Owned by: ngraham
Priority: major Milestone: heron-elk-city-update
Component: data-repository Keywords: vital-statistics, public-web
Cc: dconnolly Blocked By:
Blocking: Sensitive: no


Mani brought up the question.

Change History (13)

comment:1 Changed 6 years ago by rwaitman

  • Owner changed from mnair to dconnolly
  • Status changed from new to assigned

comment:2 Changed 6 years ago by rwaitman

  • Milestone changed from HERONv.Next to heron-waconda-update

comment:3 Changed 6 years ago by rwaitman

  • Milestone changed from heron-waconda-update to heron-walnut-update

comment:4 Changed 5 years ago by rwaitman

  • Milestone changed from heron-melvern-update to heron-elk-city-update
  • Sensitive unset

Let's ask the i2b2 people what they do at the purely demographic context.

Ex: patient died when they were 70. It's now 10 years later. If I search for cases over the age of 75, should that person be included in the cohort?

send message to i2b2 today:
Hi everybody,
We've got a question related to how people manage their i2b2 etls and managing "age".

Example: somebody dies in 2002 at the age of 70.

If I query i2b2 today at our i2b2 instance for people over 70, we'll be including this person.

We can also inform users they can exclude deceased people.

But overall, what do people do? Should we add code that stops people from aging once they die?
Of course, there will be many cases where we don't know if they are dead yet who will be aging anyway (though we've integrated the social security death index to cover some of those people)

We also have the standard i2b2 "Age at Visit" concept, so clearly in that case, they will be 70 years old or less.


comment:5 Changed 5 years ago by rwaitman

exchanged email ideas with Jack London at Kimmel Cancer Center. Recommend the following approach:
Conceptually to me I think we ought to change that to
if (dead)

age = _date_of_death - birthdate;


age = current_date - birthdate;


That would reflect their age at time of death.

Also closing duplicate ticket I opened #1525

comment:6 Changed 5 years ago by ngraham

  • Owner changed from dconnolly to ngraham

comment:7 Changed 5 years ago by ngraham

Add age_in_years_num to the patient dimension as well and make this populate that field.

comment:8 Changed 5 years ago by ngraham

  • Cc dconnolly added

I think I fixed this in [b52850c3f3ee]. Dan, would you mind having a look?

Manual Front-end Testing

Finished Query: "Frontiers Resea@15:10:35"
[2.9 secs]
Compute Time: 1 secs
Patient Set for "Frontiers Resea@15:10:35"
Number of patients for "Frontiers Resea@15:10:35"
patient_count: 2

Patient set from test patient set (Previous query pane)

Frontiers Resea@15:10:35 [12-6-2012] [demo]
  Results of Frontiers Resea@15:10:35 [12-6-2012] [demo]
    Patient Set for "Frontiers Resea@15:10:35" - FINISHED
      24220 [74 y/o f @]
      24416 [56 y/o m other]

comment:9 Changed 5 years ago by ngraham

  • Resolution set to fixed
  • Status changed from assigned to closed

As far as I know, this ticket is closed. We can always re-open if we find any issues (see comment:8).

comment:10 Changed 5 years ago by dconnolly

  • Type changed from enhancement to defect

comment:11 Changed 5 years ago by dconnolly

  • Keywords vital-statistics added

comment:12 Changed 5 years ago by ngraham

  • Keywords public-web added

comment:13 Changed 5 years ago by kcrane2

Approved for public release.

Note: See TracTickets for help on using tickets.