Robert,
Thank you for the additional information on how to reproduce the problem you were seeing. I have followed your instruction and I was able to see the same re-ordering of the panel measurement columns (see image below).
I talked to the development team and I found out that the current algorithm looks at each test in turn. For each test, the code figures out what columns are present - not all measurements need be provided. With this code logic, the tests that are displayed first dictate the ordering of the columns.
The idea is that test results will tend to be 'homogenous' and if the first measurements have measurements missing then it is likely that they're missing from consecutive tests. It wouldn't be reasonable to make room for all possible ten values of a blood glucose panel entry, if only a subset is being recorded...
I have passed along your suggestion that the measurement ordering used in the definition of the panel should be preserved if possible.
Thanks also for the suggestion for the blood glucose measurement display. It is actually possible for more than the ten measurements to be required in a day, especially if before and after measurements are being taken, as well as insulin doses. HealthFrame re-orients the measurement results to display one row per measurement type and value.
There may be some flexibility with specific test result reporting with the new technology we're developing, but in particular, we've also been thinking about the ability to have different 'display' values for measurement types - as you suggest using '1st', etc. It is not clear yet how that might be configured, but it is part of the configuration support we're discussing.
Thanks!
Support
