{"doi":"10.1186/s13023-024-03120-1","title":"Methodological advances in patient-centered rare disease research: the UTHealth Houston Turner Syndrome Society of the United States research registry","abstract":"BACKGROUND: Many different clinical specialists provide care to patients with Turner syndrome (TS), who have highly variable clinical manifestations. Therefore, a national TS registry is essential to inform a cohesive approach to healthcare and research. In 2015, the Turner Syndrome Society of the United States (TSSUS) created the Turner Syndrome Research Registry (TSRR) to engage directly with community participants who voluntarily provide longitudinal data about their experiences with TS. TSRR projects are collaborative partnerships between people with TS, TSSUS, and researchers. RESULTS: To ensure that registry workflows conform to the data privacy choices of participants, TSSUS collaborated with UTHealth Houston in 2021 to create a new version of the TSRR that completely separates participant health data (stored at UTHealth) and personal identifiers (maintained at TSSUS). We developed an innovative Visual Basic (VB) script that, when embedded into Microsoft Outlook, redirects REDCap surveys through TSSUS to participants by matching registry IDs to participant email addresses. Additionally, the utilization of REDCap allows for portability of data as it is an open source platform. CONCLUSION: In this report, we will highlight three recent changes that more closely align the TSRR with this mission: a unique and equal collaborative partnership between UTHealth and TSSUS, an open-source platform, REDCap, that ensures data portability and compatibility across institutions, and an innovative survey routing system that retains participant confidentiality without sacrificing REDCap survey distribution capabilities to connect researchers with thousands of participants.","journal":"Orphanet Journal of Rare Diseases","year":2024,"id":479640,"datarank":0.10397207708399181,"base_score":0.6931471805599453,"endowment":0.6931471805599453,"self_citation_contribution":0.10397207708399181,"citation_network_contribution":0.0,"self_endowment_contribution":0.10397207708399181,"citer_contribution":0.0,"corpus_percentile":22.178386323199504,"corpus_rank":9377,"citation_count":1,"citer_count":0,"citers_with_citation_signal":0,"citers_with_endowment":0,"datacite_reuse_total":0,"is_dataset":true,"is_dataset_confidence":0.8546,"is_data_producer":false,"deposit_databanks":null,"is_oa":true,"file_count":0,"downloads":0,"has_version_chain":false,"published_date":"2024-01-01","fair_score":50.0,"fair_percentile":62.702537450321,"algorithm_id":"datarank_citation_only_1hop_v6","ranking_scope":"data_only","authors":[{"id":1319067,"name":"Cindy Scurlock","orcid":null,"position":1,"is_corresponding":false},{"id":544030,"name":"Siddharth K. Prakash","orcid":"0000-0001-6341-9624","position":2,"is_corresponding":false},{"id":1253493,"name":"Sara Mansoorshahi","orcid":"0009-0002-9668-5640","position":0,"is_corresponding":true}],"reference_count":16,"raw_metadata":null,"created_at":"2026-07-19T02:06:54.284166Z","pmid":"38468317","pmcid":"PMC10929126","fwci":null,"citation_percentile":null,"influential_citations":0,"oa_status":null,"license":null,"views":0,"total_file_size_bytes":0,"version_count":0,"fair_f":11.1111,"fair_a":68.75,"fair_i":40.0,"fair_r":58.3333,"fair_zscore":0.6155,"fair_rationale":{"fair_score":50.0,"has_llm":true,"taxonomy_version":"fair_taxonomy_v5","dimensions":{"F":{"name":"Findable","score":11.11,"criteria":[{"key":"f_dataset_pid","label":"Persistent identifier for the data","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No persistent identifier (DOI, accession, handle, etc.) is given for the registry data.","anchors":["RDA-F1-01D — FAIR Data Maturity Model: 'Data is identified by a persistent identifier' (priorit","RDA-F1-02D — FAIR Data Maturity Model: 'Data is identified by a globally unique identifier'","FsF-F1-02D — F-UJI/FAIRsFAIR: 'Data is assigned a persistent identifier'"],"scored":true,"signal":null},{"key":"f_repository_named","label":"Named repository","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No data repository is named; the data are held within the article and supplementary material. [majority verdict 'no' (4/5 passes agreed)]","anchors":["RDA-F4-01M — FAIR Data Maturity Model: metadata is offered so it can be harvested and indexed (","NIH DMS Policy Element 4 (NOT-OD-21-014) — name the repository where data will be archived","NSTC Desirable Characteristics of Data Repositories (2022) — 'Long-Term Sustainability', 'Reten"],"scored":true,"signal":null},{"key":"f_data_availability_statement","label":"Data-availability statement","kind":"llm","weight":2.0,"fraction":0.5,"verdict":"partial","evidence":"Data generated or analyzed during this study are included in this published article and its supplementary information files. If datasets of interest are not included in this study, they are available upon request to the corresponding author, Dr. Siddharth K. Prakash at siddharth.k.prakash@uth.tmc.edu.","grounded":true,"rationale":"The data availability statement primarily points to the article and supplementary files (Colavizza category 2), with an additional request option.","anchors":["Colavizza, Hrynaszkiewicz, Staden, Whitaker & McGillivray (2020), 'The citation advantage of li","Springer Nature research data policy — Data Availability Statements: standard statement templat","RDA-F3-01M — metadata clearly and explicitly includes the identifier of the data it describes"],"scored":false,"signal":null},{"key":"f_discovery_metadata","label":"Description of the dataset as an object","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":"The initial data included a total of 957 participant records with two instruments: one foundational survey with 73 recoded variables and one instrument with participant contact and privacy preferences.","grounded":false,"rationale":"The paper describes the dataset's content and size in running prose, without an itemised inventory like a section or table. [downgraded to 'no' — no verifiable quote from the paper]","anchors":["RDA-F2-01M — 'Rich metadata is provided to allow discovery' (priority Essential)","FsF-F2-01M — F-UJI: 'Metadata includes descriptive core elements to support data findability'","FsF-R1-01MD — F-UJI: 'Metadata specifies the content of the data'"],"scored":false,"signal":null},{"key":"f_dataset_cited","label":"Dataset formally cited","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No identifier for the dataset appears anywhere in the text, whether in the reference list or body.","anchors":["FORCE11 Joint Declaration of Data Citation Principles (2014) — data should be cited as a first-","RDA-F3-01M — metadata clearly and explicitly includes the identifier of the data it describes","FsF-F3-01M — F-UJI: 'Metadata includes the identifier of the data it describes'"],"scored":true,"signal":null}]},"A":{"name":"Accessible","score":68.75,"criteria":[{"key":"a_data_openly_accessible","label":"Access route free of preconditions","kind":"llm","weight":2.0,"fraction":1.0,"verdict":"yes","evidence":"Data generated or analyzed during this study are included in this published article and its supplementary information files.","grounded":true,"rationale":"The paper states that the data are included in the open-access article and supplementary files, providing an unconditional route. [majority verdict 'yes' (4/5 passes agreed)]","anchors":["RDA-A1.1-01D — 'Data is accessible through a free access protocol'","FsF-A1-01M — F-UJI: 'Metadata contains access level and access conditions of the data'","NSTC Desirable Characteristics of Data Repositories (2022) — 'Free and Easy Access'"],"scored":true,"signal":null},{"key":"a_access_conditions_stated","label":"Access level labelled","kind":"llm","weight":1.0,"fraction":0.5,"verdict":"partial","evidence":"Data generated or analyzed during this study are included in this published article and its supplementary information files.","grounded":true,"rationale":"No explicit access-level label is used; the text describes the action of accessing the data within the article, requiring inference. [majority verdict 'partial' (3/5 passes agreed)]","anchors":["FsF-A1-01M — F-UJI: 'Metadata contains access level and access conditions of the data'","RDA-A1-01M — metadata contains information to enable the user to get access to the data","COAR Controlled Vocabularies — Access Rights v1.0 (open / embargoed / restricted / metadata-onl"],"scored":false,"signal":null},{"key":"a_controlled_access_for_sensitive","label":"Gatekeeper for sensitive data","kind":"llm","weight":0.5,"fraction":0.5,"verdict":"partial","evidence":"TSSR researchers who wish to access TSRR participants or data must submit research proposals to the TSSUS Scientific Advisory Board (SAB) for review.","grounded":false,"rationale":"The paper names the TSSUS Scientific Advisory Board as the institutional gatekeeper for accessing the registry data. [downgraded to 'partial' — no verifiable quote from the paper]","anchors":["NIH Genomic Data Sharing Policy (NOT-OD-14-124) — controlled-access via a Data Access Committee","RDA-A1.2-01D — 'Data is accessible through an access protocol that supports authentication and ","NIH DMS Policy Element 5 (NOT-OD-21-014) — Access, Distribution, or Reuse Considerations (conse"],"scored":false,"signal":null},{"key":"a_timeline_retention","label":"Availability timing & retention","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No sentence in the paper states how long the data will remain available or a persistence commitment. [majority verdict 'no' (4/5 passes agreed)]","anchors":["NIH DMS Plan Element 4 (NOT-OD-21-014) — Data Preservation, Access, and Associated Timelines","NSTC Desirable Characteristics (2022), Organizational Infrastructure: 'Retention Policy'","RDA-A2-01M — 'Metadata is guaranteed to remain available after data is no longer available'"],"scored":false,"signal":null}]},"I":{"name":"Interoperable","score":40.0,"criteria":[{"key":"i_open_nonproprietary_format","label":"Open file format","kind":"llm","weight":1.0,"fraction":1.0,"verdict":"yes","evidence":"registry data were exported from PEER as a tab-delimited text file","grounded":true,"rationale":"The paper names 'tab-delimited text file' (TSV), which is an open, community-standard format. [majority verdict 'yes' (3/5 passes agreed)]","anchors":["FsF-R1.3-02D — F-UJI: 'Data is available in a file format recommended by the target research co","RDA-R1.3-02D — data is expressed in a machine-understandable community standard","RDA-I1-01D — data uses a knowledge representation expressed in a standardised format"],"scored":true,"signal":null},{"key":"i_community_standard_vocabulary","label":"Community standard / vocabulary","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No data or metadata community standard (e.g., MIAME, GO, Dublin Core) is named for the data.","anchors":["RDA-R1.3-01M — 'Metadata complies with a community standard' (priority Essential)","RDA-R1.3-01D — 'Data complies with a community standard'","RDA-I2-01M — '(Meta)data use vocabularies that follow FAIR principles'"],"scored":false,"signal":null},{"key":"i_qualified_references","label":"Identifiers for the resources the data depend on","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No identifier for an external resource (e.g., source dataset, database, code) is given in the text.","anchors":["RDA-I3-01M — '(meta)data include references to other (meta)data'","RDA-I3-03M — 'metadata includes qualified references to other metadata'","FsF-I3-01M — F-UJI: 'Metadata includes links between the data and its related entities'"],"scored":false,"signal":null}]},"R":{"name":"Reusable","score":58.33,"criteria":[{"key":"r_reuse_license","label":"Reuse licence","kind":"llm","weight":2.0,"fraction":1.0,"verdict":"yes","evidence":"The Creative Commons Public Domain Dedication waiver (http://creativecommons.org/publicdomain/zero/1.0/) applies to the data made available in this article, unless otherwise stated in a credit line to the data.","grounded":true,"rationale":"The paper attaches the CC0 Public Domain Dedication licence to the data, which is an open standard licence.","anchors":["RDA-R1.1-01M — 'Metadata includes information about the licence under which the data can be reu","RDA-R1.1-02M — 'Metadata refers to a standard reuse licence'","RDA-R1.1-03M — 'Metadata refers to a machine-understandable reuse licence'"],"scored":true,"signal":null},{"key":"r_provenance_methods","label":"Provenance of the data","kind":"llm","weight":1.0,"fraction":0.5,"verdict":"partial","evidence":"To create TSRR version 2, registry data were exported from PEER as a tab-delimited text file, transformed into a data frame using a custom python script, and imported into UTHealth Houston REDCap after quality control and de-identification (Supplemental 1 Data).","grounded":false,"rationale":"The paper names specific tools and software (PEER, REDCap, custom python script) used to produce the data. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (2/5 passes agreed)]","anchors":["RDA-R1.2-01M — 'Metadata includes provenance information according to community- specific standa","FsF-R1.2-01M — F-UJI: 'Metadata includes provenance information about data creation or generati","W3C PROV-O (W3C Recommendation, 2013) — the entity/activity/agent model of provenance"],"scored":false,"signal":null},{"key":"r_documentation_codebook","label":"Documentation / codebook","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No documentation object (README, data dictionary) is named, and no variable-definition table is provided inside the article.","anchors":["RDA-R1-01M — '(Meta)data are richly described with a plurality of accurate and relevant attribu","FsF-R1-01MD — F-UJI: 'Metadata specifies the content of the data'","NIH DMS Policy Element 3 (NOT-OD-21-014) — Standards (documentation and metadata to accompany t"],"scored":false,"signal":null},{"key":"r_versioning","label":"Snapshot identified","kind":"llm","weight":0.5,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No version token or date is given to identify the snapshot of the data. [majority verdict 'no' (2/5 passes agreed)]","anchors":["DataCite Metadata Schema 4.6 — the 'Version' property","RDA-R1.2-01M — provenance information (which version was used is provenance)","NSTC Desirable Characteristics of Data Repositories (2022) — 'Provenance', 'Retention Policy'"],"scored":true,"signal":null},{"key":"x_code_availability","label":"Analysis code available","kind":"llm","weight":1.0,"fraction":0.5,"verdict":"partial","evidence":"The REDCap survey routing system was created by installing a custom macro in Microsoft Outlook Visual Basic for Apps (VBA, Supplementary 2 Data).","grounded":true,"rationale":"The code is provided as supplementary material, not in a machine-resolvable repository or archive. [majority verdict 'partial' (3/5 passes agreed)]","anchors":["NIH DMS Policy Element 2 (NOT-OD-21-014) — 'Related Tools, Software and/or Code'","FAIR4RS Principles v1.0 (Chue Hong et al., 2022; RDA/FORCE11/ReSA) — FAIR Principles for Resear","FORCE11 Software Citation Principles (Smith, Katz & Niemeyer, 2016, PeerJ CS 2:e86)"],"scored":true,"signal":null},{"key":"x_funding_attribution","label":"Funder and award number","kind":"llm","weight":0.5,"fraction":1.0,"verdict":"yes","evidence":"This work was supported in part by NIH/NCATS grants UL1 TR000445 and UL1 TR001105.","grounded":true,"rationale":"The paper gives specific grant numbers (UL1 TR000445, UL1 TR001105) attached to the named funder NIH/NCATS.","anchors":["DataCite Metadata Schema 4.6 — 'FundingReference' property (funderName, funderIdentifier, award","Crossref Funder Registry — canonical funder identifiers for funding metadata","RDA-F2-01M — rich metadata provided to allow discovery (funding is part of the descriptive reco"],"scored":true,"signal":null}]}},"actions":[{"key":"f_dataset_pid","dimension":"F","label":"Persistent identifier for the data","action":"Mint or cite a persistent identifier for the dataset — a repository DOI or an accession from a registered repository — and print it in the paper. A bare URL is not persistent: it is the single most common cause of a dead data link five years after publication. For clinical / human-subjects data, deposit in dbGaP or the European Genome-phenome Archive (EGA).","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No persistent identifier (DOI, accession, handle, etc.) is given for the registry data.","gain":16.67,"priority":"essential","scored":true},{"key":"f_repository_named","dimension":"F","label":"Named repository","action":"Deposit the data in a repository registered in re3data/FAIRsharing (a domain repository such as GEO, SRA, dbGaP, PRIDE, or a generalist such as Zenodo, Dryad, Dataverse) and name it explicitly in the paper. A lab website is not an archive: it has no retention commitment and no accession. For clinical / human-subjects data, deposit in dbGaP or the European Genome-phenome Archive (EGA).","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No data repository is named; the data are held within the article and supplementary material. [majority verdict 'no' (4/5 passes agreed)]","gain":16.67,"priority":"essential","scored":true},{"key":"f_dataset_cited","dimension":"F","label":"Dataset formally cited","action":"Cite the dataset in the reference list like a publication — creator, year, title, repository, DOI/accession — and cite it in-text where it is used. Only a reference- list entry is machine-readable to Crossref/DataCite, and only a citation lets the data earn credit. Cite the clinical / human-subjects repository accession (e.g. from dbGaP or the European Genome-phenome Archive (EGA)) in the reference list.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No identifier for the dataset appears anywhere in the text, whether in the reference list or body.","gain":8.33,"priority":"important","scored":true},{"key":"x_code_availability","dimension":"R","label":"Analysis code available","action":"Publish the analysis code in a public forge, archive a tagged release with a DOI (Zenodo/Software Heritage), and cite that DOI in the paper. NIH DMS Element 2 asks for the tools and code, not only the data — and 'available on request' is not a locator. Archive the analysis code in a versioned repository (GitHub + a Zenodo release DOI).","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"The REDCap survey routing system was created by installing a custom macro in Microsoft Outlook Visual Basic for Apps (VBA, Supplementary 2 Data).","why":"The code is provided as supplementary material, not in a machine-resolvable repository or archive. [majority verdict 'partial' (3/5 passes agreed)]","gain":4.17,"priority":"important","scored":true},{"key":"r_versioning","dimension":"R","label":"Snapshot identified","action":"Version the deposit and cite the exact version analysed (a version-specific DOI, or an accession with its version suffix). A reader reproducing your work against 'the current release' is reproducing it against a different dataset.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No version token or date is given to identify the snapshot of the data. [majority verdict 'no' (2/5 passes agreed)]","gain":4.17,"priority":"useful","scored":true},{"key":"f_data_availability_statement","dimension":"F","label":"Data-availability statement","action":"Replace the statement with the repository template: name the repository and give the accession or DOI (Colavizza category 3). This is the only DAS class associated with a measured citation advantage; 'available on reasonable request' and 'within the article' are not.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"Data generated or analyzed during this study are included in this published article and its supplementary information files. If datasets of interest are not included in this study, they are available upon request to the corresponding author, Dr. Siddharth K. Prakash at siddharth.k.prakash@uth.tmc.edu.","why":"The data availability statement primarily points to the article and supplementary files (Colavizza category 2), with an additional request option.","gain":0.0,"priority":"essential","scored":false},{"key":"f_discovery_metadata","dimension":"F","label":"Description of the dataset as an object","action":"Add a 'Data Records' section: itemise every file in the deposit and every variable or sample it holds, with counts and units. Describe the dataset as an object in its own right, not as a by-product of the findings — this is what makes it discoverable to someone who is not looking for your paper.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":"The initial data included a total of 957 participant records with two instruments: one foundational survey with 73 recoded variables and one instrument with participant contact and privacy preferences.","why":"The paper describes the dataset's content and size in running prose, without an itemised inventory like a section or table. [downgraded to 'no' — no verifiable quote from the paper]","gain":0.0,"priority":"essential","scored":false},{"key":"a_access_conditions_stated","dimension":"A","label":"Access level labelled","action":"State the access level in words, using the standard vocabulary: 'These data are open access' / 'These data are controlled access'. A reader — and a harvester — should not have to infer the access level from the presence of a download link.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"Data generated or analyzed during this study are included in this published article and its supplementary information files.","why":"No explicit access-level label is used; the text describes the action of accessing the data within the article, requiring inference. [majority verdict 'partial' (3/5 passes agreed)]","gain":0.0,"priority":"important","scored":false},{"key":"i_community_standard_vocabulary","dimension":"I","label":"Community standard / vocabulary","action":"Adopt and NAME your domain's data standard — the minimum-information checklist, metadata schema, or ontology your community uses (MIAME/MINSEQE, ISA-Tab, BIDS, an OBO ontology, HL7 FHIR/OMOP) — and say which one you followed. A reporting checklist standardises your paper; it does nothing for your data. In clinical / human-subjects, describe the data with OMOP CDM, CDISC SDTM or HL7 FHIR.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No data or metadata community standard (e.g., MIAME, GO, Dublin Core) is named for the data.","gain":0.0,"priority":"important","scored":false},{"key":"r_provenance_methods","dimension":"R","label":"Provenance of the data","action":"Name the instruments, kits, and software — with versions — that produced the data, not just the verbs. 'Reads were aligned' is not provenance; 'aligned with STAR v2.7.9a to GRCh38' is, because someone else can rerun it.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"To create TSRR version 2, registry data were exported from PEER as a tab-delimited text file, transformed into a data frame using a custom python script, and imported into UTHealth Houston REDCap after quality control and de-identification (Supplemental 1 Data).","why":"The paper names specific tools and software (PEER, REDCap, custom python script) used to produce the data. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (2/5 passes agreed)]","gain":0.0,"priority":"important","scored":false},{"key":"r_documentation_codebook","dimension":"R","label":"Documentation / codebook","action":"Ship a README and a data dictionary IN the deposit — every file, every variable, its units, its allowed values, its missing-value codes. It is the cheapest single thing that makes a dataset usable by someone who was not in the lab, and a table buried in the article does not travel with the data.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No documentation object (README, data dictionary) is named, and no variable-definition table is provided inside the article.","gain":0.0,"priority":"important","scored":false},{"key":"a_controlled_access_for_sensitive","dimension":"A","label":"Gatekeeper for sensitive data","action":"Route sensitive data through an institutional gatekeeper — deposit in a controlled- access repository (dbGaP, EGA) with a Data Access Committee and a published DUA — rather than through the corresponding author's inbox. An author-gated dataset dies with the author's email address, and 'on reasonable request' has been shown repeatedly not to yield data. For sensitive/human clinical / human-subjects data, use a controlled-access repository such as dbGaP or EGA.","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"TSSR researchers who wish to access TSRR participants or data must submit research proposals to the TSSUS Scientific Advisory Board (SAB) for review.","why":"The paper names the TSSUS Scientific Advisory Board as the institutional gatekeeper for accessing the registry data. [downgraded to 'partial' — no verifiable quote from the paper]","gain":0.0,"priority":"useful","scored":false},{"key":"i_qualified_references","dimension":"I","label":"Identifiers for the resources the data depend on","action":"Cite by identifier every resource the data depend on — the source datasets' accessions, the reference build (GRCh38 / GCA_000001405.28), the cohort application number, the code DOI — and register those relations on the dataset record (IsDerivedFrom, IsSupplementTo). A name is not a link: it cannot be resolved, versioned, or followed by a machine.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No identifier for an external resource (e.g., source dataset, database, code) is given in the text.","gain":0.0,"priority":"useful","scored":false},{"key":"a_timeline_retention","dimension":"A","label":"Availability timing & retention","action":"State when the data become available AND how long they will be retained — cite the repository's preservation policy. NIH DMS Element 4 asks for both; most papers give neither.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No sentence in the paper states how long the data will remain available or a persistence commitment. [majority verdict 'no' (4/5 passes agreed)]","gain":0.0,"priority":"useful","scored":false}],"suggestions":["Mint or cite a persistent identifier for the dataset — a repository DOI or an accession from a registered repository — and print it in the paper. A bare URL is not persistent: it is the single most common cause of a dead data link five years after publication. For clinical / human-subjects data, deposit in dbGaP or the European Genome-phenome Archive (EGA).","Deposit the data in a repository registered in re3data/FAIRsharing (a domain repository such as GEO, SRA, dbGaP, PRIDE, or a generalist such as Zenodo, Dryad, Dataverse) and name it explicitly in the paper. A lab website is not an archive: it has no retention commitment and no accession. For clinical / human-subjects data, deposit in dbGaP or the European Genome-phenome Archive (EGA).","Cite the dataset in the reference list like a publication — creator, year, title, repository, DOI/accession — and cite it in-text where it is used. Only a reference- list entry is machine-readable to Crossref/DataCite, and only a citation lets the data earn credit. Cite the clinical / human-subjects repository accession (e.g. from dbGaP or the European Genome-phenome Archive (EGA)) in the reference list.","Publish the analysis code in a public forge, archive a tagged release with a DOI (Zenodo/Software Heritage), and cite that DOI in the paper. NIH DMS Element 2 asks for the tools and code, not only the data — and 'available on request' is not a locator. Archive the analysis code in a versioned repository (GitHub + a Zenodo release DOI).","Version the deposit and cite the exact version analysed (a version-specific DOI, or an accession with its version suffix). A reader reproducing your work against 'the current release' is reproducing it against a different dataset."],"model":"deepseek/deepseek-v4-flash","agent_version":"fair_agent_v8","fulltext_source":"unpaywall_pdf"},"fair_model":"deepseek/deepseek-v4-flash","fair_agent_version":"fair_agent_v8","fair_fulltext_source":"unpaywall_pdf","fair_has_llm":true,"fair_computed_at":"2026-07-20T13:35:55.670600Z","clinical_trials":[],"software_tools":[],"db_accessions":[],"linked_datasets":[],"topics":[]}