Parties & Recitals
Identify the covered entity and business associate clearly, describe the business relationship, and state whether PHI access is expected and why.
Combining an MSA with a BAA creates a single contracting vehicle that clarifies both commercial terms and HIPAA duties, reducing conflicts between payment, liability, and privacy clauses while documenting how PHI will be protected and audited.
Use this agreement when the commercial engagement and HIPAA-required data protections should be documented together to avoid parallel or inconsistent contracts.
Identify the covered entity and business associate clearly, describe the business relationship, and state whether PHI access is expected and why.
Describe services, deliverables, SLAs, and any subprocessors; make PHI-related processing activities explicit and limited to the stated purposes.
Specify technical and administrative safeguards, encryption in transit and at rest, access controls, breach response, and audit rights consistent with HIPAA and 45 CFR §164.308.
Include HIPAA-required BAA provisions: permitted uses and disclosures, minimum necessary, subcontractor flow-down, breach notification timelines, and return or destruction of PHI.
Allocate risk for security incidents, regulatory fines, and third-party claims; include caps, carve-outs for willful misconduct, and insurance requirements.
Define termination for convenience and for cause, transition assistance, and procedures to return or securely destroy PHI on contract end.
| Field | Configuration |
|---|---|
| Order of Signers | Sequence signers to enforce role-based approvals |
| Authentication | Choose email link, SMS code, or stronger verification as required |
| Required Fields | Mark signature, printed name, title, and date as mandatory |
| Audit Trail | Enable comprehensive logs (IP, timestamp, actions) |
Ensure the platform can produce a tamper-evident signed PDF, provide a certificate of completion, and, if handling PHI, execute a BAA with the vendor.
| 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 | Yes limited | Yes limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
When integrating a signature workflow across clinics, consistent PHI protections were essential
A services firm required SOC 2-level controls in both contract and operations
Set as MM/DD/YYYY — governs when obligations start
BAA should be in place before vendor accesses PHI
Prompt breach notice recommended; OCR expects timely reporting
Specify 30–90 day notice for renewal or termination
Maintain records per HIPAA and IRS timelines
Finalize scope, fees, and BAA clauses before signature
Collect authorized signatures and record the effective date
Vendor begins work after BAA and onboarding controls are verified
Return or securely destroy PHI per contract and 45 CFR §164.502