Difference between revisions of "Evidence Documents"

From IHE Wiki
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
The Evidence Documents (ED) Profile specifies how data objects such as digital measurements are created, exchanged, and used.  
+
'''Evidence Documents (ED)''' specifies how data objects such as digital measurements are created, exchanged, and used.  
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
−
{{{2|''<Describe the profile in about a paragraph using user-oriented language.>''}}}
 
  
−
The Evidence Documents Profile allows detailed non-image information, such as measurements, CAD results, procedure logs, etc. to be made available as input to the process of generating a diagnostic report either as additional evidence for the reporting physician or in some cases for selected items in the Evidence Document to be included in the diagnostic report.
+
The Evidence Documents Profile allows data such as OB measurements, CAD results, procedure logs, etc. to be encoded, stored and managed just like DICOM images.
−
The production of Evidence Documents, is managed by the Scheduled Workflow Profile and/or the Post Processing Workflow Profile. As such, the Evidence Document Profile is required to be supported together with one or the other of those two profiles.
+
:* The modality can store them to PACS.
−
Evidence Documents represent one of the inputs to the reporting process described in the Reporting Workflow Profile and may provide details which get included in diagnostic reports described in the Simple Image & Numeric Reports Profile.
+
:* A reporting station can query and retrieve them along with the images.
−
It should be noted that while Key Image Notes meet the definition of Evidence Documents, they are a special case which is dealt with separately in the Key Image Notes Profile for historical reasons.
 
  
−
''<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.>''
+
Because they are structured and coded data, the receiving system can reliably parse the data and do things like:
 +
:* Compare measurements against normal ranges
 +
:* Insert measurement values into the correct part of a diagnostic report
 +
:* Calculate the different from the previous measurement on the same patient
 +
:* Plot measurements taken from several different studies on a curve
  
−
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
'''<GRAPHIC: Thinking of some Evidence Document icon in the middle. Coming into it from the left, Echo measurements, Chest CAD, Procedure Log.  Going out to the right, Report/Reading Workstation, Clinical trend graph, Orthopedic Planning station maybe>'''
  
 
==Benefits==
 
==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).>''
+
* Avoids potential errors from parsing raw text (ambiguous measurement name, unclear units, etc.)
 +
* Digital measurements from modalities stay digital
 +
** Faster, automated, reliable
 +
** Avoids errors from mis-reading or mis-dictating screen printed paper copies
 +
** Avoids errors from mis-heard or mis-typed dictations
 +
** Avoids need for radiologist to retrieve the measurement form and compare the numbers when verifying the transcribed report
 +
* Opens the door to additional decision support, clinical pathways and other automation
  
 
==Details==
 
==Details==
  
−
''<A few paragraphs, if appropriate, providing more details (in user-speak, not tech-speak) on what the profile does and how it works.>''
+
These non-image data objects may be produced by a number of different systems.
 +
 
 +
A Modality that performs measurements during a study, for example an ultrasound system with a cardiac package for measuring cardiac dimensions and calculating values like ejection fractions might create an Evidence Document containing those values and send it to the archive together with the study images.
 +
 
 +
A CAD workstation performing, post-processing on a Chest study might create an Evidence Document containing the results of the CAD analysis and add it to the archive.
 +
 
 +
Evidence Documents are based on DICOM Structured Reports (SR) which is sort of like XML for DICOM.  Most Evidence Documents will be based on SR Templates defined by DICOM for particular purposes.  For example, DICOM has templates for:
 +
:* OB/GYN Reports
 +
:* Mammography CAD Results
 +
:* Echocardiography Procedure Reports
 +
:* Cardiac Stress Testing Results
 +
 
 +
Other templates exist and more are being added each year.  In the absence of a relevant template, a system can follow one of the general purpose templates.  
  
 
==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. >''
+
 
 +
* Imaging Acquisition Modalities might create, retrieve and/or process Evidence Documents
 +
* Clinical Workstations might also create, retrieve and/or process them
 +
* CAD Systems may create them
 +
* PACS may store and manage them
 +
* Display systems may query, retrieve and display them
 +
* Reporting workstations may retrieve, process and include details from them in reports
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[Image:ED-Actors.PNG|center|]]
  
 
==Specification==
 
==Specification==
Line 37: Line 63:
  
 
[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/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.10, and [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Sections 4.43 to 4.45 document specific transactions
+
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol1.pdf Vol. 1] - Section 5 (ED Profile)
 +
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol2.pdf Vol. 2] - Sections 4.10
 +
:* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD_TF_Vol3.pdf Vol. 3] - Sections 4.43 to 4.45
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
Line 47: Line 75:
 
'''Related Profiles'''
 
'''Related Profiles'''
  
−
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one>''
+
* [[Scheduled Workflow]] [SWF] and/or [[Post-Processing Workflow]] [PPWF] manage the production of Evidence Documents.  One of these profiles must be implemented together with the Evidence Documents Profile.
 +
 
 +
* [[Patient Information Reconciliation]] [PIR] is expected to reconcile Evidence Documents along with the rest of the patient data record.
 +
 
 +
* [[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.
 +
 
 +
* [[Simple Image and Numeric Report]] [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.
  
 
'''Consumer Information'''
 
'''Consumer Information'''
Line 67: Line 107:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:RAD Profile]]
 +
[[Category:DICOM]]

Latest revision as of 19:36, 27 August 2019

Evidence Documents (ED) specifies how data objects such as digital measurements are created, exchanged, and used.

Summary

The Evidence Documents Profile allows data such as OB measurements, CAD results, procedure logs, etc. to be encoded, stored and managed just like DICOM images.

  • The modality can store them to PACS.
  • A reporting station can query and retrieve them along with the images.

Because they are structured and coded data, the receiving system can reliably parse the data and do things like:

  • Compare measurements against normal ranges
  • Insert measurement values into the correct part of a diagnostic report
  • Calculate the different from the previous measurement on the same patient
  • Plot measurements taken from several different studies on a curve

<GRAPHIC: Thinking of some Evidence Document icon in the middle. Coming into it from the left, Echo measurements, Chest CAD, Procedure Log. Going out to the right, Report/Reading Workstation, Clinical trend graph, Orthopedic Planning station maybe>

Benefits

  • Avoids potential errors from parsing raw text (ambiguous measurement name, unclear units, etc.)
  • Digital measurements from modalities stay digital
    • Faster, automated, reliable
    • Avoids errors from mis-reading or mis-dictating screen printed paper copies
    • Avoids errors from mis-heard or mis-typed dictations
    • Avoids need for radiologist to retrieve the measurement form and compare the numbers when verifying the transcribed report
  • Opens the door to additional decision support, clinical pathways and other automation

Details

These non-image data objects may be produced by a number of different systems.

A Modality that performs measurements during a study, for example an ultrasound system with a cardiac package for measuring cardiac dimensions and calculating values like ejection fractions might create an Evidence Document containing those values and send it to the archive together with the study images.

A CAD workstation performing, post-processing on a Chest study might create an Evidence Document containing the results of the CAD analysis and add it to the archive.

Evidence Documents are based on DICOM Structured Reports (SR) which is sort of like XML for DICOM. Most Evidence Documents will be based on SR Templates defined by DICOM for particular purposes. For example, DICOM has templates for:

  • OB/GYN Reports
  • Mammography CAD Results
  • Echocardiography Procedure Reports
  • Cardiac Stress Testing Results

Other templates exist and more are being added each year. In the absence of a relevant template, a system can follow one of the general purpose templates.

Systems Affected

  • Imaging Acquisition Modalities might create, retrieve and/or process Evidence Documents
  • Clinical Workstations might also create, retrieve and/or process them
  • CAD Systems may create them
  • PACS may store and manage them
  • Display systems may query, retrieve and display them
  • Reporting workstations may retrieve, process and include details from them in reports

Actors & Transactions:

ED-Actors.PNG

Specification

Profile Status: Final Text

Documents:

IHE Radiology Technical Framework:

Underlying Standards:

See Also

Related Profiles

Consumer Information

The Evidence Documents FAQ answers typical questions about what the Profile does.

Evidence Documents Purchasing describes considerations when purchasing equipment to deploy this Profile.

Implementer Information

Evidence Documents Implementation provides additional information about implementing this Profile in software.

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >


This page is based on the Profile Template

Retrieved from "http://wiki.ihe.net/index.php?title=Evidence_Documents&oldid=116951"