[MADIE-379] Current year and birthdate issues with Bonnie Created: 09/15/17  Updated: 05/08/18  Resolved: 10/09/17

Status: Closed
Project: MADiE Issue Tracker
Component/s: Measure Calculation
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Moderate
Reporter: Ann Phillips (Inactive) Assignee: Lizzie Charbonneau
Resolution: Answered Votes: 0
Labels: CQL, CQM
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive BCS_v5_3_Artifacts.zip    
Measure/Library Title: Breast Cancer Screening
CBE Number: Breast Cancer Screening test measure BCS Draft v0.0.000
Test Case Name(s): Xuebei Zhao

 Description   

One of my colleagues was creating test patients for a measure created by another colleague and ran into an interesting problem with Bonnie's current date, and birthdates of patients.

Bonnie is always 2012, which we all know about - but the measure calls for people who turned 52 during the measurement period to be part of the IPP.

This text below is from my colleagues email to me:

"I’m pretty sure that Alpha Bonnie cannot catch people who turned 52 in 2012.

For our Breast Cancer Screening measure, the IPP is women 52-74 years as of December 31 of the measurement year. I set the birthdate of one test patient on 2/1/1960. Technically, she should turn 52 on 2/1/2012, which qualifies the criterion for the IPP. However, Alpha Bonnie didn’t capture it and didn’t check the IPP for her. And as I changed her birthdate to 12/31/1959, the IPP box got checked. I think it’s because Alpha Bonnie cannot capture the patients who turned 52 in 2012 and just those who were already 52 and over in that year. Could you please check it for us? Is it because Bonnie gets confused about the current year (2012) sometimes?"



 Comments   
Comment by Lizzie Charbonneau [ 10/09/17 ]

Thanks! I've closed it.

Comment by Ann Phillips (Inactive) [ 10/09/17 ]

I tried to just close it, but I didn't see an option to do so

Comment by Lizzie Charbonneau [ 10/09/17 ]

great, thank you!

Comment by Ann Phillips (Inactive) [ 10/09/17 ]

Zi says she was able to edit the logic and make the dates work correctly

Comment by Ann Phillips (Inactive) [ 10/06/17 ]

Hi Lizzie,

I'm traveling on business and haven't heard anything from my colleague about this. Sent her a reminder this morning. She is fairly new to this (wasn't a measure I wrote) and I think it was a logic issue. I'm sure I'll have an answer this morning!

A

Comment by Lizzie Charbonneau [ 10/05/17 ]

Hi Ann,

Just wanted to follow up. Any updates if this response clarifies things for the measure author?

Thank you,
Lizzie

Comment by Ann Phillips (Inactive) [ 09/20/17 ]

thanks Lizzie! I didn't write the logic for this one, but I'll turn this over to them and have them fix it and retest'

a

Comment by Lizzie Charbonneau [ 09/20/17 ]

Hi,

The trouble is that the logic calculating the age is the following:

AgeInYearsAt( start of "Measurement Period" ) >= 52

This requires that the patient be 52 at the start of the measurement period. They cannot be 51 at the start of the measurement period. A patient with a birthdate of 2/1/1960 is 51 at the start of the measurement period. Perhaps modify the logic to the following if you want people to be able to turn 52 during the measurement periord:

AgeInYearsAt( end of "Measurement Period" ) >= 52

or

AgeInYearsAt( start of "Measurement Period" ) >= 51

Thanks,
Lizzie

Comment by Chris Tohline (Inactive) [ 09/15/17 ]

Thank you for the upload. We will investigate and get back to you.

Comment by Ann Phillips (Inactive) [ 09/15/17 ]

Hi Chris,

I've added Zi to this email as she is the one working on the measure and the export will come from her account. I'll talk her through the patient export and attach it to the ticket!

Thanks

Ann

Comment by Chris Tohline (Inactive) [ 09/15/17 ]

Ann, we will investigate and get back to you. As is often the case, we may need a copy of the MAT export package under test, can you please attach that to this ticket?

Thanks,
--Chris

Generated at Sun Aug 31 08:15:14 UTC 2025 using Jira 10.3.8#10030008-sha1:cdaed80cecc964184c5b19b002388d56f96e274e.