Difference between revisions of "Eye Care Displayable Report"
JohnMoehrke (talk | contribs) |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 28: | Line 28: | ||
'''Profile Status:''' [[Comments| Final Text]] | '''Profile Status:''' [[Comments| Final Text]] | ||
| − | '''Documents:''' | + | '''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#eye| Technical Framework 3.7] |
| + | |||
| + | :* [http://www.ihe.net/Technical_Framework/upload/ihe_eyecare_tf_rev3-7_vol1_Final_Text_2010-02-15.pdf Vol. 1] | ||
| + | :* [http://www.ihe.net/Technical_Framework/upload/ihe_eyecare_tf_rev3-7_vol2_Final_Text_2010-02-15.pdf Vol. 2] | ||
| − | |||
| − | |||
'''Underlying Standards:''' | '''Underlying Standards:''' | ||
:* [http://dicom.nema.org DICOM] | :* [http://dicom.nema.org DICOM] | ||
| + | [[Category:Profiles]] | ||
| + | [[Category:Eye Profile]] | ||
| + | |||
| + | [[Category:DICOM]] | ||
==See Also== | ==See Also== | ||
http://one.aao.org/CE/PracticeGuidelines/Information_Technology.aspx | http://one.aao.org/CE/PracticeGuidelines/Information_Technology.aspx | ||
Latest revision as of 14:48, 4 November 2019
Eye Care Displayable Report (ECDR) supports the creation, query/retrieve and reading of ubiquitous display–ready eye care reports
Summary
The Displayable Reports Profile specifies transactions supporting the creation, query/retrieve, and reading of display-ready eye care reports. The ECDR Profile allows use of the DICOM Encapsulated Document IOD, which has emerged as a ubiquitous means of encoding documents ready for presentation, including graphical content. Furthermore, the ECRD Profile allows the reporting physician to control the “look” of the report, which is important for both clinical and business reasons.
Benefits
The main benefit is that the report can be saved as an encapsulated document through the use of the DICOM encapsulated document IOD, and that reporting physician can influence the appearance of the physician report.
Details
The doctor is monitoring the progress of a patient who was diagnosed with glaucoma two years ago. The patient is in the clinic for a 3-month intraocular pressure check. During the physical exam in the clinic it is determined that the intraocular pressure in the right eye is slightly elevated. The doctor orders a Visual Field Test for both eyes. The patient has not had this test performed in the past twelve months and is scheduled for it. The Visual Field department notifies the doctor when the Visual Field test is completed and ready to be interpreted. Automated workflow notification processing is out of the scope of this Report Creation profile. The Visual Field Modality produces an image that contains analytical metrics and a diagram of the patient’s peripheral vision blind spots. The doctor performs a query/retrieve to obtain the new images. In order to determine if the damage is consistent with what existed the last time this diagnostic test was done, the doctor query/retrieves the Visual Field image that was created twelve months ago. The doctor compares the images, usually in a side-by-side display. The doctor’s findings are explained in an interpretation narrative that is saved in the encapsulated document object. The plan for continued treatment is also described in the encapsulated document. The encapsulated interpretation document is stored in the Report Repository. The doctor verifies the encapsulated interpretation DICOM object.
Systems Affected
- A system that generates and transmits clinical reports
- A system that can query/retrieve and view reports encoded as DICOM objects
- A departmental system that receives reports and stores them for long-term access
Actors & Transactions:
Specification
Profile Status: Final Text
Documents: Technical Framework 3.7
Underlying Standards:
See Also
http://one.aao.org/CE/PracticeGuidelines/Information_Technology.aspx