You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which are collected here : Ref.
"boneAgeMos" is only used if the object is of type : SmartBoneage
But since we are never creating any objects of type SmartBoneage the key "boneAgeMos" is never read thus keeping the BoneAge to be displayed in the Table as always undefined.
@nschwertner Is this a bug or am I missing something?
The text was updated successfully, but these errors were encountered:
This sounds like a bug to me, which probably occurred when the app was adapted to SMART on FHIR (from SMART Classic, which it was written against originally). I can see the data being processed inside the app (for example sample patient Paul Luttrell has some bone age observations), but then it somehow fails to get matched against the height measurements and displayed. You are welcome to contribute a fix for v1 if you work out a solution. We will address this with v2 of the app for sure.
Currently the growth chart app accepts an array of associative arrays containing the key-value pairs :
which are collected here : Ref.
"boneAgeMos" is only used if the object is of type : SmartBoneage
But since we are never creating any objects of type SmartBoneage the key "boneAgeMos" is never read thus keeping the BoneAge to be displayed in the Table as always undefined.
@nschwertner Is this a bug or am I missing something?
The text was updated successfully, but these errors were encountered: