© 2012 IBM Corporation

VNA for indexing & storing DICOM & non-DICOM objects - A point-of-view from a CTO UK Imaging Informatics Group – Birmingham November 6, 2012

Peter B. Lange Executive IT-Architect Office of the CTO, Public Sector, IBM Europe

© 2012 IBM Corporation 2

Hospital Environment Today

Archive

Radiology

•  DICOM archive •  50MB-2GB files •  First generation

obsolete •  “Closed” archives •  Archive dedicated

to each PACS

Archive

Cardiology

•  DICOM or non-DICOM

•  Little or no archiving (DVD)

•  500MB-1GB files •  Dedicated archive

Storage

..ologies

•  Non-DICOM •  Little or no

archiving •  Small files •  Dedicated

storage

Backup

Other Applications

•  Non-DICOM •  Backup and

archiving •  Small to very

large files •  Dedicated

storage

•  Different vendors, isolated archives

•  No sharing of infrastructure

•  No sharing of information base

•  May be located at different sites

Vendor Neutral Archive

• VNA provides centralized medical content repository

•  ‘Any to any’ access (controlled)

• Ensures compliance with data privacy regulations

• Simplifies maintenance and reduces storage cost

Hospital Environment Tomorrow

© 2012 IBM Corporation 3

VNA – Not just a digital dump ground

Open and standards based

Managed and structured

Leverage information

Scalable and secure

© 2012 IBM Corporation 4

What to look for when indexing in VNA. Become and stay vendor neutral. Avoid VNA vendor lock-in, unlock DICOM content and secure future interoperability

Indexing VNA

Objects

Meta Data

Indexing •  Automated •  Manage vendor specific headers •  Customizable •  Configurable •  Rules driven

Objects •  Strip to the native format •  Follow open standards •  JPEG, JFIF, PDF, MPEG etc •  Avoid properitary formats •  True vendor neutral format •  Make available as non-DICOM

Meta Data •  Decompose most of the header •  Make as mush header

information available as possible •  Don’t loose any information

stored in the DICOM header •  Preserve integrity of DICOM obj

DICOM Header

© 2012 IBM Corporation 5

What to look for when storing in VNA. Manage cost of ownership. Manage the cost when the tsunami hits

VNA

Hirachical Storage Mgmt •  Combine fast on-line with slower

and less expensive near-line and off-line (tape) storage

•  Policy driven migration based e.g. on DICOM header information or class of information

Other means •  Compression, even most native

object formats already are compressed

De-dublication •  Automated detection and

removal of dublicates •  Policy driven removal of

intermediate versions

Retention & Disposition •  Rules-based event-driven

retention and disposition •  Not just age of study, but e.g.

events like ”patient turns 18 yrs” •  Meet regulations and at the

same time manage TCO

© 2012 IBM Corporation 6

VNA for non-DICOM objects. Interfaces are kings.

WebDAV •  Older W3C standard originated

in 1996 •  Based on HTTP •  Support is fading

Java Cnt Repository (JCR) •  J2EE standard initiated as

JSR170 in 2003 •  JCR 2.0 in the works from 2010

as JSR283

CMIS •  Content Management

Interoperability Services •  Recent (2010) OASIS standard

backed by major vendors like Microsoft, IBM, ECM, Adobe and others

File System Exchange •  Vendor specific interfaces •  Often based on file pairs of

object and XML descriptor file •  Async and batch oriented •  Can include parsing of e.g.

PDFs

XDS •  VNA shall be XDS repository •  Better more scalable security

model than native VNA •  XDS-SD for scanned documents •  XDS for HL7 CDA docs •  XDR, XDM?

Vendor specific adaptors •  Most VNA vendors provides

interfaces and API toolkits for on-line synchronous application integration

© 2012 IBM Corporation 7

VNA = Vendor Neutral Architecture?

VNA

RIS/PACS •  Support a broad set of RIS/

PACS and other diagnostic imaging systems

•  Easy configuration and customization of interface

Software Platform •  Operating System •  Database •  Application server •  Identity management •  Systems management •  Reporting

Server Platform •  CPU •  32/64 bit •  Multi-core •  Form factor

Storage Platform •  Tiered storage •  Network attached storage

© 2012 IBM Corporation 8

Complexity from the many choices

•  Driving business innovation

•  Make new markets •  Respond to competitive

threats •  Enhance the customer

experience

Getting Up and Running Takes months: • Specify/Design • Procure

•  Integrate • Deploy

Development Operations Takes 30-90 days: • Provision • Configure

• Maintain • Upgrade

IT Reality

Business Goals Grow top and bottom line by:

Ongoing Effort Takes months and requires downtime: • Customize/Tune • Scale • Manage

© 2012 IBM Corporation 9

Delivery models

Appliances

RIS/PACS

EMR

Cloud

Power

© 2012 IBM Corporation 10