Data Scope
Precisely list categories of data, whether PHI, limited datasets, or de‑identified records, and define authorized purposes to avoid ambiguity over permitted analysis, sharing, or re‑use.
A CDA clarifies legal responsibilities, reduces regulatory risk, and documents safeguards required by HIPAA and state law. It preserves patient privacy, limits unauthorized uses, and makes breach response and audit rights explicit, creating a defensible governance record for vendors and covered entities.
Organizations and vendors in clinical operations, IT, and data services commonly prepare and execute CDAs before any PHI exchange.
Parties should involve legal, compliance, and IT/security teams to verify that the CDA aligns with HIPAA requirements and internal risk tolerance before signatures are collected.
Typically a commercial or contracting lead authorized to bind the vendor. This person verifies service scope, technical controls, indemnity clauses, and payment terms, and ensures escalation paths and SLAs are documented before signing on behalf of the vendor.
A senior compliance or privacy officer for the covered entity who confirms HIPAA alignment, BAA needs, permitted uses, and breach notification timelines. Their approval confirms the CDA meets regulatory and organizational privacy policies before execution.
Precisely list categories of data, whether PHI, limited datasets, or de‑identified records, and define authorized purposes to avoid ambiguity over permitted analysis, sharing, or re‑use.
Specify allowed activities (treatment, operations, research) and explicitly prohibit re‑identification, resale, or secondary uses not described in the agreement.
Identify technical and administrative safeguards such as encryption in transit/at rest, access controls, logging, and vulnerability management standards.
Set timelines and procedures for notifying the covered entity and regulators, preservation of evidence, and responsibilities for mitigation and remediation.
Grant audit rights, require periodic security assessments or penetration tests, and define access to logs and remediation tracking.
Require return or secure destruction of data at contract end, define verification of destruction, and preserve limited retention if required by law.
| Field | Configuration |
|---|---|
| Signing Order | Set role sequence so legal and compliance sign before vendor execution. |
| Authentication | Require email plus SMS code or stronger ID proofing for vendor signers. |
| Attachments | Attach BAA, SOW, and security appendices as required documents. |
| Audit Trail | Capture IP, timestamp, and user agent for each action. |
Choose an eSignature platform that supports HIPAA BAAs, secure storage, and the integrations your teams use.
Ensure the selected vendor can provide audit trails, encryption (TLS/AES), and a signed BAA when PHI is involved; align integrations with existing systems for consistent records.
The contract's start date in MM/DD/YYYY format.
Notify affected individuals and HHS without unreasonable delay, no later than 60 days (45 CFR §164.410).
Respond to patient access requests within 30 days (45 CFR §164.524(b)(2)).
Review and renew BAAs annually or when scope changes.
Define frequency (e.g., annual) and notice periods for audits.
| 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 trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA) | Yes (BAA) | Yes (BAA) | No | No |