Org Web Adapter

journals/2019_03_21.org

Thursday, 3/21/2019

ID
14c80bc4-d26d-4bc7-b92d-34d6cb90401e

#+BEGIN: clocktable :scope file :maxlevel 2

#+CAPTION: Clock summary at

| Headline | Time | |

|---------------------+--------+------|

| *Total time* | *4:21* | |

|---------------------+--------+------|

| Thursday, 3/21/2019 | 4:21 | |

| \_ Tasks [4/15] | | 4:21 |

#+END:

Tasks [5/5]

Today's meetings

Team IO standup

DONE Write in personal journal

SCHEDULED:

:LOGBOOK:

CLOCK: -- => 0:09

:END:

DONE Finish draft of narrative of engineer status and desires for mentorship

mentor@personalchallmentor

SCHEDULED:

:LOGBOOK:

CLOCK: -- => 0:46

:END:

Been kicking this task down the road for a while now and I'm not sure why. I

think I need to tighten up the nature of my tasks so they're more easily

accomplished.

DONE Review RM-2292 PR and gather all outstanding tasks

@workcdsrefactor

SCHEDULED:

:LOGBOOK:

CLOCK: -- => 0:50

CLOCK: -- => 0:30

CLOCK: -- => 0:00

:END:

DONE Clean up tests in elation reporting on RM-2292

@workcdsrefactor

SCHEDULED:

:LOGBOOK:

CLOCK: -- => 0:00

CLOCK: -- => 1:58

:END:

I think the issue here is test data not being cleared out and clobbering the

tests.

These tests do not pass:

#+BEGIN_SRC fish

dcedj test elation.quality_measures.tests.reporting.test_elation_reports

#+END_SRC

By itself the test passes:

#+BEGIN_SRC fish

dcedj test elation.quality_measures.tests.reporting.test_elation_reports.TestCQMQuery

#+END_SRC

DONE Write up developer journal and copy to Confluence

@workjournal

SCHEDULED:

:LOGBOOK:

CLOCK: -- => 0:08

:END:

https://elationhealth.atlassian.net/wiki/spaces/~colin.powell/pages/305823777/Work+log

Journal

I could have sworn I smelled pot coming from Peter's room last night. But it was

so faint that I didn't want to make a big deal about it and accuse Peter if that

wasn't what I smelled. Lo and belhold, when Emma went to wake him up he wasn't

even smart enough to remove the towel from his door or close his windows.

I'm not totally sure where we go from here. It's a curious accident that Jessica

is living with us, and so there's actually three parental figures to provide

different insights on the problem. But combined with his decision to just stay

in Bucksport two days ago, and to go back to smoking pot in our house last

night, I'm not totally interested in meeting him where he's at.

In positive news, Emma's birthday is coming up. She's asked for a

https://www.wikiwand.com/en/Dacquoise cake. I'm pretty excited about taking the

project on. She's not sure what she wants for dinner, but I proposed chicken

makhani and her interest was piqued, so we'll see.

Work log

Spent most of the day deep in the bowels of clinical decision supports, trying

to make the RM-2292 merge ready. There were a number of simple fixes, but a few

of the call outs that Andrew and Ed had from our earlier review involved

substantive changes or at the very least refactoring.

I also discovered the limitations of my fix for BMI ... narrowing decision

supports down by date. We only limit by the end date right now, but pinning the

visible CDS by start and end actually allowed the proper flu vaccine CDS to be

presented even without hacking apart the reminders in the measure definitions.

There will still need to be some work to pull reminders out of the measure

definition JSONs.

Along with the RM-2292 fixes I also discovered that the install caregap defs

management command was never re-written to store care gap definitions in the

database. So while we converted a bunch of existing care gaps to get the

definitions from the db, any new ones we install expect their definitions to be

stored in json files on S3. That's madness. And also likely a result of the

helter skelter way we have done work on CDS/CRS.

So tomorrow I'm going to refactor the care gap installation process to stuff

json in the database and hope I can get it done in time test and merge a ticket

that depends on care gaps being installed properly.