Healthcare Shared Care Document
What the Healthcare Shared Care Document Is
Why a Shared Care Document Matters
A clear shared care document reduces clinical errors, clarifies roles, and documents patient consent for information sharing. It supports continuity of care across organizations, helps meet regulatory privacy obligations, and creates an auditable record of who authorized which actions and when.
Who Typically Prepares and Uses This Document
Common users include clinicians, case managers, social workers, and patient representatives who coordinate multi-provider care.
- Primary care physicians and specialists coordinating treatment plans and medication changes.
- Care coordinators and case managers arranging follow-up, community services, and monitoring.
- Authorized patient representatives or proxies who need documented access to health information.
Use by these roles helps ensure responsibilities and data permissions are explicit and reproducible across clinical encounters.
Representative Signer Profiles
Primary Care Physician
A licensed clinician named as a coordinating provider who documents care directives, authorizes referrals, and confirms medical necessity. Their signature indicates clinical oversight and responsibility for coordinating follow-up and communicating changes to the care team.
Care Coordinator
A clinical or administrative professional responsible for executing the plan, scheduling services, and tracking outcomes. The coordinator documents completed actions, communicates with payers or providers, and maintains contact logs tied to the shared care document.
Step-by-Step: Completing a Shared Care Document
-
01Collect identifiers: Enter full patient and provider identifiers accurately.
-
02Describe care plan: Summarize goals, tasks, and responsible parties clearly.
-
03Obtain consent: Record the patient’s consent for data sharing and treatment.
-
04Sign and date: All authorized parties must sign and date the document.
Customizing the Document for Online Workflows
| Field | Configuration |
|---|---|
| Patient ID field | Required; autofill from EHR |
| Care Plan section | Conditional expand when multiple providers selected |
| Consent checkbox | Required; must capture timestamp |
| Routing rule | Send to primary provider then to coordinator |
Technical Considerations for eSubmission
Verify platform integrations, file formats, and authentication methods before sending shared care documents electronically.
- File formats: PDF, DOCX supported
- Integrations: EHR, Salesforce, Google Workspace
- Authentication: Email, SMS, or advanced 2FA
Ensure chosen tools support HIPAA protections, audit trails, and required retention policies for healthcare records.
Where to Send or File the Completed Document
-
Primary EHR: Upload final signed document into the patient’s chart.
-
Care Coordinator: Deliver a copy for scheduling and follow-up tasks.
-
Specialist Teams: Send relevant sections to consulting clinicians.
-
Patient or Proxy: Provide a copy showing consent and responsibilities.
Typical Timelines and Response Expectations
Immediate Actions:
Tasks requiring same-day execution should be flagged with responsibility and ETA.
Consent Effective Date:
Record as MM/DD/YYYY; governs data sharing start.
Provider Response:
Expect acknowledgement within 48–72 hours in active cases.
Plan Review:
Schedule a clinical review within 7–30 days per care complexity.
Expiration:
Documented consent should include an explicit expiry date.
Risks and Potential Consequences of Errors
eSignature Vendor Pricing and Capability Comparison
| 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 | Yes, 7-day trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Practical Examples from Real Organizations
Fertility Centers of Illinois
A clinic moved to electronic shared care records to centralize authorizations and track access.
- The API preserved workflow continuity for multi-site care.
- The team reported improved record completeness and easier audit preparation while retaining required privacy safeguards.
Martin Properties (Example)
A small organization consolidated signatures for service agreements and authorizations.
- Mobile signing enabled quicker acknowledgements.
- Faster execution reduced administrative lag and ensured required approvals were available at point of care or service delivery.
Frequently Asked Questions About Shared Care Documents
-
Are electronic signatures legally valid?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96, 2000) and where adopted under UETA (1999). Exceptions include certain testamentary documents and some court filings; always confirm the document type.
-
When is notarization required?
Notarization depends on substance and state law; some jurisdictions require notarization for powers of attorney or durable authorizations. Check state notary and RON rules and whether a notary acknowledgement or witness is necessary.
-
Does HIPAA allow electronic sharing?
Yes, HIPAA permits electronic PHI exchange provided safeguards are in place. Maintain access controls, audit logs, and a Business Associate Agreement when a vendor processes PHI (45 CFR §164.502 and §164.308).
-
How do I revoke or change consent?
Revocation should be documented in writing and communicated to all parties. Include procedures and notice addresses in the original document to ensure revocation is effective and traceable.
-
What authentication level is required?
Authentication should match risk: email-only may suffice for low-risk permissions; higher-risk disclosures may require multi-factor or identity-proofing consistent with state RON or federal guidance.
-
How long must I keep the document?
Follow applicable retention rules: HIPAA records six years (45 CFR §164.530(j)); financial records may follow IRS rules (IRC §6501(a)). When in doubt, retain according to the strictest applicable requirement.