Ophthalmic Tools

IHE Eye Care - DICOM Interoperability Consultants: Specializing in Digital Imaging Management, IHE, DICOM and EHR Workflow Solutions in Ophthalmology
Home
IHE Eye Care Overview
EC Workflow
EC Charge Posting
EC Evidence Documents
EC Displayable Reports
IHE Technical Framework
Integration Statement
RFQ / RFP Specifications
About Us
TSG Integrations
IHE International
DICOM Overview
HL7 Overview
Ocutouch
Innova Systems
Site Map
links
Contact Us
 
Under Development - April - May 2011 

Eye Care Evidence Documents*

 (ECED)

 

 

The Eye Care Evidence Documents Profile defines information such as observations, measurements, and results (i.e., evidence documents), to be output by devices, such as acquisition systems and other workstations; to be stored and managed by archival systems; and to be retrieved and presented or used by display and reporting systems.

 

This allows detailed non-image information, such as measurements, post processing, etc. to be  made available as input to the process of generating a clinical Report, either as additional evidence for the reporting healthcare provider, or in some cases for selected items in the Evidence Document to be included in the report.

 

The full specification of the Evidence Documents Profile is found in RAD TF- 1:14. This section adds the eye care specific options for that definition. The main extension for eye care is the use  of DICOM Encapsulated PDF.*

 

 

 http://wiki.ihe.net/index.php?title=Eye_Care_Evidence_Documents

 

 IHE EyeCare "Actors"



Actors:

Evidence Creator


Transactions

Storage commitment

Modality Images/EvidenceStored


Acquisition Modality

Transactions

Storage commitment

Modality Images/EvidenceStored


ImageManager/Image Archive


Transactions

Storage commitment

Modality Images/EvidenceStored

Query Evidence Documents

Retrieve Evidence Documents


Image Display

Query Evidence Documents

Retrieve Evidence Documents


5.3 Eye Care Evidence Document Process Flow

Evidence Documents belong to the family of Evidence Objects such as measurements,

post processing, images, presentation states, DICOM Structured Reports, etc. These

are objects 1455

generated as a result of creating eye care diagnostic information after the patient has

 left the acquisition stage of the procedure.

As with other Evidence Objects, Evidence Documents are used in the process of

creating a Diagnostic Report, either by reviewing or interpreting the Evidence

Document contents, or by copying selected parts into the Report. Evidence

Documents represent the uninterrupted 1460 information that is primarily managed

and used inside an eye care department, although distribution outside the

department is not precluded.


Apply Measurements

Retrieve Evidence Documents [RAD-45]

Query Evidence Documents [EYECARE-4]

Evidence Document Stored [EYECARE-2]

Retrieve Images [EYECARE-3]

Image Manager/ Image Archive

Storage Commitment [CARD-3]

Query Images [EYECARE-5]

Perform Measurements

Image Display

Evidence Creator/ Image Display

5.4 Eye Care Evidence Documents Use Cases

This section describes the specific use cases defined for the Eye Care

Evidence Documents Profile.

5.4.1 Eye Care Evidence Documents Being Created by Acquisition

 Modality

A typical use case for evidence documents include them being generated at the

Acquisition 1470 Modality. A technician performs the acquisition, and the

 instrument performs implicit post-processing immediately following the acquisition.

This may be entirely automatic, or require limited user inputs. An example is

glaucoma progression analysis performed on visual field analyzers, or the RNFL

analysis performed on an OPT device. The instrument provides the evidence

document at the end of the acquisition cycle. The transaction diagram for this

 use case is 1475 already in Eye Care Workflow Integration Profile. IHE Eye

Care Technical Framework, Volume.1 (EYECARE TF-1): Profiles

 

 

Note 2: The DICOM standard does not define use of a specific version of PDF when encapsulated

 PDF is used. This may result in incorrect display of reports when using a different PDF version

of software from that which was used to create the files. Other issues arise when using only PDF

with pixel data as the files are large and have difficulties with display. IHE EYECARE defines

specific versions required for support see EYECARE TF-2: 4.2.

__________________________________________________________ __________________________________________________________________

 Transaction Descriptions & "What they Do"

*Information obtained,interpreted from and credit is given to : IHE EyeCare Technical Framework 2010 vol 1 & 2.

See: http://ophthalmictools.com/IHETechnicalFramework2010Volume1and2.aspx