Enterprise imaging image sharing is rarely a single workflow. It is a set of standards-based and vendor-managed paths that move DICOM studies, evidence documents, and presentation states between organizations while preserving patient identity and image context. Once an institution moves beyond physical media, the practical decision is not which product to buy but which sharing mechanism fits a given exchange relationship. An emergency transfer to a partner hospital, an outgoing consult, a patient-mediated copy, and an encounter-based ultrasound workflow each impose different authorization, routing, and metadata requirements. This article explains the named workflows that matter most: IHE XDS-I.b, RESTful DICOMweb access, cloud gateway networks, HIE portal transfer, and encounter-based point-of-care imaging. It then walks through a concrete evaluation example for an institution choosing between two of these approaches.

The Standards-Based Baseline: XDS-I.b and DICOMweb

The IHE Cross-Enterprise Document Sharing for Imaging profile, XDS-I.b, defines actors and transactions for sharing imaging information across enterprises and depends on the IT Infrastructure XDS.b profile [1]. Its exchange units are sets of DICOM instances, which can include images, evidence documents, and presentation states, as well as diagnostic imaging reports supplied in a ready-for-display format [1]. Because XDS-I.b builds on XDS affinity domain concepts such as submission sets, readers are expected to understand the underlying XDS profile before attempting an implementation [1]. The profile addresses a specific problem: finding and retrieving prior studies when a patient has been imaged at another site within a defined community.

For real-time retrieval by an enterprise viewer, IHE defines the Web-based Image Access profile, which uses RESTful services such as WADO-RS and QIDO-RS [1]. A consumer can query study metadata from a PACS or VNA and then retrieve images for display through those same RESTful calls [1]. DICOM PS3.18 describes these DICOMweb services for communicating imaging data, including rendered volume resources and lossless XML-to-JSON conversion for metadata [4]. The standard explicitly places security considerations such as access control, authorization, and auditing outside PS3.18, directing implementers to PS3.15 [4]. Standards therefore define efficient retrieval paths but leave authentication and authorization decisions to the deployment.

Cloud Gateway Networks and the Normalization Problem

When organizations cannot agree on a shared document registry, many turn to cloud image exchange networks. Microsoft's PowerShare documentation describes a secure, cloud-based image exchange network that connects facilities, providers, and patients and integrates with systems such as PACS and Epic [8]. The service uses contacts to define trusted relationships and an accelerator component to automate sending, receiving, and routing, while web access lets users view shared images in a browser [8]. These descriptions are vendor claims about the product's capabilities, not independent performance evidence.

A Cincinnati Children's Hospital case study documented a multi-vendor approach designed to avoid locking exchange into one network. The radiology team installed bidirectional gateways from five different vendors at no cost to the organization, configured each gateway to auto-forward incoming DICOM studies to an internal VNA holding pen for normalization, and then routed studies into their PACS [2]. The authors reported importing roughly 53,000 studies annually, a 177% increase from a baseline of about 30,000 [2]. The reported increase is specific to that single children's hospital and its internal measurement; it does not establish a general efficiency effect for other institutions. The gateway pattern requires staff to manage import queues around the clock but keeps end users inside a familiar system [2].

What to Ask Before Selecting an Image-Sharing Path

Start by documenting each exchange relationship. For scheduled referrals within a known community, XDS-I.b offers registry-based discovery, but it presumes the adopting sites share an affinity domain and understand XDS concepts [1]. For browser-based retrieval from a PACS or VNA, DICOMweb defines RESTful queries and retrieves, but security configuration is outside PS3.18 and must be specified separately [1][4]. If the goal is immediate acceptance of external studies, ask whether front-line staff will manage a normalization queue or whether credentialed staff will download and correct identifiers from a portal [2][7].

Verify the metadata that survives each hand-off. The accession number matters for linking images, reports, and encounter-based captures [6]. Cloud network documentation states that images are available after the send process completes, but it does not specify how prior identifiers are reconciled with a receiving EHR [8]. For point-of-care devices, the EBIW profile remains Trial Implementation, so organizations should track the supplement's status and any public comments before depending on it [6].

HIE Portal Transfer as a Credentialed Workflow

Regional health information exchanges offer a different sharing model, in which studies remain queryable through a portal rather than being pushed into a local archive by default. The CRISP Image Exchange user guide, updated March 2026, states that the service lets organizations share radiology and cardiology studies for viewing in full diagnostic quality through the CRISP Portal or InContext application [7]. Users can measure, zoom, and collaborate on DICOM-quality images, and credentialed sites and users can transfer studies to a PACS [7]. Access requires permission to view clinical information in the portal or InContext, which a local HIE administrator controls [7].

The CRISP workflow illustrates the identity work that portal transfer imposes. When a user downloads external images, the medical record number updates automatically to match the patient's MRN in the receiving system, but a user may edit the MRN or accession number before transfer [7]. A PACS administrator must credential the user for transfer access and contact technical support with the user's email, organization, and EMR username [7]. This manual credentialing step is a documented part of the workflow, not an incidental detail. In a multi-site query, a PACS administrator or film librarian can search for priors across connected facilities and stage them before an outpatient appointment [7]. The portal pattern centralizes governance but shifts preparation work onto credentialed staff.

Encounter-Based Imaging and Point-of-Care Workflows

Traditional image sharing assumes an order and a scheduled procedure. IHE's Encounter-Based Imaging Workflow profile, a Trial Implementation supplement revised in June 2025, addresses a different reality: images acquired during a patient encounter, often with lightweight devices or point-of-care ultrasound [6]. The profile's stated goal is to ensure that such images are combined and associated within the context of the patient encounter [6]. The accession number functions as a significant index for managing an imaging study in the electronic medical record and links images to reports and other documents [6].

The EBIW profile assigns different actor groupings depending on the device. An acquisition modality is grouped with a time client, while a lightweight modality has no specified grouping in the supplement's actor table [6]. The Image Manager/Image Archive is grouped as an XDS-I.b Image Document Source so that encounter-based images become available for cross-enterprise sharing, with the expectation that relevant metadata, including the accession number, makes the sharing transparent [6]. A Result Aggregator uses the BIR Image Display profile to present indexed encounter-based images to clinicians [6]. The supplement is Trial Implementation, meaning the profile remains subject to revision through public comment [6].

Evaluation Example: Portal Transfer Versus Gateway Normalization

A concrete comparison can clarify the decision points. Consider a 400-bed community hospital that receives referrals from four regional imaging centers and occasionally transfers stroke studies to a tertiary site 120 miles away. The hospital could evaluate two documented approaches. Option A is the CRISP-style portal model, in which credentialed staff query the HIE, download selected priors, and manually confirm or adjust MRN and accession identifiers before transfer [7]. Option B is the Cincinnati gateway model, in which vendor gateways auto-forward incoming DICOM studies to a VNA holding pen and staff manage a single import queue [2].

This comparison is a suggested scenario, not a tested benchmark. The portal route places identity correction in the hands of the receiving staff at download time and makes pre-appointment staging a credentialed administrative task [7]. The gateway route automates routing but requires maintaining one or more vendor gateways and a normalization queue; the published Cincinnati figure of 53,000 annual imports reflects their five-vendor setup and workload, not a general result [2]. A hospital with high inbound referral volume and limited HIE coverage may favor gateways, while an organization already participating in a regional HIE may favor the portal. No source in this public documentation compares the two patterns empirically, so a general winner cannot be established.