- •Foreword
- •Preface
- •Contents
- •1.1 Introduction
- •1.2 Method
- •1.2.1 Databases
- •1.2.2 Dates
- •1.2.3 Keywords
- •1.2.4 Criteria for Inclusion
- •1.2.5 Criteria for Exclusion
- •1.2.6 Selection of Papers
- •1.3 Results
- •1.3.1 Subspecialty
- •1.3.2 Type of Telemedicine
- •1.3.3 Study Design
- •1.3.4 Final Conclusions of Papers
- •1.4 Discussion
- •References
- •2.1 Introduction
- •2.2 The Need for Diabetic Retinopathy Screening Programs
- •2.4 Guidelines for Referring Patients
- •2.7 Program Models for Diabetic Retinopathy Screening
- •2.9 Program Personnel and Operations
- •2.9.1 Primary Care Providers
- •2.9.2 Photographers
- •2.9.3 Clinical Consultants
- •2.9.4 Administrators
- •2.9.5 A Note to CEOs, Operations Directors, and Clinic Managers
- •2.10 Policies and Procedures
- •2.10.1 Sample Protocol 1
- •2.10.1.1 Diabetic Retinopathy Screening Services
- •Policy
- •Background
- •Procedure
- •2.10.2 Sample Protocol 2
- •2.10.2.1 Pupil Dilation Before Diabetic Retinopathy Photography
- •Policy
- •Background
- •Procedure
- •2.10.3 Sample Protocol 3
- •2.10.3.1 Diabetic Retinopathy Photography Review
- •Policy
- •Background
- •Procedure
- •2.11 Technical Requirements
- •2.11.1 Connectivity
- •2.11.2 Resolution
- •2.11.3 Color
- •2.11.4 Stereopsis
- •2.11.5 Compression
- •2.11.6 Enhancement
- •2.11.7 Pupil Dilation
- •2.11.8 Early California Telemedicine Initiatives Diabetic Retinopathy Screening
- •2.11.9 The American Indian Diabetes Teleophthalmology Grant Program
- •2.11.10 Central Valley EyePACS Diabetic Retinopathy Screening Project
- •2.12.1 Diabetic Retinopathy
- •2.12.1.1 ADA Guidelines Terms
- •2.12.1.2 Vitrectomy
- •References
- •3: Stereopsis and Teleophthalmology
- •3.1 Introduction
- •3.2 History of Stereopsis and Stereopsis in Ophthalmology
- •3.3 Technology and Photography
- •3.3.3 Imaging Fields
- •3.3.4 Image Viewing Techniques
- •3.3.5 Image Compression
- •3.4 Stereoscopic Teleophthalmology Systems
- •3.4.1 University of Alberta
- •3.4.4 Joslin Vision Network
- •3.5 Conclusion
- •References
- •4.1 Introduction
- •4.2 Methods
- •4.2.1 Main Outcome Measures
- •4.3 Results
- •4.3.1 Retinal Video Recording Versus Retinal Still Photography
- •4.3.2 Video Compression Analysis
- •4.4 Discussion
- •References
- •5.1 Introduction
- •5.1.1 Automated, Remote Image Analysis of Retinal Diseases
- •5.1.2 Telehealth
- •5.2 Design Requirements
- •5.2.1 Telehealth Network Architecture
- •5.2.2 Work Flow
- •5.2.3 Performance Evaluation of the Network
- •5.3 Automated Image Analysis Overview
- •5.3.1 Quality Assessment Module
- •5.3.2 Vascular Tree Segmentation
- •5.3.3 Quality Evaluation
- •5.4 Anatomic Structure Segmentation
- •5.4.1 Optic Nerve Detection
- •5.4.2 Macula
- •5.4.3 Lesion Segmentation
- •5.4.4 Lesion Population Description
- •5.4.5 Image Query
- •5.5 Summary
- •References
- •6.1 Introduction
- •6.3 Optical Coherence Tomography to Detect Leakage
- •References
- •7.1 Introduction
- •7.2 Patients and Methods
- •7.2.1 Participants
- •7.2.2 Methods
- •7.2.3 Statistics
- •7.3 Results
- •7.3.1 Reliability of Image Evaluation
- •7.3.2 Prevalence of Glaucomatous Optic Nerve Atrophy
- •7.4 Discussion
- •7.5 Perspectives
- •References
- •8.1 Introduction
- •8.1.2 Homology Between Retinal and Systemic Microvasculature
- •8.1.3 Need for More Precise CVD Risk Prediction
- •8.2.1 Retinal Microvascular Signs
- •8.2.2 Retinal Vessel Biometry
- •8.2.3 Newer Retinal Imaging for Morphologic Features of Retinal Vasculature
- •8.3 Associations of Retinal Imaging and CVD Risk
- •8.3.1.1 Risk of Pre-clinical CVD
- •8.3.1.2 Risk of Stroke
- •8.3.1.3 Risk of Coronary Heart Disease
- •8.3.2.1 Risk of Hypertension
- •8.3.2.2 Risk of Stroke
- •8.3.2.3 Risk of Coronary Heart Disease
- •8.3.2.4 Risk of Peripheral Artery Disease
- •8.3.3 Newer Morphologic Features of Retinal Vasculature
- •8.4 Retinal Imaging and Its Potential as a Tool for CVD Risk Prediction
- •References
- •9.1 Alzheimer’s Disease
- •9.2 Treatments
- •9.3 Diagnosis
- •9.6 Conclusions
- •References
- •10.1 Introduction
- •10.1.1 Stroke
- •10.1.2 Heart Disease
- •10.1.3 Arteriovenous Ratio
- •10.2 Purpose
- •10.3 Method
- •10.3.1 Medical Approach
- •10.3.2 Technical Approach
- •10.3.3 Output of Medical Data
- •10.4 Patients
- •10.5 Results
- •10.5.1 Medical History
- •10.5.2 Telemedical Evaluation of Retinal Vessels
- •10.5.2.1 Prevalence of Retinal Microangiopathy
- •10.5.2.2 Arteriovenous Ratio
- •10.5.2.3 PROCAM-Index
- •10.6 Discussion and Perceptive
- •10.6.1 Estimation of “Stroke Risk” Estimated by the Stage of Retinal Microangiopathy
- •References
- •11.1 Introduction
- •11.2 System Requirements
- •11.3 Fundus Camera
- •11.4 Imaging Procedure
- •11.4.1 Reading Center Procedure
- •11.5 Detection of Macular Edema
- •11.6 Implementation
- •11.7 Unreadable Images
- •11.7.1 Impact on Overall Diabetic Retinopathy Assessment Rates
- •11.7.2 Compliance with Recommendations
- •11.7.3 Challenges
- •11.7.4 Summary
- •References
- •12.1 Screening
- •12.2 Background
- •12.3 Historical Perspective in England
- •12.4 Methodology
- •12.4.1 The Aim of the Programme
- •12.5 Systematic DR Screening
- •12.6 Cameras for Use in the English Screening Programme
- •12.7 Software for Use in the English Screening Programme
- •12.9 Implementation in England
- •12.11 Quality Assurance
- •12.12 The Development of External Quality Assurance in the English Screening Programme
- •12.13 Information Technology (IT) Developments for the English Screening Programme
- •12.14 Dataset Development
- •12.15 The Development of External Quality Assurance Test Set for the English Screening Programme
- •12.16 Failsafe
- •12.17 The Epidemic of Diabetes
- •References
- •13.1 Introduction
- •13.2 Burden of Diabetes and Diabetic Retinopathy in India
- •13.3 Diabetic Retinopathy Screening Models
- •13.4 Need for Telescreening
- •13.5 Guidelines for Telescreening
- •13.6 ATA Categories of DR Telescreening Validation
- •13.7 Yield of Diabetic Retinopathy in a Telescreening Model
- •13.8 How Are Images Transferred
- •13.10 How Many Fields Are Enough for Diabetic Retinopathy Screening
- •13.11 Is Mydriasis Needed While Using Nonmydriatic Camera?
- •13.12 Validation Studies on Telescreening
- •13.12.1 Accuracy of Telescreening
- •13.12.2 Patient Satisfaction in Telescreening
- •13.12.3 Cost Effectivity
- •13.12.4 Telescreening for Diabetic Retinopathy: Our Experience
- •13.13 Future of Diabetic Retinopathy Screening
- •References
- •14.1 Introduction
- •14.2 Methods
- •14.3 Discussion
- •14.4 Conclusion
- •References
- •15.1 Introduction
- •15.1.1 Description of the EADRSI
- •15.5 State Support of Screening in the Safety Net
- •15.7 Screening Economics for Providers
- •15.8 Patient Sensitivity to Fees
- •15.9 Conclusion
- •References
- •16.1 Introduction
- •16.2 Setting Up the New Screening Model
- •16.2.1 Phase 1: Training
- •16.2.2 Phase 2: Evaluation of Agreement
- •16.2.3 Phase 3: Implementation of the Screening Model
- •16.3 Technologic Requirements
- •16.3.1 Data Management
- •16.3.2 Data Models
- •16.3.2.1 Data Scheme for Patient-Related Information
- •16.3.2.2 Data Scheme for Images
- •Fundus Camera VISUCAM Pro NM
- •PACS Server
- •ClearCanvas DICOM Visualizer
- •16.4 Results
- •16.4.1 Phase 2: Agreement Evaluation
- •16.4.2 Phase 3: Implementation of the Screening Model
- •16.5 Discussion
- •16.5.1 Evaluation of the Screening Model
- •16.5.2 Prevalence of DR
- •16.5.3 Quality Evaluation
- •16.6 Conclusion
- •References
- •17.1.3 Examination and Treatment
- •17.1.4 Limitations of Current Care
- •17.2 Telemedicine and ROP
- •17.2.2 Accuracy and Reliability of Telemedicine for ROP Diagnosis
- •17.2.3 Operational ROP Telemedicine Systems
- •17.2.4 Potential Barriers
- •17.3 Closing Remarks
- •17.3.1 Future Directions
- •References
- •18.1 Introduction
- •18.2 Neonatal Stress and Pain
- •18.3 ROP Screening Technique
- •18.4 Effect of Different Examination Techniques on Stress
- •18.5 Future of Retinal Imaging in Babies
- •References
- •19.1 Introduction
- •19.2 History of the Program
- •19.3 Telehealth Technologies
- •19.4 Impact of the Program
- •Selected References
- •Preamble
- •Introduction
- •Background
- •The Diabetic Retinopathy Study (DRS)
- •Mission
- •Vision
- •Goals
- •Guiding Principles
- •Ethics
- •Clinical Validation
- •Category 1
- •Category 2
- •Category 3
- •Category 4
- •Communication
- •Medical Care Supervision
- •Patient Care Coordinator
- •Image Acquisition
- •Image Review and Evaluation
- •Information Systems
- •Interoperability
- •Image Acquisition
- •Compression
- •Data Communication and Transmission
- •Computer Display
- •Archiving and Retrieval
- •Security
- •Reliability and Redundancy
- •Documentation
- •Image Analysis
- •Legal Requirements
- •Facility Accreditation
- •Privileging and Credentialing
- •Stark Act and Self-referrals
- •State Medical Practice Acts/Licensure
- •Tort Liability
- •Duty
- •Standards of Care
- •Consent
- •Quality Control
- •Operations
- •Customer Support
- •Originating Site
- •Transmission
- •Distant Site
- •Financial Factors
- •Reimbursement
- •Grants
- •Federal Programs
- •Other Financial Factors
- •Equipment Cost
- •Summary
- •Abbreviations
- •Appendices
- •Appendix A: Interoperability
- •Appendix B: DICOM Metadata
- •Appendix C: Computer-Aided Detection
- •Appendix D: Health Insurance Portability and Accountability Act (HIPAA)
- •Appendix F: Quality Control
- •Appendix H: Customer Support
- •Level 1
- •Level 2
- •Level 3
- •Appendix I: Reimbursement
- •Medicare
- •Medicaid
- •Commercial Insurance Carrier Reimbursement
- •Other Financial Factors
- •Disease Prevention
- •Resource Utilization
- •American Telemedicine Association’s Telehealth Practice Recommendations for Diabetic Retinopathy
- •Conclusion
- •References
- •Contributors
- •Second Edition
- •First Edition
- •Index
5 Automated Image Analysis and the Application of Diagnostic Algorithms in an Ocular Telehealth Network 45
Real cost savings for telehealth may be potential as published telehealth cost analyses include costs associated with development of the network infrastructure. Our approach has utilized commercial Internet connectivity to assess and validate the application of content-based image retrieval (CBIR) technology and its integration without incurring significant infrastructure costs.
Technological advancements have made remote delivery of consultative health care feasible and widespread in recent years. With the ubiquitous connectivity of Internet, and the increasing availability of network bandwidth, exchanging medical information and delivering services over a large geographic region is possible, while providing high throughput for real-time data analysis. To achieve the goal of automating the detection and diagnosis of diabetic eye disease in real time from digital images taken in a primary care setting, the underlying network infrastructure needs to be established. In ocular telehealth networks, the participating primary care clinics are connected to a diagnostic computer server using standard Ethernet connections. The web-based telemedical network adds portability and significant flexibility in healthcare delivery, providing access to expert diagnosis and high-throughput potential to meet the growing need for disease assessment and management in rapidly expanding at-risk and underserved patient populations. In this chapter, we present the results of our work developing and implementing image analysis and management algorithms that can leverage just such a clinical and retinal image database to improve the sensitivity and specificity of retinal diagnosis in a robust, objective, and deterministic manner using content-based image retrieval (CBIR). In the following section, the design and implementation of a telemedical network are described.
5.2Design Requirements
To provide a network infrastructure for automated diagnosis and analysis in a primary care environment, the security, reliability, and integrity of the data exchange is crucial in the design requirements. To ensure security, the data transmission
protocols must be cryptographic and compliant with FIPS (Federal Information Processing Standard) 140-2, and the patient-sensitive information must be encrypted to meet the HIPAA compliance requirements. To guarantee data reliability, the data flow in the network must be robust under any network connectivity conditions, and the data transmission has to be fast to provide high-throughput image analysis and data processing. To assure data integrity, validation for data entry needs to be enforced, and the data storage in the system needs to be continuously monitored.
5.2.1Telehealth Network Architecture
In the network design for ocular telehealth, a client–server model approach is implemented for the data transmission between the client and the diagnostic server. Undilated fundus images of both eyes are captured by a nonmydriatic commercial retina camera and are exported and submitted to the server for an automated quality assessment (QA) metric. The QA metric assures adequacy of the images for the purpose of determining a diagnosis. The QA results are communicated to the end user in real time. Inside the server, the automatic diagnostic service retrieves the images and defined patient metadata and performs image processing tasks to identify anatomical structure location, extract features, and detect lesions. Following the analysis, the algorithm assigns a diagnosis with an appropriate management plan and generates an encrypted report accessible by the referring physician. An ophthalmologist then reviews the images and the diagnostic report and provides validation before the confirmed report is returned to the end user. An ophthalmologist can also override the computer generated diagnosis by manually assigning a different diagnosis through the web interface to generate an alternative or modified report and management plan.
To provide secure data communications between the clinics and the diagnostic server over the Internet, all data transmission protocols in the network are cryptographically designed to meet the standards published in the Federal Information
46 |
T.P. Karnowski et al. |
|
|
Processing Standards (FIPS140-2). To transfer image files to the server and communicate the quality assessment result (pass or fail) to the camera, a Secure File Transfer Protocol (SFTP) is used. To access the report generated on the server, the referring physician can either login on a secure website using HTTPS (HTTP over Secure Socket Layer) or download an encrypted PDF report sent as an e-mail attachment.
To ensure security of patient-sensitive information and to meet HIPAA compliance requirements, data encryption is performed in the reviewing and confirmation process. When the review is complete, the ophthalmologist digitally signs and encrypts the report using an X.509 certificate and then sends the confirmed report with digital signature and encryption to the referring physician in the end user clinic. PDF encryption with an issued certificate guarantees data integrity and security while providing a passwordprotected access of the report for referring physicians via an e-mail attachment.
To fulfill the requirement of robust data transmission under adverse network conditions or unstable network connectivity, the client program on the camera closely monitors the network status and reacts to the connectivity instability in a real-time manner. In the multithread client monitoring program, one of the threads is devoted to scanning the network status constantly and reporting the network status to the user every second. If connectivity issues occur, the client program reacts promptly to attempt self-recovery of network connections, if possible, and prompts interactive information to the user. If self-recovery cannot be achieved within a preset time limit and network problem persists, the client program prompts the user to address the problem. If there is data transmission when network problems occur, the client program retransmits the exported images after the network is reinstated. To guarantee that there is no loss of data in the client–server communication, a persistent acknowledgement is required for committed storage in the bidirectional data transmission.
Reliability and data integrity is critical in designing the ocular telehealth system. Reliability requires the completeness, timeliness, and
accuracy of the data; integrity refers to the validity and consistency of the data. Reliability and data integrity can be compromised in a number of ways, for example, human errors when data is entered, errors that occur during data transmission, viruses, hardware malfunctions, and even natural disasters. To minimize these threats, the following methods are incorporated in the system design: regular backup to another independent physical media in the university server farm and elsewhere; controlling data access to via security mechanisms; designing user interfaces that prevent the input of invalid data; and bookkeeping the critical status of every procedure involving data manipulation and analysis to provide an audit trail of data flow in the system.
5.2.2Work Flow
The work flow of the ocular telehealth network is illustrated in Fig. 5.1. Data storage can be either in file format inside directories or in a database format. The procedural modules include quality check and thresholding, a diagnostic engine running to perform disease stratification for incoming data and to build a CBIR library based on data archival, report generation, and bookkeeping functions such as log and process records.
Three mechanisms for data communication are involved in the network flow. The communication between the remote clinics and the server is through SFTP connections, the report generated is communicated back to the referring physicians in an encrypted e-mail attachment, and the communications between the data storage modules and the procedural modules are through an internal university network. The interface design in the network is composed of three parts: (1) the client application GUI for the remote clinics, (2) the web GUI for the authorized physicians, and (3) the service GUI for monitoring and bookkeeping, which is transparent to the end user. In our web-based network, retinal images from diabetic patients are encrypted and transmitted from the fundus cameras at the primary care clinics to the diagnostic server using DICOM protocols.
5 Automated Image Analysis and the Application of Diagnostic Algorithms in an Ocular Telehealth Network 47
|
QA |
Feature map |
|
|
|
|
|
Imaging & End-user GUI |
Anatomy |
|
|
Patient database |
|
||
|
|
Ophthalmologist |
|
|
|
|
confirmation |
|
|
|
|
|
|
|
|
MD Interface
Archive |
CBIR Library |
End-user EHR
Patient report
Fig. 5.1 HIPAA-compliant telehealth infrastructure and image analysis process. The client application encrypts and exports patient images and metadata to a dedicated diagnostic server. Image processing and analysis procedures are performed in an automated fashion including a quality assessment (QA) to ensure adequacy for anatomical structure analysis, lesion detection, and assignment of an
automated diagnosis according to the posterior probability of each defined disease state using our content-based methods. The server provides an interface for the consulting ophthalmologist to generate a signed diagnostic report which is encrypted and returned to the end-user physician.
The client application GUI provides an interface for the regional primary care clinics for monitoring the data transmission and network status. The clinic acquires fundus images of the retina using VisuCamPro NM (nonmydriatic) camera (Carl Zeiss Meditec). The client application GUI closely monitors the image exportation on the camera. New images are immediately encrypted, exported, and transmitted to the dedicated diagnostic server, along with patient metadata entries from the clinics. At the same time, the client application GUI constantly scans the network status and reacts in a real-time manner to prompt interactive information when connectivity issues do occur.
After the images are submitted to the server, image processing and recognition procedures are triggered on the server to perform automated diagnosis. However, those procedures are transparent to the users. The procedures involved can be briefly described as the following: the submitted images are first subject to a quality assessment (QA) to ensure adequacy for further analysis. Images that pass QA undergo automated processing, including anatomical structure analysis, lesion detection, and automated diagnosis according to the posterior probability of each defined disease state using CBIR methods that evaluate the retrieval response and stratify the disease state, as described below.
