-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Copy link
Labels
app: backendTask implementation touches the backendTask implementation touches the backendsprint: added mid-sprintTask was added mid-sprintTask was added mid-sprinttype: enhancementEnhancement to an existing featureEnhancement to an existing featureworkstream: clinicalTask relates to clinical featuresTask relates to clinical features
Description
As part of the score calibration (previously score ranges) redesign in #518, calibrations will now be stored at a level separate from the score set level. This will allow us to better support features required of investigator provided ranges, but also support calibrations done on data sets at a later point and not necessarily associated with the investigator.
In #518, only users with permission to edit a score set will be able to add calibrations to it. It may be the case though that additional users want to have the ability to create and maintain a set of score calibrations independent of an underlying score set.
We should consider:
- Whether we want some mechanism whereby users must request this ability, to prevent the possible proliferation of irrelevant or poorly curated curations being added to datasets without the investigators permission.
- Whether we want some way to treat these differently from investigator provided and/or internally curated calibrations
- How independently provided calibrations might interact with features necessary for the implementation of Calibrations without score ranges #538
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
app: backendTask implementation touches the backendTask implementation touches the backendsprint: added mid-sprintTask was added mid-sprintTask was added mid-sprinttype: enhancementEnhancement to an existing featureEnhancement to an existing featureworkstream: clinicalTask relates to clinical featuresTask relates to clinical features