Parties
Identify each legal entity by full legal name, DBA if applicable, physical address, and primary contact for notices; include NPI and DEA where required for credentialing.
The addendum reduces ambiguity about responsibilities for dispensing, claims submission, PHI handling, and security controls. It supports HIPAA compliance by documenting BAAs and access rules, helps align billing and audit processes, and records signature authority so downstream transactions are enforceable under ESIGN and UETA.
Use is most common where contractual clarity, audited PHI handling, or state-specific registration and licensing rules intersect with pharmacy operations.
Operational lead who completes commercial and operational fields, coordinates BAA and security details, verifies DEA and NPI numbers, and ensures the addendum aligns with existing pharmacy policies and payer requirements.
In-house or outside counsel who reviews liability language, indemnity clauses, PHI handling terms, and confirms that the addendum’s signature and amendment provisions comply with ESIGN, UETA, and state contract law.
Identify each legal entity by full legal name, DBA if applicable, physical address, and primary contact for notices; include NPI and DEA where required for credentialing.
Describe specific pharmacy services covered, such as dispensing, medication therapy management, prior authorization support, or clinical trial supply, and whether subcontractors may perform tasks.
List the categories of protected health information that will be created, received, maintained, or transmitted and any limitations on usage or re disclosure.
Specify technical and administrative safeguards, encryption standards, logging, breach notification procedures, and responsibilities for security testing or audits.
Define invoicing procedures, claim submission responsibilities, timelines for payment, dispute resolution, and consequences for billing errors or denied claims.
Include signature blocks with printed name, title, date, and an explicit BAA execution line if PHI exchange will occur; note whether esignatures are acceptable under ESIGN and UETA.
| Field | Configuration |
|---|---|
| Authentication | Email link, SMS code, or stronger KBA |
| BAA Checkbox | Require acknowledgment before signing |
| Signature Order | Sequential or parallel routing options |
| Retention Setting | Automatic archival and versioning enabled |
Confirm the provider offers a Business Associate Agreement, preserves tamper-evident audit logs, and can export signed PDFs and metadata for compliance reviews and audits.
Set as MM/DD/YYYY; determines when obligations commence
BAA must be signed before PHI exchange
Specify first billing cycle and claim submission window
Allow 30–60 days for internal and payer audits
State notice period for changes and effective date
Addendum drafted and exhibits attached for review
Legal and compliance approvals secured
Authorized parties sign and date the document
Systems, access, and billing configured per addendum
| 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 | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A network pharmacy integrated electronic signing for patient consent and supplier addenda to speed processing and centralize records.
A clinic operator used standardized addenda to onboard pharmacies across multiple sites and ensure consistent PHI handling expectations.