Remote Reporting for Imaging (TeleRadiology) - Proposal

From IHE Wiki
Revision as of 09:06, 19 September 2014 by Lindop (talk | contribs) (→‎5. Discussion)
Jump to navigation Jump to search

1. Proposed Workitem: Remote Reporting for Imaging (TeleRadiology) Workflow Definition

  • Proposal Editor: Chris Lindop on behalf of IHE Canada/Canada Infoway
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: Radiology

Summary

<Summarize in a few lines the existing problem . E.g. "It is difficult to monitor radiation dose for individual patients and almost impossible to assemble and compare such statistics for a site or a population.">

<Demonstrate in a line or two that the key integration features are available in existing standards. E.g. "DICOM has an SR format for radiation dose events and a protocol for exchanging them.">

<Summarize in a few lines how the problem could be solved. E.g. "A Radiation Dose profile could require compliant radiating devices to produce such reports and could define transactions to actors that collect, analyze and present such information.">

<Summarize in a line or two market interest & available resources. E.g. "Euratom and ACR have published guidelines requiring/encouraging dose tracking. Individuals from SFR are willing to participate in Profile development.">

<Summarize in a line or two why IHE would be a good venue to solve the problem. E.g. "The main challenges are dealing with the chicken-and-egg problem and avoiding inconsistent implementations.">


2. The Problem

Cross-Enterprise or Community Diagnostic Image Sharing Repositories is a growing service internationally and has proven effective for sharing of previously acquired images and reports. The current IHE XDS-I.b infrastructure effectively supports this. IHE PCC eReferral specifies a Workflow Definition (WD) for community referral. This WD does manage patient referrals for imaging. eReferral does not address the remote reading of images outside of the initial referral or sharing of priors. Currently, to meet this need, HCIT suppliers have built proprietary systems with non-standard methods for managing this workflow. Proprietary methods limit the solution extensibility.

Cross-enterprise image sharing, beyond the initial step, has the capability to attain efficiencies and reduce cost at a macro-scale level:

  • Improve throughput of radiology depts by allowing any radiologist in the community to read and report a study
  • Align the number of resources (staff, equipment) with the needs of the community as opposed to considering individual hospitals only
  • Facilitate assignment of studies to physicians that are best qualified to read them (e.g., a SPECT expert may be leveraged across the community)
  • Provide off-hours coverage by sharing radiologists' services off peak hours

3. Key Use Case

The primary use case is workload sharing. Workload sharing could include:

  • Specialty Read(SPECT example)
  • Site Loading (time-to-read exceeds threshold example)
  • Off hours coverage

Other specialized cases to consider include:

  • Double Read(mammography example)
  • Consult(inconclusive read example)
  • Blind Read(VIP example)

A specialty read of SPECT images will be used for this example:

The community hospital has a NM acquisition system fully capable of acquiring SPECT Images, but lacks a credentialed NM Radiographer to read SPECT. Per the institutional business rules, all SPECT images will require a NM credentialed Radiologist to perform the read. The regional image sharing network has NM credentialed Radiologists. Based on the institutional business rules, this study meets the criteria for Remote Read.

The workflow document steps, then, could be:

  1. Remote Read Request:The Remote Read Requester, usually the Radiology department scheduler, is triggered by an HL7 Order with a procedure code for SPECT. The Remote Read Requester will automatically collect relevant clinical documents, including Manifest of Acquired Images, Tech Notes, Clinical Summaries, and, will create the Remote Read Request and a workflow document containing the tasks to be performed. The set of documents will be pushed to the regional image sharing network for processing.
  2. Schedule Remote Read:Once the document set is received by the image sharing network, the Remote Read Scheduler evaluates the Remote Request Request and assigns a reader(s) who are NM credentialed Radiologist. The assignment is encapsulated in an HL7 procedure scheduled message to the Remote Reader's RIS/PACS. The Workflow document is updated.
  3. Remote Read:The Remote Reader's RIS/PACS receives the procedure scheduled message and initiates the Remote Read Task. The Final Report and any evidence documents (encapsulated in a New DICOM Manifest) are the output of this task. This task may be partitioned into several subtasks to perform the read. For each subtask, the workflow document may be updated and progress may be monitored in accordance with the terms of the BA and workflow document. The additional subtasks are as follows:
    1. Prep for Read: If step is neccessary, the Remote Read Preparer
      1. creates local Patient in database
      2. Retrieves remote images and relevant priors to local cache.
    2. Ready for Read: SPECT Read is placed on the Remote Reader(NM credentialed Radiologist) reading worklist
    3. Preliminary Read: Remote Reader(NM credentialed Radiologist) releases unsigned report
    4. Final Read: Remote Reader(NM credentialed Radiologist) releases Final Report to the Regional Image Sharing Network
  4. Read Complete: The Remote Read Requester retrieves the Report and completes the Workflow. Billing system is notified(out-of-scope). Final Report distributed to patient's care team(out-of-scope).

4. Standards and Systems

Systems

  • RIS
  • PACS
  • VNA
  • Community Image Sharing Network

Standards

  • XDS-I for hosting Images and reports
  • XDW underlying workflow profile framework
    • Compatible with XDS/XDS-I architecture
    • XDW currently does not support Cross community (XCA/XCA-I))
      • Workflow is all within the same affinity domain
      • This will be addressed in context with IHE ITI community
  • XBeR-WD Workflow Definition
    • Sufficient for Image Referral
  • XDR/XDR-I for point to point
    • As necessary
  • DSUB for Notifications
    • D-SUB can act as a notification mechanism for XDW results available/completed -OR- could be a trigger to receptionist to call Dr. XXX
  • UPS DICOM Webservices
    • New DICOM Standard for workflow

5. Technical Approach

<This section can be very short but include as much detail as you like. The Technical Committee will flesh it out when doing the effort estimation.>

<Outline how the standards could be used/refined to solve the problems in the Use Cases. The Technical Committee will be responsible for the full design and may choose to take a different approach, but a sample design is a good indication of feasibility.>

<If a phased approach would make sense indicate some logical phases. This may be because standards are evolving, because the problem is too big to solve at once, or because there are unknowns that won’t be resolved soon.>

Existing actors

<Indicate what existing actors could be used or might be affected by the profile.>

New actors

<List possible new actors>

Existing transactions

<Indicate how existing transactions might be used or might need to be extended.>

New transactions (standards used)

<Describe possible new transactions (indicating what standards would likely be used for each. Transaction diagrams are very helpful here. Feel free to go into as much detail as seems useful.>

Impact on existing integration profiles

<Indicate how existing profiles might need to be modified.>

New integration profiles needed

<Indicate what new profile(s) might need to be created.>

Breakdown of tasks that need to be accomplished

<A list of tasks would be helpful for the technical committee who will have to estimate the effort required to design, review and implement the profile.>

6. Support & Resources

<List groups that have expressed support for the proposal and resources that would be available to accomplish the tasks listed above.>

<Identify anyone who as indicated an interest in implementing/prototyping the Profile if it is published this cycle.>

7. Risks

<List technical or political risks that will need to be considered to successfully field the profile.>

8. Open Issues

<Point out any key issues or design problems. This will be helpful for estimating the amount of work and demonstrates thought has already gone into the candidate profile.>

9. Tech Cmte Evaluation

<The technical committee will use this area to record details of the effort estimation, etc.>

Effort Evaluation (as a % of Tech Cmte Bandwidth):

  • 35% for ...

Responses to Issues:

See italics in Risk and Open Issue sections

Candidate Editor:

TBA