Tuesday, 01/15/2019
- ID
- afba1158-b192-4b34-83dc-87d4eed29ad6
Tasks
No entry today, just closed a sprint
DONE Pop Health Jan 2 Sprint
CLOSED: DEADLINE:
DONE Figure out why CDS is still not showing up for 2019
CLOSED: SCHEDULED:
Looking for all MeasureDefinitions with CDS mapping:
#+BEGIN_SRC python
cms2019 = MeasureDefinition.objects.filter(filename__icontains="_2019")
# Clear out any old maps for 2019 measures
for measure in cms2019:
[d.delete() for d in MeasureDefinitionToAvailableCDS.objects.filter(measure_definition__filename__icontains="_2019")]
# Try creating CDS mapping again:
for measure in cms2019:
print "Measure: ", measure.filename
try:
# Look if we hav an old
old_map = MeasureDefinitionToAvailableCDS.objects.get(
measure_definition__filename__icontains=measure.measure_code
)
print "FOUND: measure ID: {0}".format(measure.id)
new_map = old_map
new_map.id = None
new_map.measure_definition = measure
new_map.save()
except MeasureDefinitionToAvailableCDS.DoesNotExist:
print "MISSING: measure ID: {0}".format(measure.id)
#settings = {
# "settings_label": "{0}: {1}".format(measure.measure_code, measure.display_name),
# "measure_definition": measure,
# "cds_id": measure.measure_code,
# "sequence": 0,
#}
#new_map = MeasureDefinitionToAvailableCDS.objects.create(**settings)
#new_map.save()
#+END_SRC
It appears that sometimes there are multiple MeasureDefinitions ...
DONE Help Ed figure out discrepancy in care gap external patient references
CLOSED: SCHEDULED:
DONE Debug issue with QRDA report generation with many physicians
CLOSED:
#+BEGIN_SRC python
from datetime import datetime
from elation.quality_measures.reporting.elation_reports import CQMQuery
measures = MeasureDefinition.objects.filter(filename__icontains='_2018')
physician_ids=[59722855874562,59722856202242,59722856464386,59722856857602,125877370945538,59722857381890,59722858233858,123486410309634,123486045208578,64702264311810,47298427748354,59722858758146,43479571693570,59722859151362,64227329966082,59722859479042,59722860724226,47298544402434,59722861379586,59722861641730,59722862428162,66635581095938]
cqm_results=CQMQuery(physician_ids=physician_ids, measurement_period_type_idx=2, start_date=datetime(2018,1,1), measure_definitions=measures)
#+END_SRC
Never got to the bottom of why that report generator is slow, but I did figure
out that the timeout we were experiencing was not nginx or uwsgi, but rather the
load balancer in EC2. Once I bumped that up, the reports would generate. They'd
just take forver.
Reporting generation urls
+ login as lucy.li+unimplemented@elationemr.com:pass1word
DONE Get patient CQM report generating working on kube
CLOSED: SCHEDULED: <2019-01-14 Mon 9:00>
:LOGBOOK:
CLOCK: -- => 1:36
:END:
DONE Ensure the care gap refactor branch is merged with Ed's help
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:15
:END:
DONE Why is the QRDA3 code failing saying the wrong measure GUID
CLOSED: SCHEDULED:
- JIRA
- https://elationhealth.atlassian.net/browse/RM-4172
This appears to be due to a measure (CMS166v7) which is not supported in 2018
according to a github post.