Difference between revisions of "Simple Image and Numeric Report"

From IHE Wiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Simple Image and Numeric Report (SINR) specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.
+
'''Simple Image and Numeric Report (SINR)''' specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.
  
 
__TOC__
 
__TOC__
Line 5: Line 5:
 
==Summary==
 
==Summary==
  
The Simple Image and Numeric Report (SINR) Integration Profile facilitates the growing use of digital dictation, voice recognition, and specialized reporting packages.
+
Simple Image and Numeric Report (SINR) specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.
 +
 
  
The content structure of the report 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.
+
 
 +
[[Image:SINR_diag_1.png]]
  
 
==Benefits==
 
==Benefits==
Line 26: Line 28:
 
The Simple Image and Numeric Report (SINR) Integration Profile facilitates the creation, management, distribution, storage, and viewing of reports created in imaging facilities.  
 
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.  
+
The content structure uses the DICOM Structured Report for a simple imaging report. The content structure 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. The Report complexity is extensible, limited only to the constraints of DICOM.
  
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.  
+
In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report. The created report is submitted for management, distribution and storage by departmental information system.  
  
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.
+
Once the initial report is submitted, the reports are processed until the report is final. This may involve adding and changing report data as well as verifying the draft reports. Previous draft versions are maintained.  Once final, the report may be amended with updates.
  
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.
+
Permanent storage of the reports is maintained through the use of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by known DICOM queries.
 +
 
 +
 
 +
Viewing reports internal and external to the department requires a DICOM Structured Report-capable viewer.
 +
 
 +
 
 +
The Integration Profile allows for the flexibility of distributing the report external to the department at any time. But at a minimum, the final report will be made available for distribution.  The report may be distributed outside the department by an HL7 format.  The DICOM Structured Report may be queried and retrieved by an any DICOM SR-capable system.
  
 
==Systems Affected==
 
==Systems Affected==
 
Systems which are expected to have implemented actors from this profile include:
 
Systems which are expected to have implemented actors from this profile include:
:* Digital Dictation Systems
+
:* Digital Dictation Systems, with the ability to create and modify reports
:* Voice Recognition Systems
+
:* Voice Recognition Systems, with the ability to create and modify reports
:* specialized reporting packages
+
:* specialized reporting packages, with the ability to create and modify reports
:* Enterprise-wide information systems that manage the Electronic Medical Record  
+
:* Enterprise-wide information systems that manage the Electronic Medical Record for recieving reports
 
:* Radiology departmental information systems that manage Radiology Reports (i.e., radiology information system (RIS))  
 
:* 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))  
 
:* Radiology image & Report management/archiving systems that manage Radiology Reports (i.e., picture archiving and communication system (PACS))  
Line 53: Line 57:
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
[[Image:SINR.JPG]]
+
[[Image:SINR.PNG]]
  
 
==Specification==
 
==Specification==
Line 62: Line 66:
  
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 6 documents the profile
+
:* [http://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol1.pdf Vol. 1] - Section 6 documents the profile
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.24 to 4.28 document specific transactions
+
:* [https://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_TF_Vol2.pdf Vol. 2] - Sections 4.24 to 4.28 document specific transactions
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
Line 73: Line 77:
 
'''Related Profiles'''
 
'''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.
+
* [[Reporting Workflow]] [RWF] uses Simple Image & Numeric Reports as inputs to the reporting process.
 +
 
 +
* [[Patient Information Reconciliation]] [PIR] is expected to reconcile Simple Image & Numeric Reports along with the rest of the patient data record.
 +
 
 +
* [[Evidence Documents]] [ED] may be used as inputs for Simple Image and Numeric Reports.
 +
 
 +
* [[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Simple Image & Numeric Reports between sites over a network.
 +
 
 +
* [[Portable Data for Imaging]] [PDI] can store Simple Image & Numeric Reports on media such as CDs.
 +
 
 +
* [[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Simple Image & Numeric Reports when importing.
  
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.
 
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:RAD Profile]]
 +
[[Category:DICOM]]
 +
[[Category:HL7v2]]
 +
[[Category:CDA]]

Latest revision as of 07:08, 7 September 2021

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

Summary

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


SINR diag 1.png

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.


The content structure uses the DICOM Structured Report for a simple imaging report. The content structure 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. The Report complexity is extensible, limited only to the constraints of DICOM.


In the initial stage of diagnostic reporting, a reading physician records the diagnosis by generating a draft DICOM Structured Report. The created report is submitted for management, distribution and storage by departmental information system.


Once the initial report is submitted, the reports are processed until the report is final. This may involve adding and changing report data as well as verifying the draft reports. Previous draft versions are maintained. Once final, the report may be amended with updates.


Permanent storage of the reports is maintained through the use of DICOM Structured Reports. It also allows reports to be queried and retrieved throughout the enterprise by known DICOM queries.


Viewing reports internal and external to the department requires a DICOM Structured Report-capable viewer.


The Integration Profile allows for the flexibility of distributing the report external to the department at any time. But at a minimum, the final report will be made available for distribution. The report may be distributed outside the department by an HL7 format. The DICOM Structured Report may be queried and retrieved by an any DICOM SR-capable system.

Systems Affected

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

  • Digital Dictation Systems, with the ability to create and modify reports
  • Voice Recognition Systems, with the ability to create and modify reports
  • specialized reporting packages, with the ability to create and modify reports
  • Enterprise-wide information systems that manage the Electronic Medical Record for recieving reports
  • 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.PNG

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

  • Reporting Workflow [RWF] uses Simple Image & Numeric Reports as inputs to the reporting process.