Integrating the Healthcare Enterprise

1
Integrating the Healthcare Enterprise

• Portable Data for Imaging - PDI

Robert Horn Agfa Healthcare
2
Portable Data for Imaging - PDI


Scheduled Workflow

-
Patient Info. Recon-ciliation
Post-Processing Workflow
Basic Security


3
PDI Value Proposition

• Removable media that contains DICOM and may
  contain browser viewable data.
• For patient personal records
• For referral
• For enterprise data interchange
• For use in other departments, e.g. surgery
• For printing
• Media interoperability validation
• Browser compatibility
• Get CDs that you can create and read anywhere

4
PDI Value Proposition

• Interoperability validation is especially
  important for media
• Network Interoperability Problems
• Immediate, Unambiguous
• Rapidly resolved
• Media Interoperability Problems
• Long delays in detection and recognition
• Ambiguous or unknown source vendor/version
• Long delays in resolution
• Large volume of non-interoperable media created
  due to delays
• IHE Virtual Connectathon for PDI solves the media
  validation problem
• Provides rapid, unambiguous detection of problems
• Enabling rapid resolution of problems

5
PDI Actors and Transactions
Distribute Imaging Information on Media
Display
Image Display
Portable Media Creator
Report Reader
Print Composer
Media Importer
6
PDI Media Creator

• Create DICOM Compliant CDROM media
• Create web content (optional)

7
CDROM Structure
DICOMDIR
Directory of DICOM files
INDEX.HTM
README.TXT
Web content (optional)
IHE_PDI Directory of web files
Other optional content
8
CDROM Rules

• DICOM Part 10 compliance will be verified. This
  is done by both MESA tools and the project
  managers.
• IHE_PDI web content corresponds exclusively to
  the DICOM content, although it need not represent
  the entire DICOM content.
• Other content will not be placed in DICOM or
  IHE_PDI directories, but may be placed in other
  locations on the CDROM.
• Do not assume that an application on the media
  will automatically be launched. IHE recommends
  that media readers not automatically run software
  on the media.
• Web content use of XHTML and JPEG formats is
  restricted to ensure interoperability.

9
All PDI reading actors

• Shall indicate to the user when they find DICOM
  instances that are not supported by the reader.
• It is recommended that readers not automatically
  run software found on the media (for security
  reasons).

10
PDI Importer (Reader) Rules

• Portable Media Importer is required to have
  facilities to accommodate updating patient
  information to use values for the receiving
  enterprise, e.g. update patient ID.
• Portable Media Importer shall be grouped with at
  least one of the following actors
• Evidence Creator
• Acquisition Modality
• Image Manager/Image Archive
• Report Creator
• Report Manager
• Report Repository

11
CDROM Creator Rules

• All DICOM file names are limited to 8 characters
  (no extensions). This is the Part 10
  requirement.
• All other file names are restricted to the ISO
  9660 8.3 file name. E.g. support_for_my_app.dll
  would need to be SUPPORT.DLL or some other 8.3
  name.

12
More information.

• IHE Web sites
• http//www.himss.org/IHE
• http//www.rsna.org/IHE
• http//www.acc.org/quality/ihe.htm.
• Technical Frameworks
• ITI V1.0, RAD V5.5, LAB V1.0
• Technical Framework Supplements - Trial
  Implementation
• May 2004 Radiology
• August 2004 Cardiology, IT Infrastructure
• Non-Technical Brochures
• Calls for Participation
• IHE Fact Sheet and FAQ
• IHE Integration Profiles Guidelines for Buyers
• IHE Connect-a-thon Results
• Vendor Products Integration Statements