Cross-enterprise Document Sharing for Imaging

From IHE Wiki
Revision as of 18:08, 11 November 2008 by Kevino (talk | contribs)
Jump to navigation Jump to search

Cross-enterprise Document Sharing for Imaging (XDS-I) extends XDS to share images, diagnostic reports and related information across a group of care sites.

Summary

The Cross-Enterprise Document Sharing for Imaging Profile provides a solution for sharing (publishing, finding and retrieving) imaging documents across a group of affiliated enterprises.

Affiliated Enterprises such as radiology departments, private physicians, clinics, long term care, and acute care contribute and access (query and retrieve) imaging documents (images and reports) of interest.

Imaging documents include:

  • Imaging studies (images, evidence documents (e.g. post-processing measurements/analysis outcome), and presentation states);
  • Diagnostic reports resulting from the interpretation of one or more related imaging studies provided in a ready-for-display form;
  • A selection of diagnostically significant images associated with the report content.

Xdsi profile.jpg

Benefits

Details

An Imaging Document Source that wants to share a set of images and/ or imaging information objects such as a presentation state constructs a DICOM manifest that references the DICOM instances that are to be published. The manifest along with metadata is submitted to the Document Repository. The metadata describes the information that is shared. Besides information about the patient and information required by the XDS profile, the Imaging Document Source provides metadata information that is image specific such as the type of imaging procedure, the modality and the anatomic region. Images and/ or imaging information objects that are made available are not transferred to the Document Repository. Instead, the Imaging Document Source is required to make them available to be retrieved.

An Imaging Document Consumer that is interested in retrieving previously published imaging information, queries the registry ( i.e. find all CT of the Head of patient John Doe for the last 2 years) and retrieves the manifest of interest. The Imaging Document Consumer decodes the manifest to extract the identifiers that uniquely identifies the available imaging information. The Imaging Document Consumer retrieves the images and/ or imaging information objects from the Imaging Document Source.

An Imaging Document Source that wants to share an imaging report constructs a document that is shared either in a PDF and /or CDA (containing only text) format. The report is submitted to the Document Repository.

A Document Consumer (any Document Consumer and not only Imaging Document Consumer) that is interested in retrieving previously published imaging report, queries the registry and retrieves the report from the Document Repository.

Systems Affected

PACS and Workstations might implement an Imaging Document Source to provide and submit images and/ or imaging reports.

RIS might implement an Imaging Document Source to provide and submit imaging reports.

PACS, Workstation, RIS and non-radiology workstations might implement an Imaging Document Consumer to retrieve and display images and imaging reports.

Actors & Transactions:

Xds-i actors.jpg

Specification

Profile Status: Final Text

Documents:

IHE Radiology Technical Framework:

  • Vol. 1 - Section 18 documents the profile
  • Vol. 3 - Sections 4.54 and 4.55 document specific transactions
  • Vol. 3 - Appendix Y provides additional informative text

Underlying Standards:

  • DICOM
  • <need to reference ebxml ???>

See Also

Related Profiles


Consumer Information

The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>

The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>

Implementer Information

The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>

Reference Articles

<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis) >

This page is based on the Profile Template