All submissions require a data availability statement. Authors should describe where data are stored, how they can be accessed, or why access is restricted.

• Data publicly available in a repository with a persistent identifier
• Data available from the corresponding author on reasonable request
• Data restricted due to ethical or privacy constraints with access under agreement
• Data included within the article and supplementary files

Include repository DOIs when available and provide clear access terms to support reuse.

Data sharing should never compromise participant privacy. When restrictions apply, transparency about access conditions is essential.

• Remove personal identifiers and sensitive metadata
• Confirm consent for data sharing where applicable
• Use controlled access for sensitive clinical datasets
• Describe any embargo periods or access conditions

For imaging data, remove identifiers in file headers and confirm publication consent for any patient images.

Clear data documentation improves reuse, citation, and trust in the findings.

If custom code or statistical scripts were used, consider depositing them alongside datasets with version information and dependencies.

Provide descriptive metadata, variable definitions, and codebooks. Use consistent naming conventions and include units for all variables.

Cite datasets in the reference list when possible to ensure proper attribution and track reuse.

If data are shared under a specific license, include the license terms and reuse conditions in the data availability statement.

Consistent metadata improves discovery and reuse across repositories.

Include dataset identifiers in the reference list and link them in the data availability statement. This supports persistent access and credit for data contributors.

For multi site studies, clearly document ownership and stewardship of shared datasets to avoid access conflicts.

If data are derived from proprietary sources, describe the restrictions and provide a pathway for qualified access when possible.

Clear citation of datasets helps indexing services connect articles with supporting resources.

When possible, cite both dataset and code repositories to support full reproducibility.

Use specific repository names and identifiers rather than generic statements. This improves trust and ensures that readers can locate data efficiently.

If data are restricted, explain the reason and outline the steps required for access approval.

When data are included as supplementary files, describe the content and file formats so readers can interpret and reuse the material.

If licensing restrictions apply, include the license terms and any reuse limitations in the statement.

Clear data access language reduces follow up requests during review and supports compliance with funder policies.

Authors should ensure that repository links remain active and that access requirements are documented clearly.

Data statements should align with ethics approvals and consent conditions.

Clearly noted embargo dates help readers plan access.

Data access clarity reduces reviewer follow up requests.