Reporting Whitepaper: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Kevino (talk | contribs)
mNo edit summary
Kevino (talk | contribs)
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This Wiki page is currently the "live" version of the whitepaper.  It will later be re-integrated with the [ftp://ftp.ihe.net/Reporting_Task_Force/ReportingWhitepaper0.3b.doc Word Document].
This Wiki page is currently the "live" version of the whitepaper.  It will later be re-integrated with the [ftp://ftp.ihe.net/Reporting_Task_Force/ReportingWhitepaper0.3b.doc Word Document].
There seems to be some Really Good, Really Relevant material discussed at the Intersociety Summer Conference, July 27-29, 2007. <Upload Program and Link Here>.




Line 17: Line 19:
==Whitepaper Structure==
==Whitepaper Structure==


[[Reporting Whitepaper - Section 1|'''Section 1''']] presents working premises.  That way if there is disagreement about the thinking/biases that underlie the whitepaper, they can be challenged and discussed directly.
[[Reporting Whitepaper - Section 1|'''Section 1''']] presents working premises so any disagreement about the thinking/biases underlying the whitepaper can be challenged and discussed directly.
 
 
[[Reporting Whitepaper - Section 2|'''Section 2''']] describes the Report itself (content).
:* what information does it contain and how is it structured
 
[[Reporting Whitepaper - Section 3|'''Section 3''']] examines the Reporting Process (workflow/dataflow).
:* identify the tasks surrounding reporting, the data produced and the inputs required


As a first step toward consensus on the nature of the problem:
[[Reporting Whitepaper - Section 4|'''Section 4''']] describes technical issues which need to be addressed.
:[[Reporting Whitepaper - Section 2|'''Section 2''']] tries to nail down the Report itself (content)
:[[Reporting Whitepaper - Section 3|'''Section 3''']] examines the Reporting Process (workflow/dataflow).


[[Reporting Whitepaper - Section 4|'''Section 4''']] describes individual technical issues which will need to be addressed.
[[Reporting Whitepaper - Section 5|'''Section 5''']] presents and evaluates parts of the solution.
:* for each data, identify formats for encoding and mechanisms for transport
:* select mechanisms for managing the workflow that surrounds the creation, manipulation and transportation of the data.


[[Reporting Whitepaper - Section 5|'''Section 5''']] presents and evaluates
[[Reporting Whitepaper - Section 6|'''Section 6''']] introduces several real-world (Radiology) reporting environments
:* promising formats for encoding the data;
:* describe the current typical practices (baseline expectations) and associated problems
:* promising mechanisms for transporting the encoded data from place to place; and
:* describe how the solution would be applied to their workflow/architecture
:* promising mechanisms for managing the workflow that surrounds the creation, manipulation and transportation of the data.


[[Reporting Whitepaper - Section 6|'''Section 6''']] introduces several different (Radiology) reporting environments, and describes how the technologies would be applied to their workflow/architecture.  The current “state of the art” may also be described to present a better picture of user expectations and current problems.
:[[Reporting Whitepaper - Section 6.1|'''Section 6.1''']] A Radiology Department (i.e. Hospital)  
:[[Reporting Whitepaper - Section 6.1|'''Section 6.1''']] A Radiology Department (i.e. Hospital)  
:[[Reporting Whitepaper - Section 6.2|'''Section 6.2''']] An Imaging Center
:[[Reporting Whitepaper - Section 6.2|'''Section 6.2''']] An Imaging Center
:[[Reporting Whitepaper - Section 6.3|'''Section 6.3''']] A Reporting Service (e.g. Nighthawk)  
:[[Reporting Whitepaper - Section 6.3|'''Section 6.3''']] A Reporting Service (e.g. Nighthawk, NightShift)  
   
   
[[Reporting Whitepaper - Section 7|'''Section 7''']] proposes activities to implement/deploy the conclusions above.
[[Reporting Whitepaper - Section 7|'''Section 7''']] proposes activities to implement/deploy the conclusions above.

Latest revision as of 16:21, 8 August 2007

This Wiki page is currently the "live" version of the whitepaper. It will later be re-integrated with the Word Document.

There seems to be some Really Good, Really Relevant material discussed at the Intersociety Summer Conference, July 27-29, 2007. <Upload Program and Link Here>.


The optimistic goal of the whitepaper is to:

  • Describe the “problem” and related details
  • Break it down into component pieces
  • Document some technologies that could improve things
  • Propose some steps forward for coming years, including:
    • New IHE Profiles
    • IHE Profiles to be modified
    • IHE Profiles to be retired

The plan is to facilitate discussion with other IHE Domains and hopefully reach some cross-Domain consensus so we are moving in compatible directions.

Since this whitepaper is a contribution of IHE Radiology to the IHE Reporting Taskforce, the focus and viewpoint may reflect its origins. Contributions from other Domains to fill in blind-spots and balance the viewpoint are welcome.

Whitepaper Structure

Section 1 presents working premises so any disagreement about the thinking/biases underlying the whitepaper can be challenged and discussed directly.


Section 2 describes the Report itself (content).

  • what information does it contain and how is it structured

Section 3 examines the Reporting Process (workflow/dataflow).

  • identify the tasks surrounding reporting, the data produced and the inputs required

Section 4 describes technical issues which need to be addressed.

Section 5 presents and evaluates parts of the solution.

  • for each data, identify formats for encoding and mechanisms for transport
  • select mechanisms for managing the workflow that surrounds the creation, manipulation and transportation of the data.

Section 6 introduces several real-world (Radiology) reporting environments

  • describe the current typical practices (baseline expectations) and associated problems
  • describe how the solution would be applied to their workflow/architecture
Section 6.1 A Radiology Department (i.e. Hospital)
Section 6.2 An Imaging Center
Section 6.3 A Reporting Service (e.g. Nighthawk, NightShift)

Section 7 proposes activities to implement/deploy the conclusions above.