Cross-enterprise exchange needs registry and repository patterns
A VNA that only speaks local query and retrieve patterns is useful, but it is not enough for enterprise or regional exchange. IHE profiles add the actor and transaction definitions that let repositories, registries, and identity services cooperate across organizational boundaries.
Registry-repository view of cross-enterprise imaging exchange
Loading diagram...
In many deployments the VNA is not every actor at once. It may serve as the imaging repository or source while other services own registry, community, or identity responsibilities. That division matters when teams assess what "VNA support for interoperability" actually includes.
XDS.b integration profile
IHE overview of document-sharing roles, affinity domains, registries, and repositories.
Read the XDS.b profileIHE Radiology Technical Framework Volume 1
Official IHE Radiology technical framework volume that contains the XDS-I.b imaging-sharing profile and related actors.
Read the IHE Radiology frameworkA real VNA stack usually combines archive, identity, and web-access profiles
Teams often ask whether a VNA "supports IHE" as if that were one switch. In practice, archives support a profile stack: DICOM or DICOMweb for image access, XDS.b or XDS-I.b for exchange, and identity services such as PIXm or PDQm when patient domains are not uniform.
Common interoperability contracts around a VNA
| Profile or standard | What it solves | Typical VNA role |
|---|---|---|
| DICOM and DICOMweb | Store, query, and retrieve imaging objects | Archive, gateway, or repository endpoint |
| XDS.b | Register and discover content across an affinity domain | Repository or source alongside a registry |
| XDS-I.b | Share imaging studies and references across enterprises | Imaging source or repository |
| PIXm and PDQm | Cross-reference patient identifiers and demographics | Consumer of enterprise identity services |
PIXm implementation guide
Current IHE guide for mobile patient identifier cross-reference when archives need cross-domain patient ID resolution.
Read the PIXm implementation guidePDQm implementation guide
Current IHE guide for patient demographics query in mobile or API-driven ecosystems.
Read the PDQm implementation guideDICOM Part 18: Web services
Official DICOMweb specification for HTTP-based search, retrieve, and store patterns that often front modern archive services.
Read DICOMweb Part 18Web viewer profiles matter when the VNA feeds browser-based imaging surfaces
Modern imaging programs increasingly expect browser-based viewers, patient portals, and web-mediated referral access. That pushes the archive beyond DIMSE-era assumptions and toward web-oriented viewing contracts that still preserve DICOM identity, presentation, and retrieval semantics.
IHE WIA is useful here because it frames web-based image access as a profile rather than a generic screenshot pipeline. In practice, teams often pair a browser-facing viewer flow with registry or document-sharing workflows for study discovery, while the VNA remains the authoritative imaging repository.
WIA-style interactive viewing flow around a VNA
Loading diagram...
Profile boundary
Web viewing does not make archive governance simpler. The VNA still has to preserve study identity, report linkage, and auditability while the web-facing layer handles browser delivery.
IHE Radiology Technical Framework Volume 1
Official IHE Radiology technical framework volume that includes Web-based Image Access for browser-oriented imaging workflows.
Read the WIA technical frameworkDICOM Part 18: Web services
Official DICOMweb specification for the HTTP retrieval patterns that often sit behind browser-oriented imaging access.
Read the DICOMweb specificationDICOMweb direct access and XDS-style exchange solve different layers
A mature VNA often exposes DICOMweb for direct application access while also participating in XDS-style exchange for discovery across organizations. Those are complementary roles, not interchangeable ones.
Direct DICOMweb access example
Representative DICOMweb calls showing direct archive search and retrieval. XDS-style exchange would add a registry and repository workflow around this, not replace the need to understand the DICOMweb path.
Request
GETANNOTATIONS
Response
Architecture distinction
DICOMweb is the direct-access contract many viewers and services use. XDS.b and XDS-I.b add the cross-enterprise discovery and registry-repository workflow above that access path.
DICOM Part 18: Web services
Official DICOMweb specification for direct HTTP-based imaging access.
Read the DICOMweb specificationIHE Radiology Technical Framework Volume 1
Official IHE Radiology technical framework for XDS-I.b when the archive participates in cross-enterprise imaging exchange.
Read the XDS-I.b frameworkKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.