Purpose & Scope
Defines the study name, objectives, covered datasets, and permitted uses so transfers align with the research protocol and consent.
A study-specific annex narrows broad agreements into actionable rules for one protocol, reducing ambiguity about PHI handling, auditability, and legal liability.
Key stakeholders who prepare or sign the annex are listed below.
Multiple parties usually approve the annex: legal, privacy, IRB, and operational leads must confirm terms before signatures are collected.
Defines the study name, objectives, covered datasets, and permitted uses so transfers align with the research protocol and consent.
Names the sponsor, data custodian, processors, and any subcontractors and describes each party’s responsibilities for access, security, and reporting.
Lists data elements to be shared, indicating which fields contain PHI, de-identified data, or limited data sets and any required transformations.
Confirms that informed consent and IRB approval allow the proposed uses and specifies consent language or opt-out mechanisms if applicable.
Specifies encryption, access controls, authentication, logging, and breach notification procedures required for the study environment.
Describes audit rights, periodic reporting, retention periods, and obligations in the event of findings or regulatory requests.
| Field | Configuration |
|---|---|
| Signer Order | Sponsor → Site PI → Data Custodian |
| Authentication | Email plus SMS code for non-sensitive signers |
| Conditional Fields | Show PHI-handling details when PHI is selected |
| Audit Trail | Enable full IP, timestamp, and action logging |
Confirm file formats, integrations, and authentication to match your compliance and operational needs.
Ensure the platform captures an auditable certificate of completion and supports any required BAA or 21 CFR Part 11 controls for your study.
IRB approval must be in place before any PHI is shared.
All required parties must sign prior to data access or transfer.
Retention counts from document creation or effective date.
Notify affected parties per policy timelines and regulator rules.
Review annex terms upon protocol amendments or annually.
Circulate and finalize terms with legal and operations teams.
Obtain IRB approval or documented exemption for the study.
Collect required signatures in the agreed signer order.
Begin data sharing only after executed annex and controls are verified.
A university IRB required a detailed PHI handling section
A sponsor needed consistent data use terms across sites
| Criteria | Healthcare Study Annex | Data Use Agreement |
|---|---|---|
| Primary Purpose | study-specific data controls | broad data sharing terms |
| PHI Focus | ||
| Regulatory Attachments | irb and consent details | often dua and baa |
| Typical Length | shorter, protocol-focused | longer, general-use terms |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | No | No | No | No |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |