Partner implementation workbook

Plan an imaging partnership.

Turn a proposed reading arrangement into a practical review: who owns the work, how systems hand it off, and what the teams need to verify together.

Already scoped your examinations and hours? Bring that coverage brief to this workbook. Here, focus on responsibilities and the path from study to report.

The choices and brief builder need JavaScript. You can still open each review card, read the questions and use the browser’s print command as a blank discussion worksheet.

Start with the model.

The starting model is an outpatient facility considering a local radiologist as its primary partner, with any additional reading support scoped separately. It describes a planning model, not an available or approved service.

Which partnership model will you review?

Use the applicable facility process to review the proposed readers and onsite responsibilities. Include later report changes in the receiving-system and clinical-contact review.

Agree the handoffs.

Open a responsibility, choose who should lead its review and record where its supporting evidence stands. A review owner coordinates the discussion; this does not assign clinical duties.

Onsite care and protocol questionsOwner still to agree

Open question

Discuss image acquisition, patient care, protocol ownership, contrast supervision and procedures separately from remote interpretation.

Who reviews what stays onsite?

Choose a proposed review owner first.

Bring to the reviewA written boundary between onsite duties and reading support, plus the route for technologist questions.

Interpretation and report accountabilityOwner still to agree

Open question

Identify who interprets and signs, who handles preliminary-to-final review if included, and who addresses report clarifications.

Who owns the reading and report pathway?

Choose a proposed review owner first.

Bring to the reviewReport responsibilities by scope and window, including backup and later changes.

Urgent findings and report changesOwner still to agree

Open question

Plan the receiver, fallback contact and documentation for urgent findings and meaningful report changes. The report destination alone does not answer who responds.

Who reviews the clinical contact route?

Choose a proposed review owner first.

Bring to the reviewA contact pathway for each location and window, rehearsed using fictional scenarios.

Unfinished studies and exceptionsOwner still to agree

Open question

Include studies near a coverage-window edge, missing images or history, requested priors, and cases held during downtime.

Who owns the handoff review?

Choose a proposed review owner first.

Bring to the reviewA handoff list format with status, receiving role and a process for acknowledging ownership.

Records and patient requestsOwner still to agree

Open question

Agree where reports and images can be located, how requests reach the responsible records team, and how access is handled when an arrangement ends.

Who reviews ongoing access and records routing?

Choose a proposed review owner first.

Bring to the reviewA records-routing and exit plan. Questions about what a result means return to the treating clinician.

Map the four flows.

Choose a route to review for each flow. Then give it an owner and a fictional test case. Compatibility and the actual interface design need review with the system teams.

Images

Map the acquisition-to-reading route and the place failed or incomplete transfers are noticed.

Choose a proposed review owner first.

Fictional test caseA fictional examination arrives complete, with the expected site and study identifiers.

Orders and context

Map how the reason for the examination, history and priority reach the reading workflow.

Choose a proposed review owner first.

Fictional test caseThe fictional order matches its images; context and priority survive the route.

Prior studies

Define how comparison studies are requested or made available, and who resolves missing priors.

Choose a proposed review owner first.

Fictional test caseA requested fictional prior is found, matched and visible; an unavailable prior has an escalation route.

Reports and later versions

List every intended receiving system and test how preliminary, final and changed reports are distinguished there.

Choose a proposed review owner first.

Fictional test caseThe expected fictional report version appears at each destination; an amendment is recognisable and routed for review.

IHE’s Scheduled Workflow profile describes coordination across imaging systems. HL7 publishes report-status terminology; the teams still need to agree version handling and release policy at each destination. Both references are listed below.

Gather review evidence.

Give each review a coordinating role. Keep actual agreements, reader documentation, system details and test results in your teams’ approved channels.

Reader eligibility and local responsibilitiesOwner still to agree

Open question

Review the actual proposed readers, jurisdictions, facility process, modality scope and backup arrangement. A local model does not establish eligibility.

Who gathers the eligibility review?

Choose a proposed review owner first.

Bring to the reviewReader and role documentation reviewed through the applicable facility process.

Scope, agreements and information handlingOwner still to agree

Open question

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.

Who coordinates agreement and security review?

Choose a proposed review owner first.

Bring to the reviewThe applicable agreements and information-handling decisions, reviewed by the responsible teams.

End-to-end validationOwner still to agree

Open question

Use approved fictional test data to check image, order, prior and report routes together, including incorrect or missing information.

Who reviews pathway test results?

Choose a proposed review owner first.

Bring to the reviewResults and unresolved defects for each route, including report changes and contact rehearsals.

Downtime and return to serviceOwner still to agree

Open question

Walk through a failed route, fallback ownership and restoration. Account for queued studies and reports before normal routing resumes.

Who reviews recovery and reconciliation?

Choose a proposed review owner first.

Bring to the reviewA rehearsed fallback and reconciliation plan, with an owner for each unresolved item.

Launch decision and first reviewOwner still to agree

Open question

Bring scope, clinical responsibilities, agreements, eligibility and test results together. Agree a first review and the route for pausing or changing the arrangement.

Who coordinates the launch review?

Choose a proposed review owner first.

Bring to the reviewA recorded decision by the responsible teams, an exception owner and a first-review agenda.

Only fixed planning choices. Nothing is sent or saved by the workbook. Leaving this page or reloading clears it.

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.

  1. Which setting are you planning for?

    • Outpatient facility
    • Nevada outpatient facility
    • Hospital or health system
    • Radiology group
  2. Which partnership model will you review?

    • Local radiologist as primary partner; reading support separately scoped
    • Supplemental reading alongside an existing local team
    • Partnership model still to decide
  3. Where is your coverage scope today?

    • Examinations, hours and report types still to discuss
    • Coverage brief drafted; partner review still needed
    • Scope discussed; implementation decisions still needed
  4. Which report pathway needs to be tested?

    • Report pathway still to decide
    • Final reports, including later changes
    • Preliminary to final reports, including later changes
  5. Who is proposed to receive unfinished work at handoff?

    • Handoff receiver still to decide
    • Local radiology team through an agreed handoff
    • Reading service completes the agreed assigned queue
    • Joint review of exceptions, with an owner for each study

02 · Agree clinical responsibilities and handoffs

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  1. Images

    Map the acquisition-to-reading route and the place failed or incomplete transfers are noticed.

    Route options to discuss

    • Facility PACS-managed route to review
    • Modality or gateway-managed route to review
    • Image route still to map

    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.

  2. Orders and context

    Map how the reason for the examination, history and priority reach the reading workflow.

    Route options to discuss

    • System interface to review
    • Facility-approved document workflow to review
    • Order route still to map

    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.

  3. Prior studies

    Define how comparison studies are requested or made available, and who resolves missing priors.

    Route options to discuss

    • Priors sent with the new examination
    • Agreed archive access to review
    • Request-and-response pathway to review
    • Prior-study route still to map

    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.

  4. Reports and later versions

    List every intended receiving system and test how preliminary, final and changed reports are distinguished there.

    Route options to discuss

    • RIS / EHR receiving route to review
    • PACS / document receiving route to review
    • Multiple receiving routes to map individually
    • Report destinations still to map

    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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

05 · Planning brief

Bring the decisions and the open questions.

You can prepare a brief at any point. Unassigned owners, unmapped routes and evidence still to gather become its next-conversation list.

  • Proposed responsibilities and handoffs
  • Routes and fictional pathway tests
  • Evidence, launch review and unresolved decisions

Blank discussion worksheet: no brief has been prepared. The questions above are prompts for review, not approvals.

References

Reference context

Primary references for information exchange, privacy relationships and report-status terminology. They do not establish vendor compatibility, eligibility or clinical approval.

  1. Scheduled Workflow integration profileIHE International
  2. When is a health care provider a business associate of another health care provider?U.S. Department of Health and Human Services
  3. DiagnosticReportStatus code system (FHIR R4, v4.0.1)HL7 International · Published R4 terminology for report status; not a facility release or display policy