Choose one service and site
Document the request types, local booking rules and current handoffs for an initial workflow. Include both centralized intake and the location that resolves the request.
Give each request a location, an owner and a review path. Connect centralized intake with the local teams responsible for scheduling, insurance and clinical documentation.

Capture the requested site, service and callback details. Prepare a routed request for the team responsible for that location.
“I called about my referral, but I need the appointment at your north location.”
The receiving location checks its schedule and requirements, then confirms the appointment through its own process.
Keep the service date, reference number and payer response with the responsible team. Surface missing information before the next follow-up.
“Which team is following up on the authorization for next week’s service?”
The authorized team verifies the response, assigns missing work and confirms the next action.
Prepare encounter notes with transcript context. The treating clinician reviews and signs the note under the organization’s documentation rules.
“A clinician needs to review the draft note from an encounter at one of the group’s locations.”
The clinician verifies and signs the note. Access, source connections and review responsibilities are agreed during setup.
Document the request types, local booking rules and current handoffs for an initial workflow. Include both centralized intake and the location that resolves the request.
Name the people responsible for intake, review and confirmation. Confirm which locations, records and source systems each role needs before connecting the workflow.
Use a small agreed set of requests to check routing, missing information and final confirmation. Extend the workflow to another site only after its local rules and exceptions are reviewed.
Start by defining each site’s services, booking requirements and review owners. The request should carry the chosen location and original context to the team that can resolve it. Review site-specific exceptions before extending the workflow across the organization.
Identify the exact source systems, permitted data access and actions needed for the selected workflow. Confirm those connections individually with your team. Define how prepared work returns for review and how staff verifies any final action in its system of record.
Choose a service and location with a clear owner and a manageable set of requests. Review routing accuracy, unresolved information and confirmation steps first. Use that evidence to decide which additional site or workflow is ready to be included.
Bring the central intake and local operations teams together around one request type and a defined review path.