Can the LTWS PCP be signed electronically?

Yes. Electronic signatures are legally valid under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA implementations, provided intent, consent, attribution, and retention capabilities are met. Confirm exceptions such as court-ordered filings or other local statutory exclusions.

Is a Business Associate Agreement required?

If the eSignature provider will access, store, or transmit protected health information, a HIPAA Business Associate Agreement is typically required to allocate responsibilities and support regulatory compliance.

What witness or notary steps are needed?

Witness and notary needs vary by state and the document’s legal effect. Check local rules for advance directives and durable authorizations; some states require two witnesses or notarization for certain healthcare authorizations.

What happens if a field is filled incorrectly?

Minor data errors can cause payer denials or processing delays. Correct errors using the vendor’s approved amendment workflow so the change is auditable and retains previous version history.

How long must we keep signed LTWS PCPs?

Follow HIPAA retention (6 years from creation or last effective date, 45 CFR §164.530(j)) and federal tax or audit minimums. Many organizations retain clinical records seven years or longer per state or payer requirements.

Which eSignature authentication method is sufficient?

Choose an authentication level aligned with risk: email-only or SMS OTP for low-risk signatures, while remote identity proofing or stronger multi-factor authentication is advised for high-risk or sensitive authorizations.

Healthcare LTWS PCP

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

HEALTHCARE LTWS PCP

This Long-Term Waiver Services Primary Care Physician (LTWS PCP) Designation documents the patient’s selection or change of a primary care physician for coordination of long-term services and supports. Patient Name: Effective Date:

Patient Information

Patient Full Name

Date of Birth

Gender (select applicable) Male Female Other

Home Address

Primary Phone

Email (if any)

Emergency Contact

Name

Relationship

Phone

Insurance Information

Primary Insurance Provider

Policy Number

Group Number

Subscriber Name

Medical History & Current Health Status

Current Medications Allergies (including drug allergies) Prior Surgeries / Hospitalizations Chronic Conditions / Diagnoses

Primary Care Physician (PCP) Selection

I hereby designate the following primary care physician to coordinate my LTWS primary medical care. I understand that assignment of a PCP enables coordination of services, referrals, and exchange of medical information necessary for my care.

PCP Name

Practice / Clinic

NPI / Provider ID

Office Phone

PCP Office Address Reason for Selection or Change

PCP Assignment Type: New Assignment Change of PCP No Change (confirmation)

Consent, Authorization & Notices

Coordination of Care Authorization: I authorize LTWS care coordinators, my listed providers, and my designated PCP to exchange protected health information (PHI) necessary for treatment, care coordination, referrals, medication management, and eligibility verification. This includes but is not limited to diagnoses, medications, allergies, past medical and surgical history, laboratory results, and care plans.

I authorize release of medical information to the PCP for care coordination Yes No

HIPAA Privacy Acknowledgment: I acknowledge that I have received or been offered the entity’s Privacy Practices that describe how my health information may be used and disclosed, and my rights regarding that information. I understand that information necessary for care coordination will be disclosed to the PCP as described above.

HIPAA Acknowledgment Acknowledged Declined

Revocation: I understand this authorization may be revoked by me at any time by submitting a written notice to the LTWS program or provider, except to the extent that action has already been taken in reliance on this authorization. Revocation will not affect disclosures already made under this authorization prior to receipt of the revocation.

Authorization Expiration Date

Limitations: This authorization does not permit release of psychotherapy notes, unless specifically initialed and described here:

Patient Rights & Responsibilities

Patient Responsibilities: I understand it is my responsibility to keep my PCP and LTWS program informed of any changes to my medical condition, medications, insurance coverage, contact information, or emergency contacts. I understand it remains my responsibility to seek timely care and to follow the plan of care developed with my PCP.

Patient Concerns or Special Instructions

Attestation & Signature

By signing below, I certify that the information provided is true and accurate to the best of my knowledge. I authorize the exchange of health information as indicated in this form and understand that I may revoke this authorization as described above. I understand assignment or change of a PCP may require coordination with my managed care plan or payor and may be subject to plan rules.

Patient Printed Name:

Signature:

Date:

If signing as legal guardian or authorized representative, state relationship and authority below.

Relationship / Authority (if applicable)

What the Healthcare LTWS PCP Is and when it’s used

The Healthcare LTWS PCP is a provider-completed care plan template used to document long-term waiver services and the primary care provider's responsibilities for patients receiving long-term services and supports. It records patient identifiers, clinical goals, service authorizations, care coordination tasks, and signatures that establish consent and acknowledgements for ongoing care coordination. Organizations use the form to align payer authorizations, clinical teams, and case management while creating a single record that supports billing, clinical audits, and patient access requests.

Why a clear LTWS PCP matters for care continuity and compliance

A completed LTWS PCP centralizes patient instructions, documents clinical justification for long-term services, and helps meet payer and regulatory requirements. Clear plans reduce billing disputes, support clinical continuity, and provide an auditable record for patient consent and care oversight under applicable healthcare rules.

Primary users and stakeholders for the LTWS PCP

Typical users include clinical staff, case managers, payers, and primary care providers responsible for long-term waiver services.

Primary Care Providers and Nurses: Complete clinical sections, document treatment goals, and sign for medical oversight.
Case Managers and Care Coordinators: Use the plan to align services, track authorizations, and schedule provider tasks.
Payers and Utilization Review: Review for medical necessity, retain the document for audit, and confirm service authorization.

Each stakeholder uses the form differently: clinicians for care details, case managers for coordination, and payers for authorization and audit evidence.

Core sections to include in a professional LTWS PCP

A high-quality LTWS PCP is structured to capture administrative, clinical, and legal elements so the record supports care delivery, reimbursement, and regulatory review.

Patient Identifiers

Full legal name, DOB, address, and a unique patient ID to reliably link the plan to medical records and claims files.

Clinical Summary

Diagnosis, functional status, medications, allergies, and a concise narrative that explains the medical basis for long-term waiver services.

Care Goals

Measurable short- and long-term goals tied to services and expected outcomes, with targeted review dates for progress assessment.

Services Authorized

Detailed list of services, frequency, providers, and payer authorization codes to support billing and utilization reviews.

Signatures & Dates

Signed attestations from the primary care provider and patient or authorized representative with signature dates and printed names.

Coordination Notes

Contact information for involved providers, next steps for referrals, and case manager follow-up actions to ensure continuity.

Step-by-step: filling out and finalizing the LTWS PCP

Follow these steps to prepare a complete, auditable LTWS PCP that meets clinical, payer, and legal needs.

01

Collect patient details: Confirm legal name, DOB, MRN, and payer information before drafting the plan.
02

Document clinical rationale: Summarize diagnosis, functional status, and why waiver services are medically necessary.
03

Specify services: List units, frequency, providers, and effective dates tied to measurable goals.
04

Obtain signatures: Have provider and patient/authorized rep sign and date the document with required witnesses or notarization.

Typical end-to-end workflow for LTWS PCP completion

This workflow outlines common routing steps from creation to archival so teams understand responsibilities and timelines.

Initiation: Case manager opens draft after intake and pre-populates administrative fields.
Clinical Review: Primary care provider reviews clinical summary and completes clinical rationale.
Authorization: Payer or utilization review confirms services and authorizes coverage when applicable.
Finalize & Store: Obtain signatures, deliver copies to patient and payer, then archive per retention rules.

Digital workflow settings to streamline LTWS PCP processing

Configure fields and routing so each signer receives the correct view, and the system captures an audit trail for compliance.

Field	Configuration
Signature Field	Require signer name, date, and role; lock after signing.
Conditional Sections	Show service detail fields only when selected service type applies.
Authentication	Enable email and SMS OTP for provider and patient signers.
Retention Tag	Apply HIPAA or financial retention tags automatically after signing.

Technical considerations for eSubmission and signing

Ensure the signing platform supports secure authentication, audit trails, and healthcare compliance before eSubmission.

Authentication: Email, SMS OTP, or stronger options.
Audit Trail: Capture IP, timestamps, and signer events.
Integrations: EHR, cloud storage, and payer connectors.

Typical eSignature vendor comparison for Healthcare LTWS PCP workflows

Comparing baseline price and key capabilities helps organizations choose a solution that meets HIPAA, bulk-send, and integration needs without overpaying.

	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	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies	Varies	Varies

Security and compliance controls to require for eSigning

Encryption in transit: TLS 1.2/1.3

Encryption at rest: AES-256

HIPAA readiness: BAA required

Audit logging: Timestamped events

Certifications: SOC 2 Type II

Regulated workflows: 21 CFR Part 11 support

Key risks and potential consequences of errors

HIPAA enforcement: OCR investigations possible

Invalid consent: Clinical or legal disputes

Billing denials: Payer claim rejections

Delayed care: Service interruptions

Data breach: Unauthorized PHI exposure

Audit findings: Corrective action plans

Common preparation errors to avoid

Incomplete patient identifiers lead to misfiled records and payer pushback during claims or audits; confirm MRN, DOB, and legal name before finalizing.
Ambiguous service descriptions cause authorization denials; specify units, frequency, and concrete start and end dates to align with payer rules.
Missing or improper signatures invalidate parts of the plan; verify signer authority, witness requirements, and notarization rules where applicable.
Using image-only signatures without an audit trail increases evidentiary risk; use platforms that capture timestamps, IP, and signer authentication.

Expected timelines and processing benchmarks

Use these timelines as planning benchmarks; contract or payer rules may impose stricter deadlines.

Provider review time:

Typically 7–14 business days for full clinical review

Payer authorization:

Varies by payer; expect 7–30 business days for utilization review

Patient access requests:

HIPAA generally requires response within 30 days

Notarization scheduling:

Plan for same-day or next-business-day availability

Claim submission:

Submit promptly after service to meet payer timetables

Practical examples from organizations using eSigned care plans

Real-world implementations show how digital workflows reduce friction while preserving compliance.

Fertility Centers of Illinois — John Butler

They moved to online signing for care plans to centralize records and speed processes.

Staff emphasized usability and API integration for EHR workflows.
John Butler reported the implementation eased document handling and that the vendor’s responsiveness supported integration with existing clinical systems.

BIS — Dan Rotelli

BIS standardized signed forms across departments to reduce manual steps.

The focus was auditability and secure storage.
Dan Rotelli noted that the platform’s SOC 2 posture and audit trail made internal compliance checks simpler while preserving secure access for authorized staff.

Practical tips for accurate, compliant LTWS PCP completion

Adopt templates, validation, and role-based signing to reduce rework and maintain an auditable record.

Verify identities thoroughly

Confirm patient identity using government ID and match MRN and DOB. Use multi-factor or government ID checks for remote signers when required by payer or state rules.

Use clear, measurable goals

Define outcomes with specific timelines and metrics. Measurable goals reduce ambiguity in reviews and support clinical audits and authorization renewals.

Capture complete audit data

Ensure the eSignature system records IP, timestamps, document history, and signer authentication steps to support audits and dispute resolution.

Coordinate retention and access

Apply retention tags that reflect HIPAA and payer requirements so documents remain searchable and available during audits or patient access requests.

Frequently asked questions about completing and eSigning the LTWS PCP

Answers address common legal, technical, and procedural issues encountered during preparation and eSubmission.

Need help? Contact support

Can the LTWS PCP be signed electronically?
Yes. Electronic signatures are legally valid under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA implementations, provided intent, consent, attribution, and retention capabilities are met. Confirm exceptions such as court-ordered filings or other local statutory exclusions.
Is a Business Associate Agreement required?
If the eSignature provider will access, store, or transmit protected health information, a HIPAA Business Associate Agreement is typically required to allocate responsibilities and support regulatory compliance.
What witness or notary steps are needed?
Witness and notary needs vary by state and the document’s legal effect. Check local rules for advance directives and durable authorizations; some states require two witnesses or notarization for certain healthcare authorizations.
What happens if a field is filled incorrectly?
Minor data errors can cause payer denials or processing delays. Correct errors using the vendor’s approved amendment workflow so the change is auditable and retains previous version history.
How long must we keep signed LTWS PCPs?
Follow HIPAA retention (6 years from creation or last effective date, 45 CFR §164.530(j)) and federal tax or audit minimums. Many organizations retain clinical records seven years or longer per state or payer requirements.
Which eSignature authentication method is sufficient?
Choose an authentication level aligned with risk: email-only or SMS OTP for low-risk signatures, while remote identity proofing or stronger multi-factor authentication is advised for high-risk or sensitive authorizations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now