{"doi":"10.1371/journal.pone.0306918","title":"Peripheral Arterial Disease prevalence and risk factors in the Eastern Caribbean Health Outcomes Research Network (ECHORN) cohort","abstract":"INTRODUCTION: Peripheral arterial disease (PAD) indicates generalised atherosclerotic disease but is often asymptomatic. The prevalence and potential risk factors of PAD were studied in ECHORN cohort study participants. METHODS: Representative samples of community-dwelling people ≥40 years of age residing in Barbados, Puerto Rico, Trinidad, and the USVI were recruited. The survey included questions on diabetes, hypertension, heart disease and smoking status. Body Mass Index, HbA1c, blood glucose and lipids were determined. Ankle brachial index (ABI) was evaluated in one leg. An oscillometric device measured arm and leg systolic BP simultaneously. ABI classifications were PAD ≤0.90, borderline 0.91 to 0.99, normal 1.00 to 1.40, and non-compressible >0.40. Multivariable logistic regression tested associations of potential risk factors with PAD. RESULTS: Of 2772 participants (mean age 57.3, 65.2% female), 35.8% were overweight, 38.1% obese, 32.4% had diabetes, 60% hypertension, and 15.4% reported heart. ABI prevalence (95% CI) by category was PAD 4.4% (3.6%, 5.1%), borderline 5.2% (4.4%, 6.1%), normal 87.0% (85.8%, 88.3%) and noncompressible 3.4% (2.7%, 4.0%). Female sex (OR 1.72, 95% CI 1.07 to 2.77), diabetes (OR 2.23, 95% CI 1.47 to 3.4), heart disease history (OR 1.74, 95% CI 1.07 to 2.83) and less than high school education vs having a university degree (OR 2.49, 95% CI 1.19 to 5.22) were independently associated with PAD. CONCLUSIONS: Testing one leg only would underestimate PAD prevalence. Increasing the ABI cutoff for identifying PAD to <1.0 when using oscillometric devices is suggested by some studies but would more than double the estimated prevalence. Guidelines need to address this issue. Female sex and lower educational attainment are important considerations when screening. While diabetes and a history of heart disease were confirmed as risk factors, the lack of association of increasing age and cigarette smoking with PAD was unexpected.","journal":"PLoS ONE","year":2024,"id":451694,"datarank":0.20794415416798362,"base_score":1.3862943611198906,"endowment":1.3862943611198906,"self_citation_contribution":0.20794415416798362,"citation_network_contribution":0.0,"self_endowment_contribution":0.20794415416798362,"citer_contribution":0.0,"corpus_percentile":35.18991258606018,"corpus_rank":8206,"citation_count":3,"citer_count":2,"citers_with_citation_signal":0,"citers_with_endowment":0,"datacite_reuse_total":0,"is_dataset":true,"is_dataset_confidence":0.6206,"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":12.5,"fair_percentile":28.767960868236013,"algorithm_id":"datarank_citation_only_1hop_v6","ranking_scope":"data_only","authors":[{"id":702511,"name":"Deron Galusha","orcid":"0000-0003-1136-6422","position":1,"is_corresponding":false},{"id":1100579,"name":"Josefa L. Martinez‐Brockman","orcid":"0000-0002-2953-8168","position":2,"is_corresponding":false},{"id":1273591,"name":"Euclid Morris","orcid":null,"position":3,"is_corresponding":false},{"id":724376,"name":"Saria Hassan","orcid":"0000-0003-0700-9529","position":4,"is_corresponding":false},{"id":797986,"name":"Rohan G. Maharaj","orcid":"0000-0001-8319-8187","position":5,"is_corresponding":false},{"id":797987,"name":"Cruz M. Nazario","orcid":"0000-0002-5753-4738","position":6,"is_corresponding":false},{"id":797988,"name":"Maxine Nunez","orcid":"0009-0007-4379-5172","position":7,"is_corresponding":false},{"id":105807,"name":"Marcella Nuñez-Smith","orcid":"0000-0003-2797-4756","position":8,"is_corresponding":false},{"id":787724,"name":"O Peter Adams","orcid":"0000-0002-6707-6769","position":0,"is_corresponding":true}],"reference_count":38,"raw_metadata":null,"created_at":"2026-07-19T02:02:45.951080Z","pmid":"39186495","pmcid":"PMC11346651","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":50.0,"fair_i":0.0,"fair_r":16.6667,"fair_zscore":-0.8688,"fair_rationale":{"fair_score":12.5,"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":"The paper does not provide any persistent identifier (DOI, Handle, ARK, repository accession) for its own dataset.","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":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","grounded":true,"rationale":"The paper names a committee (DASR) and a website, but no repository (e.g., GEO, Dryad) is named as the holder of the data.","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":"At the time that this cohort was empaneled, the public sharing of data was not anticipated. The authors therefore did not indicate to any of the five Institutional Review Boards they applied to for ethical approval, that the data would be shared. The informed consent form stated specifically: “Only aggregated (everybody who participates will have their information joined together so no one person can be identified) anonymous (no names) data will be presented in any publicly disseminated materials.” The authors believe making data in a non-aggregated form freely available in a public repository will breach this commitment and the IRB approvals we obtained. Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","grounded":true,"rationale":"The data-availability statement points to a request process (committee contact) rather than to a repository record, placing it in Colavizza category 1.","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":"Participants completed a baseline survey which included questions on diabetes and hypertension diagnosis. Survey items were self-administered on a tablet computer. The physical examination included measurement of weight and height which were used to calculate Body Mass Index (BMI).","grounded":false,"rationale":"The dataset content is described in running prose within the methods section, but no itemised inventory (section, table, or list) of files or variables is provided. [downgraded to 'no' — no verifiable quote from the paper] [majority verdict 'no' (3/4 passes agreed)]","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 or link for the dataset appears anywhere in the paper, not in the body text nor in the reference list.","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":50.0,"criteria":[{"key":"a_data_openly_accessible","label":"Access route free of preconditions","kind":"llm","weight":2.0,"fraction":0.5,"verdict":"partial","evidence":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","grounded":true,"rationale":"The text specifies a followable access process with a precondition (application to the DASR committee), which is a defined controlled-access procedure, not a discretionary request to a person.","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":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","grounded":true,"rationale":"The paper describes an action (submit a request) but applies no explicit access-level label such as 'open access' or 'restricted access', so the access level must be inferred. [majority verdict 'partial' (3/4 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":1.0,"verdict":"yes","evidence":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","grounded":true,"rationale":"The paper names an institutional gatekeeper, the ECHORN Data Access and Scientific Review committee, for controlled access to the human-subject data.","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 when the data become available or how long they persist; only a request process is described.","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":0.0,"criteria":[{"key":"i_open_nonproprietary_format","label":"Open file format","kind":"llm","weight":1.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No file format is named for the released data; the paper does not describe any data deposit.","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, Dublin Core, ontology) is named in the paper; only clinical guidelines are referenced.","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":"The paper does not provide an identifier (accession, DOI, RRID) for any external resource that the data depend on or derive from; reference-list entries are for other literature, not data resources.","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":16.67,"criteria":[{"key":"r_reuse_license","label":"Reuse licence","kind":"llm","weight":2.0,"fraction":0.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"No licence or terms document is named for the data; the CC-BY license applies to the article only, not the data.","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":"A WatchBP® (Microlife Switzerland) office automated ABI machine was used to determine both BP and ABI.","grounded":false,"rationale":"The paper names specific instruments (WatchBP) and software (SAS 9.4) used to produce the data. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (3/4 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":"ABI values were categorised into PAD (ABI ≤0.90), borderline (ABI 0.91.-0.99), normal (ABI 1.00 to 1.40) and noncompressible (ABI >1.40)","grounded":false,"rationale":"Variable definitions are provided within the article text (e.g., ABI categories), but no separate documentation object (README, codebook) is named as accompanying the data. [downgraded to 'no' — no verifiable quote from the paper] [majority verdict 'no' (3/4 passes agreed)]","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 provided to pin a snapshot of the data; the data are not deposited in a versioned repository.","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.0,"verdict":"no","evidence":null,"grounded":false,"rationale":"The paper does not mention the availability of any code written for the study; only third-party software (SAS) is named.","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 by the National Institute on Minority Health and Health Disparities through the Eastern Caribbean Health Outcomes Research Network (ECHORN)-U24MD006939 and through the Yale Transdisciplinary Collaborative Center for Health Disparities Research focused on Precision Medicine (Yale-TCC)-U54MD010711. Support was also provided by the CTSA Grant Number KL2 TR001862 and KL2 RR024138 from the National Center for Advancing Translational Science (NCATS), a component of the National Institutes of Health (NIH).","grounded":true,"rationale":"The paper explicitly lists grant numbers (U24MD006939, U54MD010711, KL2 TR001862, KL2 RR024138) attached to named funders.","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":"The paper does not provide any persistent identifier (DOI, Handle, ARK, repository accession) for its own dataset.","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":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","why":"The paper names a committee (DASR) and a website, but no repository (e.g., GEO, Dryad) is named as the holder of the data.","gain":16.67,"priority":"essential","scored":true},{"key":"r_reuse_license","dimension":"R","label":"Reuse licence","action":"Attach a standard, machine-readable open licence to the deposit — CC0 or CC BY, which is what Horizon Europe and most funders expect — and print the licence identifier in the paper. 'Free to use' is not a licence: it grants nothing a reuser's institution can rely on.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No licence or terms document is named for the data; the CC-BY license applies to the article only, not the data.","gain":16.67,"priority":"essential","scored":true},{"key":"a_data_openly_accessible","dimension":"A","label":"Access route free of preconditions","action":"Remove the precondition or justify it. Release the data at publication with no embargo, no registration wall, and no approval step — NIH's zero-embargo public- access rule (NOT-OD-25-101) has already made 'available at publication' the federal baseline for the article; the data should not lag behind it. For clinical / human-subjects data, deposit in dbGaP or the European Genome-phenome Archive (EGA).","anchors":["yes","partial","no"],"verdict":"partial","current":0.5,"evidence":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","why":"The text specifies a followable access process with a precondition (application to the DASR committee), which is a defined controlled-access procedure, not a discretionary request to a person.","gain":8.33,"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 or link for the dataset appears anywhere in the paper, not in the body text nor in the reference list.","gain":8.33,"priority":"important","scored":true},{"key":"i_open_nonproprietary_format","dimension":"I","label":"Open file format","action":"Release the data in an open, community-standard format (CSV/TSV, JSON, HDF5, NetCDF, FASTQ, VCF, NIfTI…) instead of — or alongside — any proprietary or instrument-native format, and name the format in the paper. A dataset that needs a €2,000 licence to open is not reusable.","anchors":["yes","partial","no"],"verdict":"no","current":0.0,"evidence":null,"why":"No file format is named for the released data; the paper does not describe any data deposit.","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":"no","current":0.0,"evidence":null,"why":"The paper does not mention the availability of any code written for the study; only third-party software (SAS) is named.","gain":8.33,"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 provided to pin a snapshot of the data; the data are not deposited in a versioned repository.","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":"At the time that this cohort was empaneled, the public sharing of data was not anticipated. The authors therefore did not indicate to any of the five Institutional Review Boards they applied to for ethical approval, that the data would be shared. The informed consent form stated specifically: “Only aggregated (everybody who participates will have their information joined together so no one person can be identified) anonymous (no names) data will be presented in any publicly disseminated materials.” The authors believe making data in a non-aggregated form freely available in a public repository will breach this commitment and the IRB approvals we obtained. Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","why":"The data-availability statement points to a request process (committee contact) rather than to a repository record, placing it in Colavizza category 1.","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":"Participants completed a baseline survey which included questions on diabetes and hypertension diagnosis. Survey items were self-administered on a tablet computer. The physical examination included measurement of weight and height which were used to calculate Body Mass Index (BMI).","why":"The dataset content is described in running prose within the methods section, but no itemised inventory (section, table, or list) of files or variables is provided. [downgraded to 'no' — no verifiable quote from the paper] [majority verdict 'no' (3/4 passes agreed)]","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":"Reasonable requests for access to ECHORN data can be made to the ECHORN Data Access and Scientific Review (DASR) committee via the authors' website ( https://www.echorn.org/request-echorn-data ) or via email to the ECHORN Coordinating Center ( ecc@yale.edu ).","why":"The paper describes an action (submit a request) but applies no explicit access-level label such as 'open access' or 'restricted access', so the access level must be inferred. [majority verdict 'partial' (3/4 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, Dublin Core, ontology) is named in the paper; only clinical guidelines are referenced.","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":"A WatchBP® (Microlife Switzerland) office automated ABI machine was used to determine both BP and ABI.","why":"The paper names specific instruments (WatchBP) and software (SAS 9.4) used to produce the data. [downgraded to 'partial' — no verifiable quote from the paper] [majority verdict 'partial' (3/4 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":"ABI values were categorised into PAD (ABI ≤0.90), borderline (ABI 0.91.-0.99), normal (ABI 1.00 to 1.40) and noncompressible (ABI >1.40)","why":"Variable definitions are provided within the article text (e.g., ABI categories), but no separate documentation object (README, codebook) is named as accompanying the data. [downgraded to 'no' — no verifiable quote from the paper] [majority verdict 'no' (3/4 passes agreed)]","gain":0.0,"priority":"important","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":"The paper does not provide an identifier (accession, DOI, RRID) for any external resource that the data depend on or derive from; reference-list entries are for other literature, not data resources.","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 when the data become available or how long they persist; only a request process is described.","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).","Attach a standard, machine-readable open licence to the deposit — CC0 or CC BY, which is what Horizon Europe and most funders expect — and print the licence identifier in the paper. 'Free to use' is not a licence: it grants nothing a reuser's institution can rely on.","Remove the precondition or justify it. Release the data at publication with no embargo, no registration wall, and no approval step — NIH's zero-embargo public- access rule (NOT-OD-25-101) has already made 'available at publication' the federal baseline for the article; the data should not lag behind it. 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."],"model":"deepseek/deepseek-v4-flash","agent_version":"fair_agent_v8","fulltext_source":"epmc_xml"},"fair_model":"deepseek/deepseek-v4-flash","fair_agent_version":"fair_agent_v8","fair_fulltext_source":"epmc_xml","fair_has_llm":true,"fair_computed_at":"2026-07-20T13:14:35.355798Z","clinical_trials":[],"software_tools":[],"db_accessions":[],"linked_datasets":[],"topics":[]}