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
Dar’ya will need to dig into this a bit more and understand if/how this can be done, how it can be resourced, etc.
Some time sensitivity here as IDs will be subject of upcoming info sessions. Need to think about messaging here and what an MVP could look like...what are the priority immediate steps rather than a full solution
Dar’ya to create a one-pager to more tightly scope this, considering:
Discussed on 2025.01.06 HTAN DCC Coordination call:
In general, preference for conservative approach to any changes to identifiers, however, recognized that there are opportunities to improve on this from HTAN1. If we are going to make any changes though, need to decide on these ASAP.
Consider whether we actually need to make any changes to the identifiers themselves OR is it preferred to provide improved guidance to centers on how to implement the existing approach?
25-1 Kick-off:
Distinguish between biospecimen (e.g. start with a 0 in the last integer block) and data file ID (e.g. start with a 1 in last integer block)
Need to review latest biospecimen RFC and understand levels of samples are are needed to be captured here (sample, sub-sample, assayed sample) and what we are enforcing here.
Specific guidelines on pooled and TMA assays. This is particularly confusing where we have one data file that represents data from multiple participants. Why have Participant IDs in data file metadata - this can be inferred from the provenance
Identifiers for control and blank samples (this was not straightforward in HTAN1)
Dar'ya will put together a presentation with proposed approaches for discussion on upcoming HTAN DCC call.
24-11/12 Sprint Kick-Off Discussion:
HTAN Identifiers - do these really need to be human readable
TL:DR - Dar'ya will investigate potential options for mint IDs and if ISB can support this.
The text was updated successfully, but these errors were encountered: