Proof Of Good Health Statement

Use a Proof Of Good Health Statement 2018 template to make your document workflow more streamlined.

What the health statement does

A Proof Of Good Health Statement records a person’s signed confirmation about their health status or fitness for a specified purpose. The exact questions, signer identity, supporting information, and recipient depend on the statement supplied by the requesting organization. With signNow, the sender uploads the document, checks detected fields, adds signature and date fields, routes it to the signer, and retains the completed PDF with its audit trail. ESIGN and UETA can support electronic execution when intent, consent, attribution, and reproducible records are established.

Who uses this health statement

The requesting organization determines who must sign, what health information is requested, and where the completed statement must be retained.

Healthcare practices use the statement to collect patient or staff confirmations while controlling access to protected health information through a documented signing workflow.
Employers and staffing organizations use it for health-related onboarding or duty-clearance records, subject to applicable privacy rules and the statement issuer’s requirements.
Event, sports, and education administrators use it when participants must provide a signed health declaration before attendance, travel, or supervised activity.

Fillable fields

Upload the Proof Of Good Health Statement and place signature, date, initials, and required response fields without rebuilding the document manually.

Signer routing

Send the statement to named signers by email or controlled link, keeping the signing sequence and recipient assignments visible to the sender.

Audit evidence

Capture signer actions, timestamps, authentication events, and completion details in an audit trail associated with the signed statement.

Data protection

Protect health information with TLS 1.2 or 1.3 in transit and AES-256 encryption at rest within signNow’s documented compliance environment.

Reusable templates

Use templates for recurring Proof Of Good Health Statement workflows so approved wording, required fields, and signer roles remain consistent.

Mobile access

Complete and review the statement from signNow mobile apps when staff or signers work away from a desktop.

Setting	Recommendation
Authentication method	Email verification with SMS OTP for sensitive health information
Signature type	Typed or drawn electronic signature with signer intent
Audit trail	Enable timestamped action history and completion certificate
Document retention	Retain according to organizational policy and applicable health-record rules
Encryption	Use TLS 1.2 or 1.3 in transit and AES-256 at rest

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Authenticate signer:

Record the selected signer authentication method and its completion result.

Timestamp actions:

Capture the date and time for each document and signer action.

Hash document:

Preserve document integrity evidence as the statement moves through signing.

Seal record:

Seal the completed statement with its associated signing history.

Review history:

Open the completed audit trail to review signer and workflow events.

Export evidence:

Export the signed statement and audit evidence for approved retention.

Connect health statements to business systems

Route completed Proof Of Good Health Statements into connected CRM, ERP, collaboration, and cloud-storage workflows without rekeying document information.

Find and fill out the correct proof of good health statement

airSlate SignNow helps you fill in and sign documents in minutes, error-free. Choose the correct version of the editable PDF form from the list and get started filling it out.

Versions	Form popularity	Fillable & printable
Aetna GR-67829-46 2018	4.8 Satisfied (2180 Votes)
Aetna GR-67829-46 2016	4.8 Satisfied (122 Votes)

Protect health statement records

Data in transit:

TLS 1.2 and 1.3 encryption

Data at rest:

AES-256 encryption at rest

Health information:

HIPAA compliance with BAA

Operational controls:

SOC 2 Type II certification

Security management:

ISO 27001 certification

Signer authentication:

Two-factor authentication options

Access requirements for signing

Complete the Proof Of Good Health Statement through Chrome, Firefox, Safari, or Edge on Windows or macOS. signNow mobile apps support iOS and Android, while TLS 1.2 or 1.3 protects data in transit during access and signing.

Browser support Chrome, Firefox, Safari, and Edge browsers
Desktop systems Windows and macOS desktop access
Mobile apps iOS and Android signNow apps

Organizations handling health information should manage access through approved devices, defined user permissions, and a configured signNow authentication method. Confirm API, SSO, and HIPAA BAA requirements before connecting the statement to clinical, employee, or benefits systems.

Retain and review signed statements

Accurate fields, controlled access, exported audit evidence, and a record-specific retention rule make the completed health statement easier to administer and defend.

Match retention to record context

Apply the retention rule that matches the record’s actual context rather than assigning one universal period. HIPAA-covered documentation must be retained for 6 years from creation or the last effective date under 45 CFR §164.530(j).

Export the audit trail

Export the completed Proof Of Good Health Statement together with its signNow audit trail. Preserve signer identity evidence, timestamps, and completion details so the record remains understandable outside the signing application.

Restrict health information access

Limit access to staff who administer the health workflow or need the statement for a documented business purpose. Use role-based permissions and avoid forwarding health information through personal email accounts.

Verify fields before sending

Review every response field before sending, including dates, names, and health declarations. Require the signer to correct inaccurate information before signing rather than relying on post-signature edits.

Prepare the statement

Review the statement fields, health details, and required signer information before sending.

Deliver to signers

Send by email or share a controlled signing link through signNow.

Complete signer review

Allow each signer to review disclosures and complete required signature fields.

Archive the record

Save the completed statement and audit trail in the approved records system.

Troubleshoot Proof Of Good Health Statement workflows

Resolve field-detection, signer-access, health-information, plan, and electronic-signature questions before distributing the completed statement.

Upload the original Proof Of Good Health Statement as a PDF, then check signNow’s detected fields. Add or reposition fields when the source document contains blank lines rather than interactive form fields.

The Business plan includes legally binding eSignatures, templates, audit trails, and mobile apps. Business Premium adds bulk send, while Enterprise adds advanced signer authentication for higher-control health workflows.

HIPAA compliance requires a business associate agreement when protected health information is handled. signNow identifies HIPAA compliance as available with a BAA; confirm the account configuration before sending health information.

A completed signature alone does not prove every health statement fact is accurate. Require the signer to review each response, preserve the signed document, and retain the audit trail showing intent, timestamps, and actions.

If a signer cannot open the request, resend the invitation or provide a controlled signing link. For sensitive information, use SMS OTP or another configured authentication step rather than forwarding the original email.

ESIGN and UETA generally recognize electronic signatures when intent, consent, attribution, and record reproduction are established. Consumer-facing records also require the disclosures described in 15 U.S.C. §7001(c).

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.