Ophthalmology Implementation Guide
0.2.0 - CI Build

Ophthalmology Implementation Guide - Local Development build (v0.2.0). See the Directory of published versions

## Patient Journey Use Case

### Cataract Use Case

#### Problem Statement

Cataract Surgery is one of the most commonly performed surgical procedures in the world. There is no universal benchmarking standard for evaluating the methods and outcomes of cataract surgery. Surgeons use different data sets, equipment, and information systems store their data in proprietary data silos. There is no universally agreed technique for sharing cataract surgery data or permitting outcome research beyond the ‘silo’ of each local information system. This is an impediment to audit, research, and shared care with other health professionals especially Optometry.

#### Use Case

A surgeon performs a cataract procedure on an individual eye of a patient and records data before the procedure, at the time of the procedure, and after the procedure in an Ophthalmology management application. Many stakeholders including the surgeon, the patient community, payers, accreditation agencies, researchers would like to track outcomes from this and other similar procedures and benchmark them against the work of other surgeons working both locally and globally. This would bring benefits including: shared care with other health professionals such as Optometrists and outcome research and identification of needy populations, evaluation of differences in surgical technique, equipment and consumables

There are many benefits for each party in such a system, should it be supported by interoperable eye care-specific resources and standards of healthcare information exchange. Some of these include:

##### Ophthal:

- Receives follow up data to learn about Mr. ABC’s surgical outcome
- Self-auditing becomes easier to assess outcome performance from aggregated data across the full journey of their patients
- Peer benchmarking
- Minimize cognitive and practical energy applied to record keeping, sending, retrieving and chasing-up

##### Optom:

- Increasing capacity to educate (Communication) patients in the preop and postop period & provide better service
- Easier relationship building with partnering Ophthals
- Standardized and automated auditing and aggregation (as above) to improve and/or change patient care paradigms
- Minimize data harmonization efforts (as above)

##### Mr. ABC:

- Receives relevant personal health data
- Can integrate this into many emerging personal health record applications (eg - glasses prescription)
- Minimize concerns and considerations about data harmonization efforts in a collaborative care model (as above)

### Glaucoma care

#### Problem Statement

Mrs. XYZ (patient) is a 75-year-old Hispanic female with stable and controlled moderate primary open angle glaucoma (Condition) that requires regular monitoring. Mrs. XYZ’s glaucoma is cared for collaboratively by an Optom and Ophthal. The majority of encounters take place at the Optom, whilst she is stable, during which she undergoes a series of examinations (eg: visual acuity, intraocular pressure measurement (Observation)) and diagnostic tests (eg - visual fields, fundus photography, ocular coherence tomography) and a risk assessment is performed (RiskAssessment). As it is a chronic disease, optimal glaucoma management relies on capturing longitudinal and multimodal data points (examination, testing, imaging (Observation, ImageStudy, DiagnosticReport). Frequency of visits may vary (eg - from every 3-12 months, depending on a number of factors). Whenever certain parameter thresholds are reached that suggest worsening of disease (Condition), the patient will generally be referred (ServiceRequest, Referral Note) to the Ophthal for evaluation and decisions about any new or changed management (eg - change in (Medication) or recommendation for surgical intervention (Procedure)). Therefore, it is essential that all of these monitoring records are routinely transferred to the ophthalmologist. The reasons for this are twofold; first, the Ophthal may be involved in reviewing some of the information collected during the Optom encounter, and second, if and when the time comes for referral, they will have the relevant information available.

There are many benefits for each party in such a system, should it be supported by interoperable eye care-specific resources and standards of healthcare information exchange. Some of these include:

##### Ophthal:

- Can be involved in remote monitoring of Mrs. XYZ’s care
- Self-auditing becomes easier to assess outcome performance from aggregated data across the full journey of their patients
- Peer benchmarking
- Minimize cognitive and practical energy applied to record keeping, sending, retrieving and chasing-up

##### Optom:

- Increasing confidence to monitor Mrs. XYZ knowing that the Ophthal has access to her results and information
- Increased capacity to educate (Communication) patients about decisions and following Ophthal referral to provide a better service
- Easier relationship building with partnering Ophthals
- Standardized and automated auditing and aggregation (as above) to improve and/or change patient care paradigms
- Minimize data harmonization efforts (as above)

##### Mr. ABC:

- Receives relevant personal health data
- Can integrate this into many emerging personal health record applications (eg - glaucoma medication adherence) and can leverage emerging devices (eg home Icare ® - home IOP monitoring device) to enrich the data available to practitioners between visits
- Minimize concerns and considerations about data harmonization efforts in a collaborative care model (as above)
- Actors in scenario #2: patient (Mrs. XYZ), 2x practitioners (Optom, Ophthal), multiple devices, potentially multiple locations, and potentially 2x healthcare services.