PDF work on PHI, without shipping it to a third party.
The compliance problem with most PDF tools is not the editing, it is the upload. If a document containing PHI is processed on someone else’s servers you need an agreement covering it. CompendiumPDF does its work locally, so ordinary editing, OCR and redaction never create that exposure.
Why local processing matters for PHI
Ordinary use of CompendiumPDF creates no third-party exposure, because there is no third party in the loop. Editing, OCR, conversion, compression and redaction all happen in the application on your computer.
Two features do transmit data, and only when you deliberately invoke them: license activation sends your email address and a device identifier, and Compendium Sign receives the specific document you choose to send for signature.
Signature workflows
Compendium Sign supports ESIGN/UETA, HIPAA and 21 CFR Part 11 profiles with one-time-password identity verification, and maintains a hash-chained audit trail so tampering with the history is detectable. Signature blocks are added on an appended page rather than overlaid on your content, so a signature can never cover a material term.
Common questions
Do I need a business associate agreement to use it?
For ordinary use there is nothing to cover: documents are processed locally and never reach our servers. If you choose to send a document for signature through Compendium Sign, that service does receive it, and should be covered by an agreement.
Is the e-signature legally defensible?
Signatures go through Compendium Sign, which maintains a hash-chained audit trail and supports ESIGN/UETA, HIPAA and 21 CFR Part 11 workflows with OTP identity verification. Whether a given signature is enforceable always depends on the circumstances of its use.
Get started
Buy a license and set up your account in one pass, then download the installer. One installer covers CompendiumPDF, CompendiumWP and Compendium LECX, and installs without administrator rights.