An orders-based imaging workflow is a specific operational design in which an EHR order initiates image acquisition, applies patient metadata through a DICOM modality worklist, and routes the resulting study to an enterprise archive for viewing and documentation. The most detailed public implementation report comes from a pediatric ophthalmology division that integrated thirteen devices across six modalities and five locations, then measured workflow efficiency and billing output [1]. That report provides a concrete reference point, but it does not establish that the same results will occur in every eye care setting. The broader literature shows that ophthalmic imaging remains fragmented by proprietary formats and inconsistent DICOM conformance, which means integration decisions must be evaluated against local device capabilities, archive architecture, and the specific clinical workflows that generate orders [3][4]. This article explains the named workflow, the technical decision points that determine whether it works, the evidence limitations, and a concrete evaluation example.

What an Orders-Based Workflow Actually Changes

The pre-implementation workflow described in the pediatric ophthalmology report was manual and paper-dependent. Technologists entered demographic and clinical data on each device for every patient, printed images and results for later physician review, and then scanned the paper copies into the EHR after a clinical note was created [1]. The replacement workflow used EHR orders, DICOM modality worklists, and enterprise archive storage so that order placement, metadata application, and documentation could be automated where possible [1]. The stated guiding principle was to create a standard process for performing, documenting, storing, and billing imaging studies across multiple modalities and procedures [1].

The measured outcomes were substantial in that setting. Post-implementation, 16,267 imaging studies were completed between November 15, 2022, and December 31, 2024, generating $11.4 million in billed charges [1]. Keystrokes and mouse clicks were reduced by 40 to 86 percent depending on modality, and time savings were observed in most modalities [1]. Optical coherence tomography and B-scan ultrasound required more time because of order-specific imaging steps [1]. These figures are specific to one quaternary care children's hospital and should not be read as universal benchmarks for other practices.

Technical Decision Points: DICOM, HL7, and Archive Requirements

The implementation team set explicit device requirements before building the workflow. Ocular imaging devices had to meet hospital security requirements, create DICOM standard images, use a DICOM modality worklist, send DICOM images to the enterprise imaging archive, and be viewable in the enterprise viewer [1]. The team also worked with the ophthalmology division's business director to compile procedures and billing codes performed on each device and gathered standard or structured diagnostic and procedural notes [1]. These requirements illustrate that an orders-based workflow is not simply an EHR configuration change; it depends on device-level DICOM capabilities and a defined archive destination.

The HIMSS-SIIM Enterprise Imaging Community whitepaper describes the typical fragmentation that these requirements are meant to address. In routine eye care, providers may interact with several workstations, clinical applications, and interfaces during a single visit, and the ordering computer is often not integrated with the workstation used to manage and document care [3]. Imaging modalities, image management systems, and electronic medical records lack interoperability, forcing manual transcription of image data, annotations, or structured reports into the EMR with an inherent error rate [3]. The whitepaper points to vendor-neutral archives and standardized messaging, including HL7 and SMART on FHIR, as components of a path toward non-proprietary image storage and sharing [3].

A Concrete Evaluation Example for a Two-Location Retina Practice

Consider a suggested evaluation for a retina practice with two locations, one OCT device from a major vendor, one fundus camera, and an existing EHR that supports HL7 orders but has no current DICOM archive. The first step would be to request DICOM conformance statements from both device manufacturers and check whether each device can query a modality worklist and send images via C-STORE to a vendor-neutral archive [4][6]. The second step would be to run a controlled test with a standard patient, counting clicks, keystrokes, and time from order entry through image acquisition, as the pediatric ophthalmology team did [1]. The third step would be to inspect the resulting DICOM metadata for patient identifiers and demographic accuracy, since abnormal names and birthdates were a documented cause of linkage failure in the IRIS Registry study [2][7].

This suggested evaluation would not produce a universal recommendation. A practice with strong demographic hygiene and devices that support full DICOM worklist queries may see efficiency gains similar in direction to the pediatric report, while a practice with older proprietary devices may need interface work before any orders-based workflow is viable. The evidence does not establish a minimum device count, modality mix, or archive vendor that predicts success. The only defensible conclusion is that the evaluation must be local and measured.

Where Cross-Vendor Linkage Succeeds and Where It Fails

A retrospective study using de-identified IRIS Registry data tested whether DICOM metadata from Heidelberg Engineering and Optos devices could be linked to patient records through a proprietary heuristic patient-matching algorithm under HITRUST guidelines [2]. The study acquired 2,287,839 DICOM files from 54,896 unique patients and successfully linked 1,937,864 images from 46,196 unique patients to registry records [2]. After removing records with abnormal patient names and invalid birthdates, the linkage success rate was 93.3 percent for images and 88.2 percent for patients [2]. The authors note that accurate linkage across modalities in adherence with the DICOM standard could support research and AI algorithm development [2].

The failure analysis is as instructive as the success rate. Records with names containing numbers and abnormal dates of birth were excluded to improve matching, which means the reported rates apply to a cleaned subset rather than the full source population [2]. The study also relied on a proprietary matching algorithm, so the results do not demonstrate that any two organizations can reproduce the same linkage using standard tools alone [2]. For operational integration, this suggests that patient demographic quality and metadata consistency are active variables, not fixed assumptions.

Standards Adoption and the Limits of DICOM Compliance Claims

The American Academy of Ophthalmology states that DICOM is the gold standard for interoperable ophthalmic imaging and supports broader conformance to improve care coordination, patient access, and innovation [4]. The Academy has developed DICOM-based imaging standards for common ophthalmic modalities and updates its standards documentation regularly, most recently in December 2025 [4]. In 2022, the Academy and ARVO jointly published a policy statement calling partial compliance insufficient and arguing for full implementation of DICOM standards [4].

A key limitation is that FDA market authorization does not require DICOM compliance for ophthalmic imaging devices, and conformance claims are not independently certified [4]. The Academy's 2021 standardization recommendations state that even so-called DICOM-compliant devices can fail to meet standards in significant ways, such as embedding patient identifiers on the image [7]. The Academy specifically encourages manufacturers and PACS vendors to provide machine-readable discrete data for user-selected reports and to use lossless compression for pixel or voxel data [7]. These gaps mean that a vendor's DICOM conformance statement is a starting point for evaluation, not proof of complete interoperability.

Vendor Documentation and IHE Profiles as Evaluation Inputs

Vendor materials describe integration capabilities in different terms. Heidelberg Engineering's HEYEX 2 platform is described as supporting device integration, EMR and HIS connectivity, modality worklists, automated reports, vendor-neutral archiving, and role-based access with end-to-end encryption [5]. The company states that the platform is designed to help with HIPAA, GDPR, and local data protection compliance, but these are vendor claims about design intent rather than independently verified outcomes [5]. EyeMD EMR publishes an IHE Integration Statement listing supported actors and options, including DICOM C-FIND patient root, study root, and modality worklist queries, C-STORE image storage, and display of DICOM ophthalmic images and encapsulated PDFs [6].

The EyeMD statement itself warns that an IHE Integration Statement is not sufficient to ensure successful integration [6]. It states that users must analyze integration issues and validate data accuracy and stability before clinical use [6]. The statement also notes that IHE profiles evolve and that EyeMD reserves the right to change product features, which means installed integrations may require future updates [6]. These vendor documents are useful for comparing declared capabilities, but they do not substitute for testing against the specific devices and archive already in place at a given practice.