Difference between revisions of "Nuclear Medicine Image"

From IHE Wiki
Jump to navigation Jump to search
(Created page with " ''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. Delete text in italic...")
 
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
''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.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
 
  
 
'''Nuclear Medicine Image (NMI)''' specifies how Nuclear Medicine images and result screens are created, exchanged, used and displayed.
 
'''Nuclear Medicine Image (NMI)''' specifies how Nuclear Medicine images and result screens are created, exchanged, used and displayed.
Line 7: Line 5:
  
 
==Summary==
 
==Summary==
''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases)Don't get into how it works, leave that to the Details section.>''
+
The Nuclear Medicine Image (NMI) Profile specifies basic '''display capabilities''' that are required in nuclear medicine, and provides vendors information as to what features users expect in products that "work well" with nuclear medicine images.   Portions of the profile deal with both '''cardiac''' and '''general nuclear medicine'''Other sections of the profile ensure that nuclear medicine images can be stored and retrieved properly, and options deal with '''exporting result screens''' and viewing of tomographic (SPECT) studies.
  
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+
[[Image:Nm-diagram.png]]
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
==Benefits==
  
==Benefits==
+
In many medical centers nuclear medicine images are interpreted on dedicated nuclear medicine workstations.  However, nuclear medicine networks have increasingly been linked to hospital and enterprise PACS, to allow images to be viewed by other physicians.  This profile helps ensure that others can view nuclear medicine images properly, and that the images are stored in a manner that allows accurate retrieval and presentation.
  
''<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).  Consider using a bullet list for readability.  If possible, identify benefits that help users and vendors make the business case for the profile.>''
+
Complying with NMI can help: 
 +
* '''Nuclear medicine physicians''' by allowing them to distribute their images with confidence that they will be displayed well, and stored in a manner that will ensure they they will be fully functional on retrieval.
 +
* '''General radiologists''', by providing proper display of comparison nuclear medicine images.  
 +
* '''Consulting cardiologists''', by making it easier for them to view nuclear medicine cardiac images formatted properly, and view clinical application result screens (both static and dynamic) on general purpose DICOM viewers.  
 +
* '''Patients's physicians''', by making it easier for them to view nuclear medicine images and clinical application results when planning patient treatments.
  
 
==Details==
 
==Details==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
When nuclear medicine (NM) images are stored using DICOM, they are formatted as DICOM NM image objects.  DICOM NM objects have a number of features that differ from more common DICOM CT objects for example.  An NM object contains multiple frames, uses color presentations, etc.  Some PACS, particularly older ones, do not deal well with these features and do a poor job of displaying NM images.  The NMI profile clarifies the usage of these NM object details, and explains what types of image displays are expected by the user.
  
''<If the user might be familiar with the mechanisms used by the profile, you can mention them hereE.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
+
When creating NM images, modalities are required to populate attributes with key clinical details and use the multi-frame vectors structures in a standardized way, making datasets more predictable for processing and display systems.
 +
 
 +
When manipulating NM images, users typically need image controls that are slightly different than the controls needed for CT or plain radiographs.  This profile details the functions and types of controls required for NM display, while leaving the exact user interface details up to the various vendors.
 +
 
 +
Cardiology organizations have agreed that cardiac nuclear medicine images should be displayed in a standardized format, in order to avoid misinterpretation.  The NMI profile provides details of that format to vendors, so that they can be in compliance with the standards.
 +
 
 +
Since some systems deal primarily with cardiac images, and other systems may deal primarily with general NM images, the image display portion of this profile has two main options--general and cardiac--and one or both may be chosen for implementation.
 +
 
 +
The Result Screen Export option specifies how result screens can be saved by clinical applications and later displayed on general purpose display stationsStatic result screens are stored as DICOM Secondary Capture objects.  Dynamic result screens (e.g. with cardiac cine portions) are stored as DICOM Multiframe Secondary Capture objects.
 +
 
 +
Other options deal with creation of multiplanar reconstructions of tomographic (SPECT) data.
  
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 
 
 
==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. and for each, how it would participate.>''
 
  
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* Modalities may create, store, and transmit NM images.
* ''Display systems may query, retrieve and display Evidence Documents.''
+
* PACS systems may store, manage, and/or display NM images.
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
* Display systems may query, retrieve and display NM images.
 +
* Workstations may retrieve, process and display NM images, and may create evidence documents.
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[Image:Nmi-actors.png]]
  
 
==Specification==
 
==Specification==
Line 42: Line 52:
 
'''Documents:'''  
 
'''Documents:'''  
  
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Supp_NMI_TI_2007_05_17.pdf NMI Supplement] - 2007.05.17
 
 
[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 (SWF 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
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
 
 
:* [http://dicom.nema.org DICOM]
 
:* [http://dicom.nema.org DICOM]
:* [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'''
 +
 
 +
* [[Scheduled Workflow]] [SWF] can manage the production of NM Images.
  
 +
* [[Patient Information Reconciliation]] [PIR] is expected to reconcile NM Images along with the rest of the patient data record.
  
'''Related Profiles'''
+
* [[Reporting Workflow]] [RWF] may use NM Images as inputs to the reporting process.
 +
 
 +
* [[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share NM Images between sites over a network.
  
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
+
* [[Portable Data for Imaging]] [PDI] can store NM Images on media such as CDs.
  
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
* [[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of NM Images when importing.
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
  
  
Line 91: Line 94:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:RAD Profile]]
 +
[[Category:DICOM]]

Latest revision as of 15:04, 25 May 2018

Nuclear Medicine Image (NMI) specifies how Nuclear Medicine images and result screens are created, exchanged, used and displayed.

Summary

The Nuclear Medicine Image (NMI) Profile specifies basic display capabilities that are required in nuclear medicine, and provides vendors information as to what features users expect in products that "work well" with nuclear medicine images. Portions of the profile deal with both cardiac and general nuclear medicine. Other sections of the profile ensure that nuclear medicine images can be stored and retrieved properly, and options deal with exporting result screens and viewing of tomographic (SPECT) studies.

Nm-diagram.png

Benefits

In many medical centers nuclear medicine images are interpreted on dedicated nuclear medicine workstations. However, nuclear medicine networks have increasingly been linked to hospital and enterprise PACS, to allow images to be viewed by other physicians. This profile helps ensure that others can view nuclear medicine images properly, and that the images are stored in a manner that allows accurate retrieval and presentation.

Complying with NMI can help:

  • Nuclear medicine physicians by allowing them to distribute their images with confidence that they will be displayed well, and stored in a manner that will ensure they they will be fully functional on retrieval.
  • General radiologists, by providing proper display of comparison nuclear medicine images.
  • Consulting cardiologists, by making it easier for them to view nuclear medicine cardiac images formatted properly, and view clinical application result screens (both static and dynamic) on general purpose DICOM viewers.
  • Patients's physicians, by making it easier for them to view nuclear medicine images and clinical application results when planning patient treatments.

Details

When nuclear medicine (NM) images are stored using DICOM, they are formatted as DICOM NM image objects. DICOM NM objects have a number of features that differ from more common DICOM CT objects for example. An NM object contains multiple frames, uses color presentations, etc. Some PACS, particularly older ones, do not deal well with these features and do a poor job of displaying NM images. The NMI profile clarifies the usage of these NM object details, and explains what types of image displays are expected by the user.

When creating NM images, modalities are required to populate attributes with key clinical details and use the multi-frame vectors structures in a standardized way, making datasets more predictable for processing and display systems.

When manipulating NM images, users typically need image controls that are slightly different than the controls needed for CT or plain radiographs. This profile details the functions and types of controls required for NM display, while leaving the exact user interface details up to the various vendors.

Cardiology organizations have agreed that cardiac nuclear medicine images should be displayed in a standardized format, in order to avoid misinterpretation. The NMI profile provides details of that format to vendors, so that they can be in compliance with the standards.

Since some systems deal primarily with cardiac images, and other systems may deal primarily with general NM images, the image display portion of this profile has two main options--general and cardiac--and one or both may be chosen for implementation.

The Result Screen Export option specifies how result screens can be saved by clinical applications and later displayed on general purpose display stations. Static result screens are stored as DICOM Secondary Capture objects. Dynamic result screens (e.g. with cardiac cine portions) are stored as DICOM Multiframe Secondary Capture objects.

Other options deal with creation of multiplanar reconstructions of tomographic (SPECT) data.

Systems Affected

  • Modalities may create, store, and transmit NM images.
  • PACS systems may store, manage, and/or display NM images.
  • Display systems may query, retrieve and display NM images.
  • Workstations may retrieve, process and display NM images, and may create evidence documents.

Actors & Transactions:

Nmi-actors.png

Specification

Profile Status: Trial Implementation

Documents:

Underlying Standards:

See Also

Related Profiles


Consumer Information

The 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 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>

Implementer Information

The 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>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >


This page is based on the Profile Overview Template