Entity Details
Legal name, DBA, EIN or TIN, physical address, and primary contact information so the certified party can be clearly identified and located for notices or audits.
A formal certification centralizes compliance evidence, shows due diligence during vendor selection or audits, and clarifies responsibilities across parties. It supports HIPAA documentation requirements (45 CFR §164.530(j)), reduces ambiguity in incident response, and provides a consistent record that can be produced for internal or external review.
Organizations that must document HIPAA safeguards use this form to record technical and administrative measures and assign accountability.
Use by these groups ensures consistent, auditable attestations of security measures and clarifies whether a BAA is in place between parties.
A senior executive or legally authorized representative who can bind the organization. They confirm organizational attestations, approve legal obligations, and assume responsibility for the statements on behalf of the entity.
The compliance lead responsible for privacy and security programs. This person verifies technical safeguards, documents risk assessments, and manages responses to requests and breaches documented on the certification.
Legal name, DBA, EIN or TIN, physical address, and primary contact information so the certified party can be clearly identified and located for notices or audits.
Specify the systems, services, or activities covered by the certification and whether the form applies to processing, storage, transmission, or all three categories of PHI handling.
Concise listing of administrative, technical, and physical controls in place, including encryption, access control, logging, patch management, and employee training cadence.
Indicate whether a Business Associate Agreement exists, its execution date, and the party responsible for maintaining or renewing the BAA.
Include the certification effective date and any expiration or review date to define the period covered by the attestation and next review cycle.
Signature, printed name, title, date, and contact information for the signer; include witness or notary lines if required by the organization or state rules.
| Field | Configuration |
|---|---|
| Signer Authentication | Email plus SMS one-time code for moderate assurance |
| Attachment Requirements | Require uploaded BAA or contract PDF before sign-off |
| Reminders and Expiry | Send 3 reminders; expire link after 14 days |
| Audit Trail Options | Enable full event logging and PDF certificate export |
Choose a platform that supports secure storage, audit trails, and the integrations your organization needs.
Ensure the chosen solution can export tamper-evident signed PDFs, maintain audit logs, and support a BAA when PHI is processed.
1–3 business days to gather supporting documentation
3–10 business days for legal and compliance review
7–14 calendar days typical for external signers
Provide certified records within 30 days when requested
Follow HIPAA rules; notify HHS and individuals as applicable
Form and attachments uploaded to the workflow for review
Legal and privacy review of scope, BAA, and controls
Authorized official signs and dates certification
Final signed document stored with audit metadata
They implemented the form during vendor onboarding to centralize PHI handling practices.
A property services firm used certification for contractor access to tenant health accommodations.
| 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 | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| 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 |