IHE_in_Cardiology-ACC.ppt
Upcoming SlideShare
Loading in...5
×
 

IHE_in_Cardiology-ACC.ppt

on

  • 749 views

 

Statistics

Views

Total Views
749
Views on SlideShare
749
Embed Views
0

Actions

Likes
0
Downloads
11
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Systems means HIS, RIS, modalities, PACS, review stations, printers, etc.
  • E.G. too much data re-entry, too many manual steps “Who owns the problem?” The hospital can’t solve the problem with insufficient tools (although there have been impressive efforts) The integration problem was generally outside the scope of a single vendor/product
  • E.G. too much data re-entry, too many manual steps “Who owns the problem?” The hospital can’t solve the problem with insufficient tools (although there have been impressive efforts) The integration problem was generally outside the scope of a single vendor/product
  • **Consider making the cycle graphic Incremental approach: Can’t solve all at once Connectathon – Practical measure of progress, Validates the integration work accomplished. Refer the Scorecard. Demo – promotes standards based integration to users/purchasers
  • What’s wrong with DICOM? Nothing misinterpretation and ambiguity
  • !! Asking for Scheduled Workflow is a lot easier than comparing DICOM Conformance Statements (“Can your system buy train tickets?” is easier that asking for a list of verbs, nouns, and grammatical syntaxes) The problems are integration problems which means they are communication problems Dictionaries are great. But if I drop you on the Champs Elysee and you want to get a nice meal, Handing you a dictionary is not really solving your problem. Being resourceful individuals you Would start flipping through the dictionary and would eventually get yourself fed, but it would Be slow and painful and you might be surprised what actually showed up on your plate. What would be much more useful would be a phrasebook. It describes specifically how to use the language to accomplish a particular task. This requires a series of predictable transactions with a set of actors. Just like the section on restaurants defines a set of phrases for the maitre d’, the bartender, your waiter, etc for you to make a reservation, get a table, get a menu, order and receive food, pay your bill, etc. The IHE section for the Scheduled Radiology Workflow profile defines a set of transactions for the ADT, the Order Placer, the Modality, the PACS etc. to register a patient, order and schedule a study, pass that information to the modality, Receive status updates, etc.
  • Year 3: Consolidation for IHE (Status, Report/Study Linkage) Catch-up for the vendors and products Original plan called for a 5-year initiative …
  • Framework is being developed now. Likely to require AUDIT TRAIL, system login, node identification/certificates.

IHE_in_Cardiology-ACC.ppt IHE_in_Cardiology-ACC.ppt Presentation Transcript

  • Integrating the Healthcare Enterprise IHE ’s Potential for Cardiology Joseph Biegel Mitra IHE Planning Committee
  • What is IHE?
    • An industry-clinical partnership to integrate clinical information systems throughout healthcare
      • Demographics, images, waveforms, reports
    • Goal: Improve the efficiency and effectiveness of clinical practice by:
      • Providing an implementation framework for open connectivity using existing standards
      • Improving clinical information flow
  • Who participates in IHE?
    • Industry sponsors: Radiological Society of North American (RSNA) and Health Information and Management Systems Society (HIMSS)
    • A neutral forum open to all vendors: Participants include GE, Phillips, Siemens, IDX, Cerner, Mitra, and some 30 others
    • Standards committee members: DICOM, HL7
    • Clinicians, hospital information technology staff, healthcare administrators
  • Why is IHE needed?
    • Serious Integration Challenges:
      • Systems need information from other systems: patient demographics, referring physicians, echo/angio images, ECG waveforms, hemodynamics, clinical reports, etc.
      • But, systems communicate poorly or not at all
      • Result: - tedious, inefficient workflows - data that is inconsistent or unavailable
      • Responsibility for information flow between systems and between departments is often unclear.
  • What does IHE do?
    • Users and vendors work together to identify and design solutions for integration problems
    • Intensive process with annual cycles:
      • Identify key specific healthcare workflows and integration problems
      • Research & select standards to specify a solution
      • Write, review and publish IHE Technical Framework
      • Perform cross-testing at “Connectathon”
      • Demonstrations at meetings (RSNA/HIMSS/ACC)
  • What does IHE cover?
    • Currently focused in Radiology
    • 30 Vendors tested 70 systems at the Year 3 Connectathon
    • Systems include:
      • HIS, RIS
      • MR, CT, US, CR, DX, …
      • PACS, Review Stations, Reporting Systems
      • Printers, Imagers
  • Why aren’t existing industry standards sufficient?
    • Standards are vital (HL7, DICOM, ICD, …)
      • They provide consensus, tools & technologies
      • IHE is entirely standards-based
    • But standards alone are insufficient
      • Varying interpretations
      • Optional variations
      • No real-world specifications or scenarios
      • No assurance of portability or connectivity
  • How is IHE related to standards?
    • IHE focuses on specific, practical integration problems
    • Standards such as HL7 and DICOM provide “dictionaries”
    • IHE defines a “phrasebook” and/or “grammar” that solves real world problems by assembling pieces provided by DICOM/HL7
  • Key IHE concepts
    • Technical Framework: detailed, structured document delineating standards-based transactions among systems (“ IHE actors ”) to support specific workflow and integration capabilities
    • Integration Profiles: Documents specifying integration capabilities for specific patient-care problems
  • IHE’s track record
    • Year 1 (1999): Proof of Concept (Basic Scheduled Workflow)
    • Year 2 (2000): Introduction of 7 Integration Profiles for Radiology
    • Year 3 (2001): Consolidation, Catch-up (Real Products) Expansion to France
    • Year 4 (2002): 3 New Profiles Expansion to Japan, Germany
    • Year 5 (2003): New Profiles Expansion to Cardiology, Lab, Pathology, …?
  • Integration Profile examples
    • Scheduled Imaging-Encounter Workflow
        • Registration, ordering, scheduling, acquisition, distribution, storage
    • Patient Information Reconciliation
    • Consistent Presentation of Images
        • Across various devices, media
    • Key Image Note
        • Adding text notes and pointers to images
  • Why IHE in cardiology (1)?
    • Cardiology workflow involves multiple diagnostic tests, images and reports
    • Cardiology clinical systems/devices typically are unintegrated
      • Separate systems for ECG/Holter, EP, PPM/ICD, echo, angiographic images, hemodynamics, documents/reports
      • Each system typically requires redundant manual data entry, with inevitable errors
  • Why IHE in cardiology (2)?
    • Systems typically do not share data
      • Patient demographics, directories of referring physicians or of images/documents
    • Image formats often not portable
      • Encrypted formats, proprietary readers, variable headers
    • Fragmentation causes inefficiency, invalid or inaccessible clinical data, and compromises the quality of care
  • Why IHE in cardiology (2) ?
    • Some of the concepts of the IHE TF have broad general applicability and many can be applied or adapted to Cardiology
    • The imaging vendors are largely the same
    • DICOM and HL7 are used in Cardiology today
      • Other Cardiology specific standards could easily be leveraged in a Cardiology specific version of the TF
  • Common characteristics
    • Cardiology is similar in some vital respects to radiology
      • Driven by imaging modalities
      • Managing distributed departmental resources
      • Need for an integrated patient-centered view and for administrative reporting
      • Need to improve lab efficiency via workflow management
      • Legacy installed base technology issues
  • Cardiology workflow elements
    • Workflow often similar to radiology:
      • Patients are admitted
      • Demographics entered (often multiple times for the same patient)
      • Imaging studies are performed and read
      • Reports generated
  • Distinct cardiology needs
    • Clinical data content is more complex
      • Therapeutic as well as diagnostic procedure reports, with richer report content
      • Richer graphical content: moving images, color
      • Clinical encounter data
      • Outcome reporting
    • Cardiology focuses on an integrated patient view rather than on procedures, images and reports in isolation
  • IHE/cardiology possibilities (1)
    • Image exchange/portability
      • Even with DICOM, image transfer and display often don’t work
      • Difficulty importing outside images into local archives
    • As part of a cardiology Technical Framework, IHE could specify unambiguous, vendor-supported, compatible DICOM implementations
  • IHE/cardiology possibilities (2)
    • Redundant, manual patient demographic data entry is slow and error prone
      • DICOM and HL7 can help, but the standards themselves are not enough
    • IHE could leverage or adapt its Scheduled Workflow Integration Profile and Patient Information Reconciliation Profile for cardiology, resulting in a single entry point for patient demographics, accessible to all cardiology systems and devices
  • IHE/cardiology possibilities (3)
    • IHE can develop generic, standards-based interfaces between cardiology devices/systems and enterprise systems for scheduling, ordering and results reporting
    • Cardiology makes large capital purchases of imaging and information systems without assurance that systems can co-exist or interface: The “fear at power on” factor
    • The IHE TF can define vendor-neutral requirements that assure interoperability
  • IHE/cardiology possibilities (4)
    • Structured reporting: In partnership with ACC and clinicians, IHE could develop standards-based cardiology reports, including diagrams and graphics for anatomy, function and viability
    • Beyond static, black-and-white DICOM: IHE could develop Implementation Profiles for motion images, color images, waveforms, Doppler, pediatric echo
      • IHE and industry will do the heavy lifting at the technical level
      • BUT IHE needs ACC involvement
        • To ensure that IHE focuses on clinical needs and provides clinically relevant solutions
        • To act as impartial, patient-centered observers (rarely referees), so that IHE remains truly vendor-neutral
    An IHE/ACC partnership
  • Conclusions
    • IHE can dramatically improve the care of cardiology patients and life for cardiologists.
    • To succeed--and to do justice to its goals--IHE needs both expert cardiology input and ACC involvement