TL;DR
When eye care is shared across organizations, give every public administrative instruction a responsible organization and an accepted receiving route. Distinguish consultation requests, professional coordination, scheduling and later questions. The marketing handoff should explain who handles the next step without assigning clinical responsibilities or implying that every organization controls the entire pathway.
Start with the real arrangement
'Co-managed care' is not enough information for a writer to assign tasks. Ask the authorized operational and clinical leads to describe the actual organizations, roles, locations and approved communication routes. A shared page, referral relationship or common service name does not establish a universal agreement.
The owner's problem may appear when someone contacts the surgical practice about an appointment handled elsewhere, or asks another office for information that only the surgical coordinator can verify. Those are conditional administrative scenarios. Confirm which ones the real workflow supports before adding instructions.
Do not use a marketing project to negotiate care responsibilities, determine clinical follow-up or interpret a patient-specific transfer. Those decisions belong to qualified practice teams under the actual arrangement. The content brief starts with their approved facts.
Complete a role-specific acquisition handoff map
This original map helps writers and staff explain the administrative path. Substitute the real organization names only after their role and permitted wording are confirmed.
| Public task | Organization that explains it | Receiving role to verify | Acceptance evidence |
|---|---|---|---|
| Ask about the practice's evaluation offering | Organization actually providing that evaluation | Approved scheduling or coordinator route | Request arrives with the correct service and office |
| Ask about a professional referral | Organization responsible under the actual referral arrangement | Authorized professional coordination contact | Sender and receiver understand the permitted next administrative action |
| Confirm an appointment | Organization controlling that appointment | Actual scheduling team | Confirmation describes the right organization, purpose and site |
| Ask about later scheduling | Organization assigned that administrative task | Named receiving team | Handled or explicitly returned through an approved exception process |
| Ask which organization to contact | The page owner supplies an approved routing explanation | Appropriate general contact with qualified escalation | Visitor is not left to guess from logos |
For each task, record the source fact owner, wording approver, destination, backup and unresolved exception. Keep the working document free of clinical histories and personal contact records. The map describes responsibilities; it is not permission to transfer information between organizations.
Separate information sharing from a marketing invitation
For U.S. HIPAA-regulated uses or disclosures of protected health information, HHS describes a general written-authorization requirement for marketing, with limited exceptions. HHS's marketing guidance. The current marketing definition distinguishes certain treatment and care-coordination communications subject to conditions, including financial remuneration. Apply it alongside the current authorization rule to the actual communication and arrangement.
Do not assume a shared-care relationship authorizes a joint promotional list or unrestricted agency access. Have the practice's privacy and legal owners assess the real data, purposes, recipients, agreements and applicable rules. Use the approved systems and routes for necessary individual coordination.
Outside the United States, assess the actual jurisdiction rather than importing the HIPAA framework. A public page can still be improved using verified organizational facts while questions about a particular information transfer remain with the responsible reviewers.
Draft instructions from the receiver backward
Ask the receiving team what it can actually do. If it only accepts an appointment query, the page should not say it confirms a clinical plan. If it forwards a message to another organization, say what that means under the approved process without inventing a response deadline.
A useful drafting specimen is: 'For questions about [verified administrative task], contact [responsible organization] through [approved route]. [Other organization] handles [separately verified task]. If you are unsure which route applies, use [approved general contact].' Complete every field from actual facts before publication.
Use the service-role guide to keep organizational capability accurate. This map adds operational ownership across organizations, including what happens when the first recipient cannot resolve the request.
Test the handoff without triggering patient communication
Coordinate synthetic rehearsals with both relevant teams where authorized. Test a correctly routed query, a query arriving at the wrong organization and an uncertain destination. Use practice-controlled details and prevent real appointments or outreach. Do not fabricate a clinical history.
The receiving role should be able to identify its task, permitted next action and exception owner. Record whether the sender can distinguish a message transmitted from a task accepted. Do not close a handoff merely because a general inbox received something.
Review public pages, downloadable administrative instructions and confirmation wording together. Assign a change owner for provider relationships, contact routes or scheduling responsibility. Do not let an old logo or reused paragraph continue to imply a responsibility that has changed.
The shared-episode review-request guide covers a different task: who sends an approved feedback invitation. It does not assign clinical care or acquisition responsibilities. Keep that request workflow separate from the map here.
Frequently asked questions
Can we put every organization's logo on the page?
Use only authorized, accurately described relationships. Logos should not substitute for explaining which organization performs the requested administrative task.
Does the handoff map decide follow-up care?
No. Qualified teams must establish clinical roles through the actual arrangement. The map communicates their verified administrative instructions.
What if an organization cannot confirm its role yet?
Keep the unsupported instruction out of publication and assign the precise question to its owner. Continue correcting verified public facts and usable contact routes without inventing a shared-care promise.