Org Web Adapter

Editing journals/2019_03_29.org

* Friday, 3/29/2019
:PROPERTIES:
:ID:       d5ae916b-7cea-4666-8300-77bd99b395c4
:END:
#+BEGIN: clocktable :scope file :maxlevel 2
#+CAPTION: Clock summary at [2019-04-01 Mon 10:00]
| Headline          | Time   |      |
|-------------------+--------+------|
| *Total time*      | *5:18* |      |
|-------------------+--------+------|
| Friday, 3/29/2019 | 5:18   |      |
| \_  Tasks [5/16]  |        | 5:18 |
#+END:
** Tasks [6/6]
*** DONE Write in daily journal :@personal:habit:journal:
:LOGBOOK:
CLOCK: [2019-03-29 Fri 11:27]--[2019-03-29 Fri 11:35] =>  0:08
:END:
*** DONE Figure out why jenkins needs syslog to run tests :@work:jenkins:ci:
:LOGBOOK:
CLOCK: [2019-03-29 Fri 11:35]--[2019-03-29 Fri 13:28] =>  1:53
:END:

I figured out this morning that the env is PYTHONPATH, not PYTHON_PATH for
injecting the route to modules. That took WAY too long to figure out yesterday.
Of course, today's a new day, so it figures I'd solve it quickly this morning.

Now the docker image appears to be missing syslog  ... not sure why hippo makes
so many stupid assumptions about installed software.

And now I've got it running, but half the tests break because I don't have a
working instance of elastic search. wtf.

Next step is to either try excluding fragile tests or spin up an elastic search
docker container. I have access to the EHR storage for Elation, so I can grab
the docker image ... maybe easiest.
*** DONE Try adding elastic search docker instance to Jenkins pipeline
CLOCK: [2019-03-29 Fri 14:50]--[2019-03-29 Fri 16:00] =>  1:10

Turns out I had to convert the declarative pipeline script to a scripted
pipeline script to hook up docker containrs. But now it's totally running,
albeit slowly. Now to find a way to parallelize tests.
*** DONE Bi-weekly prod/dev meeting :@work:meeting:proddev:
:LOGBOOK:
CLOCK: [2019-03-29 Fri 16:00]--[2019-03-29 Fri 16:50] =>  0:42
:END:
*** DONE Research bug in BMI CDS reminders where they don't go away when dimsissed :cms69:@work:cds:bmi:
:LOGBOOK:
CLOCK: [2019-03-29 Fri 13:28]--[2019-03-29 Fri 14:45] =>  1:17
:END:

Interestingly, when you look at the json output from the chart data endpoint,
the one for the SNOMED code related to that is:
#+BEGIN_SRC json
{
  "dob": "02/25/1969 00:00:00 -0800",
  "codes": {
    "2.16.840.1.113883.6.96,183932001": [
      {
        "start": "03/27/2019 09:16:22 -0700",
        "end": "03/27/2019 09:16:22 -0700",
        "source": 140737510440984
      }
    ],
    "2.16.840.1.113883.6.96,306253008": [
      {
        "start": "04/30/2016 17:58:27 -0700",
        "end": null,
        "source": 64067076128
      }
    ],
    "2.16.840.1.113883.6.96,308335008": [
      {
        "start": "03/27/2019 00:00:00 -0700",
        "end": "03/28/2019 09:16:22 -0700",
        "source": 140737510440984
      },
      {
        "start": "03/27/2019 00:00:00 -0700",
        "end": "03/28/2019 09:16:38 -0700",
        "source": 140737511030808
      }
    ]
  },
  "sex": "F"
}
#+END_SRC

Note that 183932001 is the SNOMED code for a procedure not done on purpose, and
it's start date is correct, but the end date is also being populated. Maybe
that's correct? Like it's recording a procedure and it's took zero seconds to
decline the weight measurement of the patient? Or might that be the problem?

Going to force the end-date to be null and see if that corrects it.

Hacking the end date to be null does not work. So that's not the issue. Going to
now check how the calculator determines the denominator exclusions.
*** DONE Write up developer journal and copy to Confluence :@work:journal:
https://elationhealth.atlassian.net/wiki/spaces/~colin.powell/pages/305823777/Work+log
** Journal
Kicked off today with a little bit of work, but mostly a trip to the grocery
store to get ingredients for Emma's birthday cake. I finally figured out the
essence of a dacquise cake this morning, mostly being a meringue with some
icing, whipped cream and chocolate between the layers. I was also able to give
Emma an hour or so in the house along, as I took Nabby and Asa with me. Asa is
such a cutie to bring along on shopping trips.
** Work log