Radstead · Partnership planning
Blank discussion worksheet
Use these prompts to agree what the responsible teams need to review. No choices or owners have been selected in this blank worksheet.
Discussion prompts, not clinical approval or service activation. Proposed review owners coordinate the conversation; they do not acquire clinical duties through this worksheet.
01 · Start with the model
Consider the options together. Any additional reading support needs a separately agreed scope; a setting or model does not establish an available service.
Which setting are you planning for?
Which partnership model will you review?
Where is your coverage scope today?
Which report pathway needs to be tested?
Who is proposed to receive unfinished work at handoff?
02 · Agree clinical responsibilities and handoffs
Onsite care and protocol questions
Who reviews what stays onsite?
Discuss image acquisition, patient care, protocol ownership, contrast supervision and procedures separately from remote interpretation.
Evidence to bring: A written boundary between onsite duties and reading support, plus the route for technologist questions.
Proposed review owner: still to agree. Evidence: open for discussion.
Interpretation and report accountability
Who owns the reading and report pathway?
Identify who interprets and signs, who handles preliminary-to-final review if included, and who addresses report clarifications.
Evidence to bring: Report responsibilities by scope and window, including backup and later changes.
Proposed review owner: still to agree. Evidence: open for discussion.
Urgent findings and report changes
Who reviews the clinical contact route?
Plan the receiver, fallback contact and documentation for urgent findings and meaningful report changes. The report destination alone does not answer who responds.
Evidence to bring: A contact pathway for each location and window, rehearsed using fictional scenarios.
Proposed review owner: still to agree. Evidence: open for discussion.
Unfinished studies and exceptions
Who owns the handoff review?
Include studies near a coverage-window edge, missing images or history, requested priors, and cases held during downtime.
Evidence to bring: A handoff list format with status, receiving role and a process for acknowledging ownership.
Proposed review owner: still to agree. Evidence: open for discussion.
Records and patient requests
Who reviews ongoing access and records routing?
Agree where reports and images can be located, how requests reach the responsible records team, and how access is handled when an arrangement ends.
Evidence to bring: A records-routing and exit plan. Questions about what a result means return to the treating clinician.
Proposed review owner: still to agree. Evidence: open for discussion.
03 · Map the four information flows
Review compatibility and the actual interface design with the system teams. Use approved fictional test cases, without patient information or real credentials.
Images
Map the acquisition-to-reading route and the place failed or incomplete transfers are noticed.
Route options to discuss
Fictional test case: A fictional examination arrives complete, with the expected site and study identifiers.
Proposed route and review owner: still to agree. Evidence: open for discussion.
Orders and context
Map how the reason for the examination, history and priority reach the reading workflow.
Route options to discuss
Fictional test case: The fictional order matches its images; context and priority survive the route.
Proposed route and review owner: still to agree. Evidence: open for discussion.
Prior studies
Define how comparison studies are requested or made available, and who resolves missing priors.
Route options to discuss
Fictional test case: A requested fictional prior is found, matched and visible; an unavailable prior has an escalation route.
Proposed route and review owner: still to agree. Evidence: open for discussion.
Reports and later versions
List every intended receiving system and test how preliminary, final and changed reports are distinguished there.
Route options to discuss
Fictional test case: The expected fictional report version appears at each destination; an amendment is recognisable and routed for review.
Proposed route and review owner: still to agree. Evidence: open for discussion.
04 · Gather validation and launch review evidence
Keep actual agreements, reader documentation, system details and test results in your teams’ approved channels. The responsible teams verify the evidence and make their own decisions.
Reader eligibility and local responsibilities
Who gathers the eligibility review?
Review the actual proposed readers, jurisdictions, facility process, modality scope and backup arrangement. A local model does not establish eligibility.
Evidence to bring: Reader and role documentation reviewed through the applicable facility process.
Proposed review owner: still to agree. Evidence: open for discussion.
Scope, agreements and information handling
Who coordinates agreement and security review?
Have the responsible teams review responsibilities, service definitions, privacy roles, access and exit terms. Whether a business associate agreement is needed depends on the relationship and purpose.
Evidence to bring: The applicable agreements and information-handling decisions, reviewed by the responsible teams.
Proposed review owner: still to agree. Evidence: open for discussion.
End-to-end validation
Who reviews pathway test results?
Use approved fictional test data to check image, order, prior and report routes together, including incorrect or missing information.
Evidence to bring: Results and unresolved defects for each route, including report changes and contact rehearsals.
Proposed review owner: still to agree. Evidence: open for discussion.
Downtime and return to service
Who reviews recovery and reconciliation?
Walk through a failed route, fallback ownership and restoration. Account for queued studies and reports before normal routing resumes.
Evidence to bring: A rehearsed fallback and reconciliation plan, with an owner for each unresolved item.
Proposed review owner: still to agree. Evidence: open for discussion.
Launch decision and first review
Who coordinates the launch review?
Bring scope, clinical responsibilities, agreements, eligibility and test results together. Agree a first review and the route for pausing or changing the arrangement.
Evidence to bring: A recorded decision by the responsible teams, an exception owner and a first-review agenda.
Proposed review owner: still to agree. Evidence: open for discussion.