Scope
Define the specific PHI types, permitted uses, and any processing limitations so data handling expectations are clear and auditable.
A clear agreement reduces compliance risk by allocating responsibilities for PHI protection, breach handling, and regulatory reporting. It documents controls and provides evidence of required contractual protections under HIPAA and HITECH, helping organizations demonstrate compliance during audits.
Covered entities and vendors exchanging PHI must complete or require this agreement before any PHI transfer.
Signing the agreement before PHI exchange and keeping an executed copy supports regulatory defenses and internal compliance workflows.
Define the specific PHI types, permitted uses, and any processing limitations so data handling expectations are clear and auditable.
List permitted disclosures and processing activities, including any restrictions on onward transfers or aggregation for analytics.
Specify administrative, physical, and technical safeguards such as encryption, access controls, and incident response procedures.
Set timelines and reporting channels for suspected breaches, including cooperation obligations for investigations and notifications.
Establish the right to audit, review logs, and receive evidence of compliance, including frequency and scope limits.
Detail data return or destruction procedures upon contract end and steps for continued protection of retained records.
| Field | Configuration |
|---|---|
| Authentication Method | Email + SMS code or KBA for higher assurance |
| Signature Type | Electronic signature with audit trail |
| Audit Trail | Capture IP, timestamp, and action log |
| BAA Requirement | Enforce BAA acceptance before enabling PHI fields |
Select a signing platform that supports required security, integrations, and file formats for your workflows.
Ensure the platform can support retention exports, audit logs, and a signed BAA to meet HIPAA contract and recordkeeping needs.
Ensure the agreement and any required BAA are signed prior to sharing PHI.
Retention periods typically begin on the document creation or execution date.
Provide required consent/consumer disclosure before obtaining electronic signatures for consumer-facing records.
Contract should require prompt cooperation on breach investigations and notifications.
Specify how long audit logs and signed copies remain accessible for inspections.
Complete initial terms, scope, and security requirements.
Privacy and contract teams verify obligations and indemnities.
Obtain authorized signatures and capture audit evidence.
Return or securely destroy PHI per agreement terms.
| Criteria | Electronic Agreement | Paper Agreement |
|---|---|---|
| Legal validity | esign/ueta acceptance | common law enforceable |
| Signature evidence | audit trail and metadata | wet ink on paper |
| Storage requirements | encrypted digital storage | physical filing or safe |
| HIPAA compatibility | yes with baa | yes with baa |
| 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 plan | Varies by plan | Limited trial | Limited trial |
| 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 |