- ID
- ed454fa8-87c4-4210-95ca-d8ad5d8d047b
April, 4 2019
Thursday, 4/04/2019
#+BEGIN: clocktable :scope file :maxlevel 2
#+CAPTION: Clock summary at
| Headline | Time | |
|---------------------+--------+------|
| *Total time* | *2:52* | |
|---------------------+--------+------|
| Thursday, 4/04/2019 | 2:52 | |
| \_ Tasks [5/12] | | 2:52 |
#+END:
Tasks [7/7]
DONE Write in daily journal
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:44
:END:
DONE Set tasks for the day
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:10
:END:
Going back to using projects.org to manage projects and set things as "NEXT"
with this daypage being my work list. That allows me to keep things less
cluttered. When I run out of tasks on ths list (which should happen ever day) I
dip back into the agenda well for the next tasks.
DONE Remove warning for CQM year in javascript
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:14
:END:
Notes
In addition to removing the warning, we should check on how the year value is
cached in localstorage. That may be causing issues with how years display.
---
Ended up just cutting out the display of the message. There's too much that uses
the localstorage year to feel safe just pulling it out, and the biggest hazard,
having users see CDS for the wrong year without realizing it, becomes basically
a non-problem with the CDS year change triggering CDS recalcs, which I did a
while back.
DONE Figure out why caregaps can't be installed to test deletion
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:45
:END:
Notes
Discovered that that 1210 branch suffered from the same issue as the caregap
importer improvement branch. Namely, that the caregap parsing task was not
registered properly with celery and so never ran. Not sure how that could have
happened, but I pushed up a fix and will need to retest this branch.
DONE FIGmd standup
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:17
:END:
DONE Stand up stage-west for CAIPA caregap imports
CLOSED:
:LOGBOOK:
CLOCK: -- => 17:13
:END:
Notes
Had to totally tear it down and start over.
DONE Assit with setting up a customer with DW access
CLOSED:
:LOGBOOK:
CLOCK: -- => 1:19
:END:
Notes
Figured out what we were missing: https://elationhealth.atlassian.net/wiki/spaces/~josh.wright/pages/274858014/Managing+DW+Jumphost+Users
That allows you to setup SSH keys for the jumphost for folks to connect.
---
Didn't work. Turned out only a handful of Elation employees have access to the
jumphost. Justin, Cameron, Rox and ... Lauren Hill?! I contacted Lauren who's
the only one of four folks not out of office or departed. I'm gonna ask for
Jacob's help tomorrow to get access the box via Lauren's SSH key.
Journal
I'm falling off the wagon again. I had this whole scheme to do daypages, where I
jot down my todo list for a given day and the "work the plan," but I ran
headlong into the issue of where to keep long running tasks. Copy and pasting
your todo list from days past sucks, and isn't very useful for prioritizing
things. I may need to go back to agenda mode with NEXT tasks and such.
I'm also a little discouraged by the weather lately. I have the Bridge the Gap
race coming up, and it's supposed to be rainy and a little cold. That sounds
like a recipe for disaster.
Ended up spending a lot of today just putting out fires at work. After standup,
I spent a little time trying to get the care gap importer to work with XOCOS
and MSFTACO measure definitions, but the importer kept complaining that the
measures didn't exist.
I finally got most of it work, and discovered that deleting measures when there
are patients with open care gaps doesn't work. So it's back to the drawing board
with the delete command. At the very least, I should put in a warning when
deleting that the definition can't be deleted because a patient has an open gap.