Journal of Medical and Surgical Urology – Data Archiving Permissions

Journal of Medical and Surgical Urology supports data transparency while respecting ethical, legal, and privacy constraints in clinical and surgical datasets.

Authors should include a clear data availability statement describing where data are stored, how access is granted, and what restrictions apply.

When public release is not feasible, controlled access pathways should be documented with request process details and expected timelines.

• Repository name, accession or persistent identifier, and stable access URL where available.
• Description of dataset scope and whether raw, processed, or aggregated data are provided.
• Access conditions including open, controlled, embargoed, or case-by-case review procedures.
• Any legal, ethical, or contractual restrictions that affect redistribution rights.
• Contact route for access requests when direct public release is not allowed.
• Version control information if data or code may be updated post-publication.

Authors should ensure data statements are aligned with local ethics approvals and patient consent language, especially for sensitive procedural and outcome data.

If data are available only under restricted conditions, explain the rationale transparently to maintain reader trust in study governance.

Transparent archiving practices help reviewers and readers evaluate whether conclusions are robust and methodologically defensible.

Data access planning also reduces post-publication friction for institutions, evidence synthesis teams, and policy organizations.

When code and datasets are prepared early, manuscript revisions are typically smoother because analytical assumptions can be clarified quickly.

JMSU may request additional clarification if data statements are incomplete, inconsistent with ethics approvals, or unclear about access procedures.

Data statements should include repository path, access conditions, and file structure notes for practical reuse.

Controlled-access datasets need clear request pathways and expected review timelines for external researchers.

Versioning policy should be documented if archived datasets are updated post-publication.

De-identification strategy must balance participant privacy and analytical utility in shared files.

Code and software environment notes substantially improve reproducibility for secondary analyses.

Data statements should include repository path, access conditions, and file structure notes for practical reuse.

Controlled-access datasets need clear request pathways and expected review timelines for external researchers.

Versioning policy should be documented if archived datasets are updated post-publication.

De-identification strategy must balance participant privacy and analytical utility in shared files.

Code and software environment notes substantially improve reproducibility for secondary analyses.

Data statements should include repository path, access conditions, and file structure notes for practical reuse.

Controlled-access datasets need clear request pathways and expected review timelines for external researchers.

Versioning policy should be documented if archived datasets are updated post-publication.

De-identification strategy must balance participant privacy and analytical utility in shared files.

Code and software environment notes substantially improve reproducibility for secondary analyses.