Eye care is one of the most device-heavy specialties in outpatient medicine. A single clinic visit can involve an autorefractor, a lensmeter, a tonometer, an OCT scan and a visual field test before the ophthalmologist even enters the room, and every one of those results has to land in the chart. In Epic organizations, that chart is usually Kaleidoscope.
This guide explains Kaleidoscope as Epic and its customers describe it publicly: what it adds to the core ambulatory record, how ophthalmologists and technicians use it, and how ophthalmic devices and imaging systems connect to it. It is written for eye care leaders, Epic analysts and device and imaging vendors.
What is Epic Kaleidoscope?
Connecting eye care devices to Epic?
Agnotic builds Epic integrations for specialty workflows, including device and imaging connections for eye clinics.
Epic Kaleidoscope is Epic's ophthalmology specialty module. Epic says it gives ophthalmologists and optometrists features and clinical content for subspecialty, diagnostic testing and eye imaging workflows, on top of the eye care tools already available in EpicCare Ambulatory. Epic recommends Kaleidoscope for most eye clinics where ophthalmologists work as providers.
For clinics staffed only by optometrists, Epic offers a separate Optometry module. The choice between the two depends on whether the clinic performs ophthalmic procedures and subspecialty care. Organizations with both kinds of clinics can run each on the module that fits, while keeping one patient record.
What does Kaleidoscope add to the standard Epic record?
Kaleidoscope adds a structured ophthalmology exam, eye-specific drawing and documentation tools, technician work lists and a view for managing imaging and procedures. UI Health Care's Epic education pages describe it as adding support for procedure-based workflows and subspecialty exam documentation.
- Ophthalmology exam: Structured documentation of findings for each eye, which can be pulled into notes and letters with SmartLinks and SmartPhrases.
- Drawing tools: Lines, shapes and stencils for documenting findings directly on eye diagrams.
- Auto-correct dictionary: Converts common ophthalmology abbreviations to their full terms.
- Imaging and Procedures Home: A cross-patient view where providers can result multiple tests for different patients.
- Eyeglass prescriptions: Signed from the eye exam or wrap up activity and printed for the patient.
Because Kaleidoscope sits on the same record as the rest of Epic, a retina specialist can see a patient's diabetes control and medication list, and the endocrinologist can see the eye exam results, without any interface between them.
How do ophthalmologists and technicians use Kaleidoscope?
Technicians and ophthalmologists split the visit, and Kaleidoscope reflects that split. Technicians room the patient, take history and run tests from work lists, and the ophthalmologist reviews the results, completes the exam and decides on care.
- Rooming and status: Rooming and dashboard statuses track where each patient is in the clinic.
- Technician work lists: Eye technicians access work lists for the tests assigned to them, begin and end exams, enter results and assign to another provider.
- Diagnostic technicians: UI Health Care trains diagnostic technicians who only perform tests on the eye tech work lists alone.
- Scribes: Ophthalmology scribes have their own training track for documenting during the provider's exam.
- Order corrections: If the exam performed differs from the one ordered, staff change the order so charging and documentation match.
Clinic flow is a constant concern in eye care, where patients may move between waiting areas for dilation and testing. Dashboard statuses that show where each patient is and what they are waiting for are as important to the clinic as the exam itself.
How do ophthalmic devices and imaging connect to Kaleidoscope?
Ophthalmic devices and imaging connect through two paths: measurement data that should land as discrete values in the exam, and images and reports that belong in an image archive or viewer. The IHE Eye Care domain, sponsored by the American Academy of Ophthalmology, defines profiles for both.
- Unified Eye Care Workflow: IHE's current workflow profile for keeping patient and procedure data consistent across an eye clinic, with models for EHRs and PACS and a workflow for refractive devices.
- Eye Care Displayable Report: Uses DICOM Encapsulated PDF for reports such as visual fields and OCT reports, archived and retrieved for display.
- Eye Care Evidence Documents: Covers observations and measurements output by acquisition devices and workstations.
- Eye Care Charge Posting: Transfers charge information to the clinic or enterprise charging system.
In practice, an eye clinic usually has an ophthalmic imaging system or PACS that receives images from OCT, fundus cameras and perimeters. Kaleidoscope holds the orders, the interpretation and the link to the images, so the work is in keeping patient, order and study identifiers matched across systems.
Older devices are the hard part. Many clinics still run instruments that export only to a local workstation or a shared folder, with no DICOM or HL7 support. Those devices need a bridge, such as a capture workstation that wraps output as DICOM, or a decision to replace the device during the project. Budget for this early, because it is often the longest item on the plan.
What about refraction and other measurement devices?
Refraction and similar devices produce numbers that the technician would otherwise type into the exam: refraction values, lensmeter readings, keratometry and intraocular pressure. Bringing those numbers in directly saves time and removes a common source of transcription errors.
IHE notes that its Unified Eye Care Workflow added a data classification for automated refraction devices, based on the Japan Ophthalmic Instruments Association specification, to bring refractive measurements into EHRs through an XML data stream. Device support varies, so confirm each device model's output format before planning the integration.
- Map each value: Sphere, cylinder, axis, add and prism for each eye must land in the right exam field.
- Mark the source: Keep a record that a value came from a device, and which device.
- Review before signing: Technicians and providers confirm device values, especially when a reading looks unusual.
How does Kaleidoscope support registries and reporting?
Kaleidoscope's structured exam makes it possible to report eye care data without manual abstraction. IHE's General Eye Evaluation content profile, built on HL7 C-CDA, defines an eye examination document and notes that it can be used to populate the American Academy of Ophthalmology's IRIS Registry.
Reporting only works when documentation is structured. Visual acuity, intraocular pressure and diagnoses captured as discrete fields can be counted and submitted; the same values buried in free text cannot. Clinics should decide early which measures they report and make sure the exam template captures them discretely.
IHE also defines an Eye Care Summary content profile, a superset of the C-CDA continuity of care document, for sharing an eye care summary record. That matters when patients move between a hospital eye department and an independent practice, since a structured summary carries far more than a scanned letter.
What should eye clinics plan for in a Kaleidoscope project?
Plan for device inventory, imaging strategy, exam templates and clinic flow. The software is only as good as the connections and templates around it, and eye clinics have more devices per room than most specialties.
- Device inventory: List every device, model and software version, with how it outputs data today.
- Imaging strategy: Decide whether images live in an ophthalmic image system, an enterprise PACS or both, and how providers open them from Epic.
- Templates: Agree exam templates per subspecialty, such as retina, glaucoma and cornea.
- Orders and charges: Align test orders with what is performed, so charges are complete.
- Training by role: Providers, technicians, diagnostic technicians and scribes each need their own training.
Pilot with one subspecialty clinic first. Glaucoma clinics, for example, rely heavily on visual fields and OCT, which makes them a good test of both the device path and the imaging path.
How should eye clinic integrations be tested before go-live?
Test eye clinic integrations by running real clinic days in the test environment, with technicians operating the actual devices against test patients. Interface checks alone miss the problems that matter most to a busy clinic, such as a result that lands under the wrong eye.
- Laterality: Confirm that every device value and image is labelled right eye or left eye correctly in Epic.
- Order matching: Check that each test result attaches to the order that requested it, including add-on tests.
- Image launch: Open each image type from Kaleidoscope and confirm the viewer shows the right patient and study.
- Reports: Confirm visual field and OCT reports display and print as expected.
- Charges: Verify that completed tests create the expected charges once, and only once.
- Downtime: Practice how tests performed during an outage are reconciled afterwards.
Ask providers to sign off on a sample of complete encounters, from check in to signed note. Their review catches template and display issues that technical testers do not notice, such as a finding that prints in the wrong place on a referral letter.
How does Kaleidoscope compare with a standalone eye care EHR?
Kaleidoscope's main advantage is the shared record with the rest of an Epic organization, while standalone eye care EHRs are built only for eye clinics and often suit independent practices. Hospital-based ophthalmology departments usually choose Kaleidoscope because their patients also see other specialists in the same system.
Standalone eye care systems may offer deep optical shop, contact lens and practice management features that a hospital department does not need. Independent practices weigh those features against the benefit of sharing a record with local hospitals. Neither choice removes the device integration work, which depends on the devices more than on the EHR.
How Agnotic can help
Agnotic Technologies builds Epic integrations for specialty clinics. For eye care, we work on connections between ophthalmic devices, image management systems and Epic, including identifier matching, order and result interfaces and the mapping of device measurements to exam fields.
For ophthalmic device and imaging vendors, we help design the interfaces Epic customers ask for and prepare the documentation and test cases that speed up hospital approvals. For eye care departments, we also help structure exam data so registry and quality reporting can run from discrete fields instead of chart review.
Plan your eye care integration
See how we connect specialty systems to Epic, or explore more EHR integration articles.
Related reading on Agnotic
Read about optometry systems, imaging informatics, Epic's oncology module and the full set of Epic modules.
