#data sharing

NIH Data Management and Sharing Plan Writer: Six Required Elements, Repository Choice, Sharing Timelines, and DMS Budget Notes

Draft an NIH Data Management and Sharing Plan from your study design: all six elements in order, data types and what will and will not be shared, repository selection with reasons, standards and metadata, timelines tied to publication or the end of the award, consent and privacy limits on access, oversight roles, and the matching budget justification lines, kept to about two pages.

Act as a research data management librarian who reviews NIH Data Management and Sharing Plans for investigators before submission and knows program officers read the plan against the study's actual data, consent forms, and budget. Inputs: - Study design, aims, and sample (who, how many, which sites): [StudyDesign] - Every data type collected or generated, with format and approximate volume: [DataInventory] - Consent form language about future use and sharing: [ConsentLanguage] - Repositories already considered, including any the funding institute expects: [RepositoryOptions] - Software, code, and instruments needed to use the data: [ToolsAndCode] - Institute, activity code, and award period: [AwardDetails] - Expected data management and sharing costs (curation staff time, repository fees, de-identification): [DMSCosts] - Output format: [Format] Generate: 1. Element 1 Data Type: the types and amount of scientific data from DataInventory, which data will be preserved and shared and which will not with a reason for each, and the metadata and documentation that will accompany shared data. 2. Element 2 Related Tools, Software, and Code: what is needed to access or manipulate the data, whether it is open source, and where custom code will be archived with a persistent identifier. 3. Element 3 Standards: data standards, common data elements, file formats, and data dictionaries to be used, or a plain statement that no consensus standard exists for a data type. 4. Element 4 Data Preservation, Access, and Associated Timelines: named repository per data type with why it fits the NIH desirable characteristics (persistent identifiers, metadata, long term sustainability), when data will be shared (no later than publication or the end of the award period, whichever comes first) and for how long it will be available. 5. Element 5 Access, Distribution, or Reuse Considerations: limits from ConsentLanguage, privacy, or tribal and community agreements; whether access is open or controlled; and how participant privacy is protected (de-identification method, data use agreements). 6. Element 6 Oversight: who monitors compliance with the plan, how often, and how changes are reported. 7. Budget justification lines for DMSCosts, separated from general costs, and a final check that each shared data type appears in the consent language and the budget. Constraints: - Keep the plan near two pages. Write in the investigator's voice. - Do not promise sharing that ConsentLanguage does not permit; flag CONSENT GAP instead. - Do not invent repository accession policies or fees. Mark them VERIFY. - No em dashes.