Some measurements are measured in different ways: Waist Circumference by NCFS, Waist Circumference by NHANES, Waist Circumference by WHI etc.

To deal with this we need to change the measurement page to accept LOINC codes from another source than just the URL param (from react-router).

This would involve changing the react-router config and having a dictionary somewhere of measurement => LOINC codes (1-many) mapping to pull from.

After the promise is resolved through the thennable function, if the page is changed, it makes another API call on the next then.

Possible fix: resolve the promise after the first call and then the values (just have to figure out exactly how this works)-

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/resolve

Doesn't function properly, currently using false as a default

should not affect the rest of the state of dashboard, should be a simple accordion (e.g. click on a risk tile, then click on a graph, then click to put away teh graph)

needs to be made smaller

Can we change the ratio between top and bottom part of the risk score detail view? I can barely fit a single timeline into the available space on my 15" display. On smaller displays there is not enough room to even fit a single timeline.

to create the issue search for [

This is an issue since it makes the UI slow, and will get worse the more graph widgets we add.

Respective code snippet in Past-To-Future-Graph.js:

target: "data",
eventHandlers: {

	onMouseDown: (evt) => {
		//console.log("on mouse down triggered: ", evt);
		return [
		{
      target: "data",
      mutation: (props) => {
      	this.func2 = this.boundFunction.bind(this);
      	
      	document.addEventListener('mousemove', this.func2);

        return null;
      }
    }];},

	onMouseUp: (evt) => {
		console.log("on mouse up triggered: ", evt);
		return [
		{
      target: "data",
      mutation: (props) => {
			document.removeEventListener('mousemove', this.func2);

      }
    }];}  
}
}]}```

Changing the past date while the timeline view is open will update the blue marker in the detail view (top) but not in the overview (bottom).

Currently, to get the min/max/refRange and individual observation results for graphs on the Measurement Page we are finding the necessary measurements once.

This becomes unwieldy with more measurements (codes) so the data model needs to be redesigned to handle both the single and the multiple case.

These are the current fields that are necessary (however, they are all individual props):

measurement1: {
    minVal:0
    maxVal:100
    referenceRange:[30,40]
    dataPoints:[{x:timePoint1, y:measurementValue1},{x:timePoint2, y:measurementValue2},{x:timePoint3, y:measurementValue3},{x:timePoint4, y:measurementValue4}]
}
measurement2: {...}
measurement3: {...}
}

We need to make the above model extensible in case the graphs need more features at some point.

Designed like the following, the method will be extensible for new risk scores and will automatically parse observation and condition resources, and extra patient resource information (age, gender).

The risk scores are being calculated differently on different pages...look into this in the morning.