Difference between revisions of "Simple Image and Numeric Report"

From IHE Wiki
Jump to navigation Jump to search
Line 26: Line 26:
 
In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report object, which is submitted to the Report Manager. Once a report is sent to the Report Manager, the Report Creator relinquishes control of the report to the Report Manager.
 
In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report object, which is submitted to the Report Manager. Once a report is sent to the Report Manager, the Report Creator relinquishes control of the report to the Report Manager.
  
Reports are processed and modified by the Report Manager. This involves adding and changing report data as well as verifying draft reports. In all cases, any change in the report content by the Report Manager leads to the creation of a new DICOM Structured Report object. At any time, the Report Manager can transmit reports to the Report Repository for external access, but at a minimum the final report must be sent to the Report Repository. A Report Creator can effectively amend a report by submitting a new SR SOP Instance.
+
Reports are processed and modified by the Report Manager. This involves adding and changing report data as well as verifying draft reports. In all cases, any change in the report content by the Report Manager leads to the creation of a new DICOM Structured Report object.  
 +
 
 +
At any time, the Report Manager can transmit reports to the Report Repository for external access, but at a minimum the final report must be sent to the Report Repository. A Report Creator can effectively amend a report by submitting a new SR SOP Instance.
 +
 
 +
The Report Repository provides permanent storage of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by Report Readers.
 +
 
 +
A Report Reader provides a user interface to view DICOM Structured Reports that it retrieves from the Report Repository or External Report Repository Access.
  
The Report Repository provides permanent storage of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by Report Readers. A Report Reader provides a user interface to view DICOM Structured Reports that it retrieves from the Report Repository or External Report Repository Access.
 
 
The External Report Repository Access is a gateway to obtain other enterprise department reports, such as Laboratory and Pathology, from within the Imaging department. DICOM Structured Reports are queried and retrieved by a Report Reader from the External Report Repository Access.
 
The External Report Repository Access is a gateway to obtain other enterprise department reports, such as Laboratory and Pathology, from within the Imaging department. DICOM Structured Reports are queried and retrieved by a Report Reader from the External Report Repository Access.
  
 
The Enterprise Report Repository receives diagnostic reports in HL7 format.
 
The Enterprise Report Repository receives diagnostic reports in HL7 format.
 +
 
The Simple Image Report and Simple Image and Numeric Reports are required minimally to have the functionality defined in template TID 2000. Creators may introduce increased complexity as long as it conforms to the SOP class. The templates referenced in the Technical Framework are included in DICOM Part 16.
 
The Simple Image Report and Simple Image and Numeric Reports are required minimally to have the functionality defined in template TID 2000. Creators may introduce increased complexity as long as it conforms to the SOP class. The templates referenced in the Technical Framework are included in DICOM Part 16.
 
The report structure defined is simple: a title, an observation context, and one or more sections, each with a heading, observation context, text, image references, and optionally coded measurements.  Some elements can also be coded to facilitate computer searches.  Such reports can be input to the formal diagnostic report, thus avoiding re-entry of information.
 
  
 
==Systems Affected==
 
==Systems Affected==

Revision as of 10:47, 20 March 2008

Simple Image and Numeric Report (SINR) specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.

Summary

The Simple Image and Numeric Report (SINR) Integration Profile facilitates the growing use of digital dictation, voice recognition, and specialized reporting packages. The SINR profile facilitates the creation, management, distribution, storage, and viewing of reports created in imaging facilities.

Benefits

The key benefits of Simple Image Numeric Report profile are as follows:

  • DICOM SR, enables maximum interoperability in Imaging Departments
  • Export to Clinical Data Repositories with HL-7 V.2 defined mapping
  • Non-transcription based information capture systems support, including;
  • Numerical measurements from image processing applications
  • Links to images stored in the image repository
  • machine searchable structured content
  • Integrated with the Reporting Workflow
  • Adaptable to CDA and XML interfacing

Details

The Simple Image and Numeric Report (SINR) Integration Profile facilitates the creation, management, distribution, storage, and viewing of reports created in imaging facilities.

In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report object, which is submitted to the Report Manager. Once a report is sent to the Report Manager, the Report Creator relinquishes control of the report to the Report Manager.

Reports are processed and modified by the Report Manager. This involves adding and changing report data as well as verifying draft reports. In all cases, any change in the report content by the Report Manager leads to the creation of a new DICOM Structured Report object.

At any time, the Report Manager can transmit reports to the Report Repository for external access, but at a minimum the final report must be sent to the Report Repository. A Report Creator can effectively amend a report by submitting a new SR SOP Instance.

The Report Repository provides permanent storage of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by Report Readers.

A Report Reader provides a user interface to view DICOM Structured Reports that it retrieves from the Report Repository or External Report Repository Access.

The External Report Repository Access is a gateway to obtain other enterprise department reports, such as Laboratory and Pathology, from within the Imaging department. DICOM Structured Reports are queried and retrieved by a Report Reader from the External Report Repository Access.

The Enterprise Report Repository receives diagnostic reports in HL7 format.

The Simple Image Report and Simple Image and Numeric Reports are required minimally to have the functionality defined in template TID 2000. Creators may introduce increased complexity as long as it conforms to the SOP class. The templates referenced in the Technical Framework are included in DICOM Part 16.

Systems Affected

Systems which are expected to have implemented actors from this profile include:

  • Digital Dictation Systems
  • Voice Recognition Systems
  • specialized reporting packages
  • Enterprise-wide information systems that manage the Electronic Medical Record
  • Radiology departmental information systems that manage Radiology Reports (i.e., radiology information system (RIS))
  • Radiology image & Report management/archiving systems that manage Radiology Reports (i.e., picture archiving and communication system (PACS))

Actors & Transactions:

SINR.JPG

Specification

Profile Status: Final Text

Documents:

IHE Radiology Technical Framework:

  • Vol. 1 - Section 6 documents the profile
  • Vol. 2 - Sections 4.24 to 4.28 document specific transactions

Underlying Standards:

See Also

Related Profiles

The SINR profile is a dependency to Reporting Workflow. This integrtion Profile defines the Workflow associated with managing the Diagnostic Reports crearted by this profile.

Other documents which are sometimes referred to as “reports” and may be encoded using DICOM SR (for example, procedure reports, CAD results and echocardiography measurement reports) however such documents do not follow the same kind of verification and distribution process described in this profile. These other documents serve different purposes and are instead addressed in the Evidence Documents profile.