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
To reflect full meaning of the measurement, it should be shown with it's value_as_concept_id or if the result is numeric, the value is interpreted based on the reference range with such a values generated: "below", "within" and "above normal range".
Currently the only variables are shown.
The feature extractor already supports the variables with values, it was implemented in FeatureExtraction 3.6.0.
Also, does Compare characterization use the variable+value pairs, or only variables?
The text was updated successfully, but these errors were encountered:
The current implementation within CD is to only use the presence or not of a covariate, so this would be a significant enhancement.
How we implement this is probably going to be some extra functionality specific to measurements though but the use of the "Below, within, above" pattern in FE > 3.6.0 might turn out to be fairly striaghtforward.
Also, does Compare characterization use the variable+value pairs, or only variables?
It will only be using variables currently.
I will add this to our release roadmap as as this could be extremely useful!
To reflect full meaning of the measurement, it should be shown with it's value_as_concept_id or if the result is numeric, the value is interpreted based on the reference range with such a values generated: "below", "within" and "above normal range".
Currently the only variables are shown.
The feature extractor already supports the variables with values, it was implemented in FeatureExtraction 3.6.0.
Also, does Compare characterization use the variable+value pairs, or only variables?

The text was updated successfully, but these errors were encountered: