Viv3ckj/move validation data #90
Conversation
| pharmacy_first_dates = select_events(clinical_events, codelist=pharmacy_first_consultation_codelist).date | ||
|
|
||
| # Specify whether a patient has been prescribed a PF medication on the same day as a PF consultation code | ||
| has_pfmed_on_pfdate = selected_med_events.where(medications.date.is_in(pharmacy_first_dates)).exists_for_patient() |
There was a problem hiding this comment.
selected_med_events has already been filtered to only include those events where the consultation_id matches a pharmacy_first_ids, see:
selected_med_events = select_events(
medications, consultation_ids=pharmacy_first_ids).where(
medications.date.is_on_or_between(INTERVAL.start_date, INTERVAL.end_date)
)here we want to use the date as a backup to look at all pharmacy first medications on the same day as a pharmacy first consultation, specifically for those events where the linkage through consultation_id doesnt exist. so we need to provide a medications event frame that still includes all the pf medications
There was a problem hiding this comment.
Good spot! Thanks, I've made the changes now.
|
We just noticed that we need to rework some of the selected events because we sometimes want them linked by |
|
@viv3ckj I just wanted to check my understanding why we're not pulling the eps_erd_prescribing_data.r function from the data development project. I think that was because we're not expecting to continue looking at medication status in this repo? |
|
@milanwiedemann we are pulling eps_erd_prescribing_data.R, check lib/functions/eps_erd_prescribing_data.R. Do you think it should or shouldn't be included? |
…c_stats_measure Refactor pf desc stats measure
Closes #84