Context Navigation

← Previous Ticket
Next Ticket →

#2301 assigned problem

constraining birth-date by date doesn't work - HERON uses sysdate for start_date in demographics

Reported by:	tmcmahon	Owned by:	ngraham
Priority:	minor	Milestone:	heron-menomonee-update
Component:	data-repository	Keywords:	public-web wrong-results training
Cc:	dconnolly, mhoag, ngraham, badagarla	Blocked By:
Blocking:		Sensitive:	no

Description

Currently the start date for age in the demographics folder is not the DOB. This causes issues when users limit the date for a group that contains age. I try to train people not to limit dates for ages, but many continue to do so. Changing the start_date to DOB instead of registration date will eliminate false results and confusion.

Background:
(9:57:57 AM) DanC: this age stuff should be in https://bmi-work.kumc.edu/work/browser/heron_load/epic_demographic_transform.sql ...
(9:58:26 AM) DanC: case when reg_date is null then sysdate else reg_date end start_date
(9:58:32 AM) DanC: https://bmi-work.kumc.edu/work/browser/heron_load/epic_demographic_transform.sql#L44

Russ, please assign the milestone/priority.

Change History (17)

comment:1 Changed 7 years ago by dconnolly

Milestone:	heron-solomon-update → heron-toronto-update
Owner:	changed from rwaitman to ngraham
Status:	new → assigned
Type:	task → problem

comment:2 Changed 7 years ago by ngraham

Milestone:	heron-toronto-update → heron-lovewell-update
Priority:	major → minor

Though I think the resolution to this problem is likely straightforward, I didn't get around to it for this release. Postponing one month. Also, I don't believe this is considered a high-level goal so setting priority accordingly.

comment:3 Changed 7 years ago by ngraham

Keywords:	public-web added
Sensitive:	unset

comment:4 Changed 6 years ago by ngraham

Milestone:	heron-republican-update → heron-marmaton-update

For me, it seems intuitive that the start date for an age fact should be the date the age was measured. But, I guess that's not in line with the way our customers are thinking.

I've taken a stab at this in [a49fa76af023] on the age_facts_start_date_2301 branch.

Note that for a rather small percentage of patients, the start date for the age fact will be the ETL date. For just a handful, it'll be the registration date.

select count(*) from patient_dimension; --2,035,468
select count(*) from patient_dimension where birth_date_hipaa is null; --23,034
select count(*) from patient_dimension where birth_date_hipaa is null and reg_date is null; --23,030
select count(*) from patient_dimension where birth_date_hipaa is null and reg_date is not null; --4

ETL has already started for milestone:heron-republican-update so moving to the next milestone.

comment:5 Changed 6 years ago by dconnolly

Bummer we didn't finish this while working on HIPAA age issues recently.

comment:6 Changed 6 years ago by dconnolly

Milestone:	heron-verdigris-update → heron-kanopolis-update

postponing tickets other than those identified as Verdigris priorities in today's heron-weekly meeting

comment:7 Changed 6 years ago by dconnolly

Keywords:	wrong-results added
Milestone:	heron-kanopolis-update → heron-webster-update
Priority:	minor → major

reviewing the minor pile with NG...

comment:8 Changed 6 years ago by ngraham

Keywords:	training added
Priority:	major → minor

Tamara says this isn't a high priority as she has a workaround to tell users.