iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Often, yes—but not automatically. There is no universal rule allowing or forbidding a researcher from belonging to two or more disease research networks. Permission depends on each network’s governance documents, your institution and appointment, sponsor and award terms, the effort you can commit, and what you plan to do with data or materials. Before accepting a second role, obtain a written determination from each network and from the relevant offices at your institution.
Membership itself is only one question. A researcher may be allowed to participate in multiple consortia while still being barred from moving identifiable data, linking datasets, reusing specimens, or publishing without another network’s review. Treat the appointment decision and every proposed data or material transfer as separate approvals.
Why there is no single multiple-network rule
Disease networks are created under different sponsors, cooperative agreements, institutional arrangements, and operating manuals. Their administrators may define eligibility by institution, funded site, disease area, role, or named protocol. Some arrangements can impose conflict-of-interest disclosures, minimum effort, exclusivity, confidentiality, or publication requirements; others may have no express restriction on outside appointments.
Free tools Windows power users keep installed
One-click scans. No signup required.
The 2021 HHS ASPE landscape report on research-network governance identifies legal and contractual terms, data-source conditions, and local policies as factors controlling who may contribute, access, or use network data. That means a permission granted by one consortium cannot be assumed to apply to another. Ask each network’s governance body or administrative contact for its current rule rather than relying on informal precedent.
#1 Best Overall
Also separate a network “membership” from a funded appointment. Your university, hospital, or research institute may require approval for an additional institutional role, outside activity, cost-share commitment, or percentage of effort even when the network itself welcomes you. A grant, cooperative agreement, employment contract, or clinical appointment can contain obligations that are invisible in a public membership page.
Checks to complete before accepting a second network role
1. Eligibility, appointment, and effort
Request the membership policy, governance charter, consortium agreement, and current application instructions for both networks. Confirm:
- Whether individuals may hold concurrent network appointments.
- Whether membership is restricted to named institutions, funded sites, principal investigators, or protocol personnel.
- Who approves an appointment: a steering committee, coordinating center, sponsor, institutional official, or principal investigator.
- Whether the role requires a minimum or maximum percentage of effort, meeting attendance, protocol work, recruitment, or data-management duties.
- Whether outside appointments, competing commitments, or exclusivity clauses must be disclosed.
Compare the requested effort with your award notices, institutional workload records, and employment terms. A second appointment can be permissible in principle but impossible to perform without reducing effort on an existing award. Ask your grants or sponsored-projects office to document how the commitments fit together.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 112. Conflicts of interest and overlapping funding
Disclose scientific, financial, and organizational overlaps under your institution’s conflict-of-interest policy. Include common sponsors, competing products or interventions, overlapping patient populations, shared investigators, and any role that could influence access to data or specimens.
Review every relevant award notice, cooperative agreement, subcontract, and collaborator agreement for confidentiality, intellectual-property, publication, attribution, and data-transfer clauses. NIH policy recognizes that licensing limits attached to materials, proprietary work, and co-funded projects can restrict sharing. Raising a proposed collaboration early can prevent an agreement from imposing restrictions that conflict with either network’s obligations.
3. Participant consent, privacy, and IRB authority
Before proposing any cross-network use, read the consent language for the dataset or specimens. Determine whether participants agreed to:
- Sharing outside the original network or institution.
- Future research beyond the original disease or protocol.
- Genomic analysis or broad data use.
- Linkage with registries, electronic health records, or another network’s dataset.
- Deposit in a named repository or use by investigators in other countries.
Check whether participants selected limitations and whether the proposed use could make a person identifiable when combined with another dataset. De-identification reduces risk but does not, by itself, create permission for open transfer or unrestricted linkage.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Ask the responsible IRB or privacy board whether the new use requires an amendment, a new protocol, a reliance arrangement, or a formal determination that the activity is not human-subjects research. Confirm whether a data-use agreement (DUA), material-transfer agreement (MTA), security review, or controlled-repository approval is required. The originating institution may retain authority even when a second network supplies the scientific question.
4. NIH Data Management and Sharing obligations
The NIH Data Management and Sharing (DMS) Policy covers NIH-funded or NIH-conducted research that generates scientific data, subject to the policy’s scope and applicable exceptions or limitations. It took effect on January 25, 2023. Investigators must submit a DMS Plan and then follow the NIH-approved version.
For a second network, compare the proposed activities with the plan already approved for each award. Ask whether joining the network changes:
- Which scientific data will be collected, preserved, or shared.
- When data must be made available and through which repository.
- Who is responsible for curation, metadata, quality control, and access decisions.
- Whether a change to the approved plan requires prior NIH or institutional approval.
DMS obligations do not override consent limits, privacy law, IRB conditions, confidentiality clauses, DUAs, or repository access controls. If two plans point to different repositories or timelines, obtain written direction from the relevant NIH Institute or Center and your institutional grants office before moving data.
Recommended Free Tools
5. Genomic and disease-specific repository rules
Genomic data can carry additional submission, consent, and access expectations. Check the applicable NIH Institute or Center policy and the repository rules for the project, including dbGaP where required. A disease program may also mandate a particular archive, data dictionary, security standard, or timeline.
Do not assume that a dataset already accepted by one network can be copied into another repository. Verify whether the second network is an authorized recipient, whether the consent permits the transfer, and whether controlled access rather than public release is required. NIH privacy and genomic-data guidance recommends evaluating controlled access for participant data, including data that have been de-identified.
6. Network operating rules
Obtain the current operations manual or consortium agreement for each network. Look for rules on:
- Protocol concept submission, scientific review, and approval.
- Required human-subjects, privacy, data-security, or database training.
- Credentialing, role-based permissions, and audit logs.
- Data dictionaries, coding standards, quality checks, and deadlines.
- Publication review, author eligibility, acknowledgments, attribution, and embargoes.
- External collaborations, data linkage, specimen release, and secondary analyses.
- Departure procedures, account termination, data return, and record retention.
The Rare Diseases Clinical Research Network (RDCRN) illustrates how detailed these rules can be: its Cycle 5 policy describes required database training and attestation before access and sets out network-specific protocol and data-sharing processes. Those provisions are an example of one network’s administration, not a universal requirement for every disease consortium.
Membership is different from sharing data between networks
Many disputes arise because investigators treat a permitted appointment as permission to reuse information. They are separate decisions.
Rank #4
| Activity | Question to answer | Typical approval points |
|---|---|---|
| Hold a scientific or advisory role | Does each network permit concurrent appointments, and can you meet the effort and conflict requirements? | Network governance body, institutional supervisor, grants and conflict-of-interest offices |
| Access another network’s dataset | Are you an eligible user under its access policy, and have you completed required training? | Data-access committee, coordinating center, institutional security or privacy review |
| Transfer or link participant data | Do consent, IRB determinations, privacy safeguards, and the DUA permit this exact transfer and linkage? | Originating and receiving institutions, IRB or privacy board, data custodian, repository |
| Move specimens or proprietary materials | Do the MTA, license, sponsor terms, and consent allow the proposed recipient and use? | Technology-transfer or contracts office, network custodian, ethics review |
| Publish a joint analysis | Which network controls review, authorship, attribution, and embargo timing? | Publication committee, principal investigators, sponsor and institutional officials |
A DUA should identify the permitted dataset, users, purpose, security controls, retention period, breach duties, publication process, and destruction or return requirements. If the agreement permits only a defined analysis, using the same data for a new disease question may require a fresh approval.
Use the same comparison framework for both networks
Build a written matrix before you apply or accept an appointment. Compare these six dimensions:
- Eligibility and approval: Who may join, who votes or signs, and whether approval is tied to a funded site or named investigator.
- Effort and conflicts: Required workload, outside-activity disclosure, competing commitments, and any exclusivity language.
- Control of data and materials: Which institution or sponsor is custodian, who owns intellectual property, and who can authorize release.
- Participant and privacy conditions: Consent scope, IRB or privacy-board oversight, identifiability, security, and controlled-access requirements.
- Reuse and transfer: Permitted linkage, secondary use, international transfer, repository deposit, retention, and destruction.
- Operations and publication: Training, credentials, protocol review, data standards, authorship, attribution, embargoes, and external-collaboration procedures.
Mark each item as “permitted,” “permitted with conditions,” “not permitted,” or “not stated.” For anything marked “not stated,” obtain a written answer; do not infer permission from silence.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A practical due-diligence sequence
- Describe the proposed role. State the network, title, expected effort, protocols, meetings, data access, specimen access, and duration.
- Collect governing documents. Obtain membership terms, charter, operations manual, award or cooperative-agreement provisions, and any publication or data-access policy.
- Map current obligations. List your employment appointment, existing awards, subcontracts, DUAs, MTAs, IRB protocols, and approved DMS Plans.
- Ask targeted questions in writing. Send the same fact pattern to each network administrator and request the policy section or approval authority supporting the answer.
- Obtain institutional review. Route the proposal to grants, contracts, conflict-of-interest, IRB or privacy, information-security, and technology-transfer offices as applicable.
- Resolve data boundaries. Specify whether you will only advise, access a dataset, copy data, link records, receive specimens, or publish an analysis. Each step may need a different agreement.
- Document conditions. Keep approvals, training certificates, access decisions, repository terms, and publication clearances with the project record.
- Recheck after changes. A new protocol, sponsor, repository, disease cohort, country, or type of identifier can invalidate an earlier determination.
Common situations and the safer response
Two networks, no shared data
This is usually the simplest case, but you still need approval for concurrent appointments, effort, conflicts, confidentiality, and publication attribution. Separate credentials and project records help prevent accidental commingling.
One network wants to analyze the other’s dataset
Do not send a copy until consent, IRB or privacy review, the DUA, security controls, and repository rules all cover the proposed analysis. A network administrator’s informal email is not a substitute for the agreement required by the data custodian.
Best Value
- Essential guide to the language of medicine
- Includes 1 000 new words and senses
- Covers the latest brand names and generic equivalents of common drugs
- Pronunciation provided for all entries
Both networks study overlapping patients
Clarify recruitment ownership, duplicate enrollment controls, identifier management, and whether linkage is allowed. Consent may permit participation in one protocol but not record linkage across studies.
An NIH award is involved
Compare both projects with their approved DMS Plans and any Institute- or program-specific repository requirements. Ask NIH and institutional officials before changing the sharing route, timing, dataset definition, or named repository.
Genomic or rare-disease data are involved
Assume heightened review until the applicable consent, genomic-data policy, repository, and controlled-access conditions are confirmed. The scientific value of combining datasets does not remove those obligations.
Warning signs that require escalation
- A network promises that “membership is unrestricted” but will not provide its governing terms.
- Someone suggests that de-identification automatically makes transfer lawful or permissible.
- The proposed analysis is outside the purpose described in the consent or DUA.
- Two sponsors claim overlapping rights to the same specimens, software, or derived data.
- Your effort appears on multiple awards without an institutional reconciliation.
- Publication rules conflict, or one network requires approval before the other permits submission.
- Repository, international-transfer, or security requirements are unclear.
Pause the appointment or transfer and escalate to the network’s governance contact and your institutional grants, contracts, IRB, privacy, security, or conflict-of-interest office. Ask for a written resolution and retain it with the study records.
What to keep in the project file
Maintain a concise decision record containing the proposed role, network contacts, governing documents reviewed, effort calculation, conflict disclosures, consent and IRB determinations, DMS Plan comparison, DUA or MTA, repository decision, training evidence, access approvals, and publication conditions. Record who approved each step and the date. This file makes later audits, staff turnover, and protocol changes easier to manage.
The defensible answer to “Can I join two disease research networks?” is therefore conditional: likely possible in some settings, but never presumed. Obtain network-specific and institution-specific approval, and treat every cross-network use of data or materials as a separate compliance question.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
