image integration and inter- operability beyond the enterprise rsna’s image sharing network pilot...
Post on 11-Jan-2016
216 Views
Preview:
TRANSCRIPT
Image Integration and Inter- Image Integration and Inter- operability BEYOND the Enterpriseoperability BEYOND the Enterprise
RSNA’s Image Sharing Network Pilot Project
Chris CarrDirector of Informatics
RSNA
Project OverviewProject Overview
• In Sept. 2009, RSNA was awarded two-year $4.7 million contract by the National Institute of Biomedical Imaging and Bioengineering (NIBIB) – Funding provided under provisions of ARRA
• Designed as pilot project to create “Internet-Based Network for Patient-Controlled Medical Image Sharing”
• Network based on IHE XDS-I.b profile for sharing images and reports
• Provide for patient control by enabling access via personal health record (PHR) accounts
Imaging and Information SharingImaging and Information Sharing
• Medical imaging the most commonly ordered diagnostic procedure and fasting growing physician service in US health system– Medicare data show annual utilization increases of about 9%, three times
the rate of other physician services
• Value of medical imaging in providing accurate, noninvasive diagnosis is unquestioned
• Costs of “overutilization” and excessive radiation exposure are growing concerns
• Inaccessibility of prior studies is responsible for a significant number of duplicate studies
• Medical images consistently standardized (DICOM) and the part of the health record most frequently provided to patients in digital form
• Today most often provided on portable media (CD, DVD)• Serious limitations to exchange via physical media:
inconvenience and failures for producers and consumers of images
• The growth of advanced imaging techniques (eg, MRI, CT, PET, Nuclear Cardio) has led to an enormous growth in the amount of imaging data acquired—by volume the largest source of electronic health data
Imaging and Information SharingImaging and Information Sharing
ARRA - HITECHARRA - HITECH
• Project funded under ARRA to further general goals of HITECH
• “Broad use of HIT has the potential to improve health care quality, prevent medical errors, increase the efficiency of care provision and reduce unnecessary health care costs, increase administrative efficiencies, decrease paperwork, expand access to affordable care, and improve population health.”- http://healthit.hhs.gov/portal/server.pt
Project GoalsProject Goals
• Demonstrate a method for sharing images and reports that improves upon portable media
• Enable patients to create a medical record with access at their control • Create standards-based links to personal health record systems to
enable sharing of images and reports• Establish the practice and expectation of accessibility of health records
by participating patients• Enroll a growing number of patients throughout course of project—up
to 300,000• Provide data on the impact of image sharing on care—surveys and
performance metrics• Deliver open source reference implementation of systems developed
for project
Participating SitesParticipating Sites
• Year 1: Five major medical centers• Mount Sinai, NYC• Mayo Clinic, Rochester, MN• University of California, San Francisco• University of Chicago• University of Maryland Medical Center
• Year 2: • Each of the five Year 1 sites recruit three additional
“satellite” sites• 7 additional sites begin sharing images for clinical trials
Project TeamProject Team
• Steering Committee:PI: David S. Mendelson, MD – Mount
Sinai Medical Center Co-PI: Brad Erickson, MD – Mayo
ClinicRon Arenson, MD – University of
California, San FranciscoDavid Avrin, MD, PhD – University of
California, San FranciscoPaul Chang, MD – University of
ChicagoEliot Siegel, MD – University of
Maryland Medical Center
• Technical CommitteeMicah Adams, MSc – UMMCSteve Langer, PhD – Mayo Steve Moore, MSEE – Mallinckrodt
Institute of Radiology, Washington University, St. Louis
Femi Oyesanya – University of ChicagoEd Rackus – University of ChicagoKen Shastri, Project Manager Wyatt Tellis, PhD – UCSFWendy Zhu – University of Chicago
Overall PlanOverall Plan
• Year 1: • Develop systems needed to enable image sharing through
PHRs• Establish sharing of images and reports at five initial sites via
PHR• Year 2:
• Expand patient information sharing via PHR to satellite sites• Begin sharing images for clinical trials at seven additional
research site• Recruit growing number of patients throughout course of trial• Gather information on patient usage and impact on radiology
operations at participating sites
Systems DesignSystems Design
• Based on IHE XDS model• Data to be shared images (CT, MR, X-Ray) and diagnostic
reports• All data access will be through PHR accounts• Simplified model for sharing to address policy considerations• Using PHRs to simulate “CD over the Wire”
CD Over the WireCD Over the Wire
• Participating sites currently create (and import) hundreds of imaging CD/DVDs daily
• Physical media are time consuming to create• Physical media rely on patient maintenance and delivery to
subsequent care providers• In spite of DICOM and IHE, inconsistency in formatting and
viewers• Online delivery offers potential to improve incrementally, but
significantly upon current state of practice
Personal Health Records (PHRs)Personal Health Records (PHRs)
• “an electronic record of health-related information on an individual that conforms to nationally recognized interoperability standards and that can be drawn from multiple sources while being managed, shared, and controlled by the individual.”
National Alliance for Health Information Technology. (2008). Report to the Office of the National Coordinator for Health Information Technology on Defining Key Health Information Technology Terms. http://www.nahit.org/images/pdfs/HITTermsFinalReport_051508.pdf.
Steps in Sharing via PHRSteps in Sharing via PHR
• Site staff obtain consent and enroll patient• Site staff assemble submission set (images, reports and
manifest) and submit to Clearinghouse• Patient is provided two-factor security key (via printout
and/or email) for retrieving record through PHR• Site staff provide patient with instructional material on
creating and using PHR account• Patient creates account, logs in, uses security key to retrieve
record into PHR• Patient provides subsequent care providers with access to
records through PHR
Network ComponentsNetwork Components
• “Edge” Device at each site to bridge local imaging and information systems with image sharing network
• Image “Clearinghouse” to temporarily store images and reports
• One or more Web-based PHR providers capable of securely retrieving images and reports from clearinghouse into patient account
System ArchitectureSystem Architecture
Edge DeviceEdge Device
• Listens to HL7 messages from RIS, captures completed reports
• Enables site personnel to create an encounter record by selecting one or more sets of images and reports
• Retrieves image studies from PACS• Creates XDS-based payload including images, reports and
manifest• Generates security key to identify patient submission set and
sends package to Clearinghouse
ClearinghouseClearinghouse
• Receives, registers and stores submission set (images, reports, manifest) for designated period (eg, 30 days)
• Responds to queries from designated PHR systems providing security key and sends requested submission set
Personal Health Record (PHR)Personal Health Record (PHR)
• Allows creation of secure patient-controlled account• Provides facility for patient to enter security key and
retrieves and processes selected encounter record from Clearinghouse
• Provides persistent storage for images and reports• Provides Web-based viewer for images and reports• Provides mechanism for secure download of images
for viewing in local environment
Based on IHE XDS-I ModelBased on IHE XDS-I Model
• Defines transactions (Web services) and encoding of submission set (MTOM/XOP)
• Edge Server adds Document Source capability to local RIS-PACS environment
• Clearinghouse includes Registry/Repository and PIX Manager (for Patient ID management)
• PHR acts as Document Consumer to retrieve submission set
IHE XDS-I.b Data FlowIHE XDS-I.b Data Flow
Imaging Document
Source
Document Consumer
(XDS.b)
Document Registry
(XDS.b)
Document Repository (XDS.b)
Provide & Register Imaging Document Set – MTOM/XOP [RAD-68]
Register Document Set – b [ITI-42]
Retrieve Document Set [ITI-43]
Registry Stored Query [ITI-18]
WADO Retrieve [RAD-55] Retrieve Imaging Document Set [RAD-69]
Retrieve Images [RAD-16] Retrieve Presentation States [RAD-17] Retrieve Reports [RAD-27] Retrieve Key Image Note [RAD-31] Retrieve Evidence Documents [RAD-45]
Imaging Document
Consumer
IHE XDS ModelIHE XDS Model
• Assumes HIE “Affinity Domain”: network of sites with shared security policies and BAAs for information sharing
• Access by care providers at sites participating in Health Information Exchange (HIE) is primary use case
• Patient demographic information used to link documents acquired at various sites
• Longitudinal record exists in HIE registry
IHE XDS-I HIE ModelIHE XDS-I HIE Model
Care Site
Care Site
Care Site
Care Site
Imaging Center
Community Health Center Regional Hospital
Local Clinic
Repository
Repository
RegistryRegistry
Health Information Exchange Health Information Exchange NetworkNetwork
RegionalRepository
Alterations of IHE ModelAlterations of IHE Model
• Not a Health Information Exchange (HIE) model• No coordination of local patient IDs across sites• No exposed PHI or subject discovery through
network• Patient ID Cross-Reference (PIX) Manager
functionality greatly simplified• Treats XDS-I payload like XDS.b: no DICOM/WADO
retrieve• Initially, information sharing provided only through
PHR
PHR-based ExchangePHR-based Exchange
Care Site
Care Site
Care Site
Care SiteImaging Center
Community Health Center
Regional Hospital
Local Clinic RegistryRegistry
Multi-site Access via PHRMulti-site Access via PHR
Repository
PHRPHR
PHRPHR
Policies Behind DesignPolicies Behind Design
• Security policy has to satisfy most restrictive policy among participating sites:• No inbound connections to clinical systems• No export of unsecured protected health information
(PHI) outside site firewall• No exchange of PHI with other care providers without
business associate agreement (BAA)• Patient controls records (like CD model)• PHR is used to create longitudinal records and share
information across sites
Limitations of Project ModelLimitations of Project Model
• Not a “universal coverage” model• Depends on active patient to initialize sharing• Does not serve patients debilitated by trauma, age,
disease• Initially no aggregation of information for quality, outcomes
analysis• Limited by capabilities and policies of PHR providers
• Capabilities likely to vary• Business model for PHRs not well established
Open QuestionsOpen Questions
• First time medical images are being sent to a device on the Internet. How will CIOs etc. feel about that?
• There are still network bandwidth issues at facilities which may create scaling issues
• Clearinghouse is based on an “hosted environment model”
• PHRs must make modifications to use the RSNA ID and provide viewing functionality
Potential Benefits of ProjectPotential Benefits of Project
• Establish practice of online information sharing• Encourage patient ownership of electronic health
records• Build expectation of patient-control within participating
sites• Improve upon portable media for convenience and
efficiency of information sharing• Show standards-based mechanism and simple
infrastructure for sharing of information through PHRs• Establish functional model that can persist given
commensurate business/funding model
SummarySummary
• Medical images are a high-value use case and a relatively easy win for information sharing
• Participants want to promote standards-based approach for implementing information sharing (IHE)
• Current business and security policies make it impossible to establish a true HIE model in term of current contract
• Information sharing through PHRs is an important incremental step toward greater accessibility of health information for care providers
Thanks for joining us!Questions?
Find out more at Find out more at www.ihe.net
ccarr@rsna.orgccarr@rsna.org
top related