Difference between revisions of "Simple Image and Numeric Report"

From IHE Wiki
Jump to navigation Jump to search
(New page: {{{1|'''This is a template page. CLICK HERE if you're not sure how to use it. DO NOT MODIFY this page unless you are changing the template for all future users.''...)
 
 
(29 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{{1|'''This is a template page. [[:Category:Templates|CLICK HERE]] if you're not sure how to use it. DO NOT MODIFY this page unless you are changing the template for all future users.'''
+
'''Simple Image and Numeric Report (SINR)''' specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.
 +
 
 +
__TOC__
 +
 
 +
==Summary==
 +
 
 +
Simple Image and Numeric Report (SINR) specifies how Diagnostic Radiology Reports (including images and numeric data) are created, exchanged, and used.
 +
 
 +
 
 +
 
 +
[[Image: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.  
  
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.''
 
  
''Your page name should simply be Full Profile Name Profile with spaces, with capitals, without the acronym. e.g. Scheduled Workflow Profile''
+
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.
  
  
''<Tell a user in one sentence what the profile is about (including the acronym) so they can decide if they're on the right page (and copy this one sentence description into the [[Profiles]] page as well), e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams. >''
+
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.  
  
}}}
 
__TOC__
 
  
==Summary==
+
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.
{{{2|''<Describe the profile in about a paragraph using user-oriented language.>''}}}
 
  
''<Insert a simple graphic that, at a glance, gives an impression of what the profile is about.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  Do not use an actor/transaction diagram here.>''
 
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
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.  
  
==Benefits==
 
  
''<List the key benefits the profile provides (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).>''
+
Viewing reports internal and external to the department requires a DICOM Structured Report-capable viewer.
  
==Details==
 
  
''<A few paragraphs, if appropriate, providing more details (in user-speak, not tech-speak) on what the profile does and how it works.>''
+
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==
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. >''
+
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:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[Image:SINR.PNG]]
  
 
==Specification==
 
==Specification==
  
 
'''Profile Status:''' [[Comments| Final Text]]   
 
'''Profile Status:''' [[Comments| Final Text]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
 
'''Documents:'''  
 
'''Documents:'''  
 
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  E.g.>''
 
  
 
[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 5 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.8 to 4.10, 4.14 to 4.19, and 4.23 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
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E provides additional informative text
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
:* ''<list standards on which this profile is based; if possible with links to sources>''
 
 
:* [http://dicom.nema.org DICOM]
 
:* [http://dicom.nema.org DICOM]
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
:* ...
 
  
 
==See Also==
 
==See Also==
 
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
 
  
 
'''Related Profiles'''
 
'''Related Profiles'''
  
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one>''
+
* [[Reporting Workflow]] [RWF] uses Simple Image & Numeric Reports as inputs to the reporting process.
 
 
'''Consumer Information'''
 
 
 
The [[{{{3|Profile FAQ Template}}}]] answers typical questions about what the Profile does. ''<Replace the link with a link to the actual FAQ page for the Profile>''
 
  
The [[{{{3|Profile Purchasing Template}}}]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
+
* [[Patient Information Reconciliation]] [PIR] is expected to reconcile Simple Image & Numeric Reports along with the rest of the patient data record.
  
'''Implementer Information'''
+
* [[Evidence Documents]] [ED] may be used as inputs for Simple Image and Numeric Reports.
  
The [[{{{3|Profile Implementation Template}}}]] provides additional information about implementing this Profile in software. ''<Replace the link with a link to the actual Implementation page for the Profile>''
+
* [[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Simple Image & Numeric Reports between sites over a network.
  
'''Reference Articles'''
+
* [[Portable Data for Imaging]] [PDI] can store Simple Image & Numeric Reports on media such as CDs.
  
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >''
+
* [[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Simple Image & Numeric Reports when importing.
  
 
 
This page is based on the [[Profile Template]]
 
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 
+
[[Category:RAD Profile]]
 
+
[[Category:DICOM]]
''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' [[Category:{{{3|Templates}}}]]
+
[[Category:HL7v2]]
 +
[[Category:CDA]]

Latest revision as of 06: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.