Difference between revisions of "Remote Reporting for Imaging (TeleRadiology) - Proposal"

From IHE Wiki
Jump to navigation Jump to search
Line 9: Line 9:
 
==2. The Problem==
 
==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.  eReferral specifies a Workflow Definition 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.   
+
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.  eReferral specifies a Workflow Definition 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 this initial step has the capability to attain efficiencies and reduce cost at a macro-scale level:
 
Cross-enterprise image sharing, beyond this initial step has the capability to attain efficiencies and reduce cost at a macro-scale level:
Line 16: Line 16:
 
*Facilitate assignment of studies to physicians that are best qualified to read them (e.g., a SPECT expert may be leveraged across the community)
 
*Facilitate assignment of studies to physicians that are best qualified to read them (e.g., a SPECT expert may be leveraged across the community)
  
Currently, to meet this need, HCIT suppliers have built proprietary systems with non-standard methods for managing this workflow. 
 
 
<Summarize the integration problem. What doesn’t work, or what needs to work.>
 
 
<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>
 
 
==3. Key Use Case==
 
==3. Key Use Case==
  

Revision as of 14:13, 7 July 2014

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

  • Proposal Editor: Chris Lindop
  • 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

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. eReferral specifies a Workflow Definition 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 this 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)

3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.> <Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>

4. Standards and Systems

<List existing systems that are/could be involved in the problem/solution.> <If known, list standards which might be relevant to the solution>

5. Discussion

<Include additional discussion or consider a few details which might be useful for the detailed proposal> <Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.> <What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?> <What are some of the risks or open issues to be addressed?>

<This is the brief proposal. Try to keep it to 1 or at most 2 pages>