ihe product selection and acceptance testing

18
IHE Product Selection and Acceptance Testing

Upload: cor-loef

Post on 07-May-2015

105 views

Category:

Technology


0 download

DESCRIPTION

IHE, Integrating the Healthcare Enterprise, creates solutions for interoperability problems in healthcare by developing standards based interface specifications. Healthcare ICT products that have implemented the IHE specifications make the integration efforts for an eHealth solution much easier. Conformity assessment in the deployment process towards an operational application portfolio is supported by a proven test methodology and Open Source test tools.

TRANSCRIPT

Page 1: IHE product selection and acceptance testing

IHE Product Selection and Acceptance Testing

Page 2: IHE product selection and acceptance testing

Streamlining Product Selection and Acceptance Testing v Effective and efficient performance of Business Use Cases are enabled by

a connected set of administrative and clinical applications v Initial challenge:

Ø  Selection of suppliers and systems Ø  Integrate systems, educate users, and start-up the operation

v On-going challenge: Maintain the operational ICT Application portfolio Ø  New releases Ø  New systems Ø  New connections Ø  New functionality

v IHE profiles for exchange, content, terminology, workflow, security and privacy enable this in a multi-vendor setting.

v Supported by the IHE Test Tools and Procedures in the Conformance Assessment continuum.

Page 3: IHE product selection and acceptance testing

Deployment: the Road to Production

Connectathon: IHE profile level

Testing

Product Release Testing

Projectathon: Interoperability Specification

Testing

Acceptance Testing

Production

Entrance Rules Governance

IHE Profiles

IHE Profiles

Interoperability Specifications

Product Accredited Testing (ISO17025:2005)

Page 4: IHE product selection and acceptance testing

Connectathon key figures

Page 5: IHE product selection and acceptance testing

Connectathon results matrix

On-line registry showing for all Connectathons worldwide which vendors have successfully passed the tests with their products for a selected set of IHE Profiles.

v  Health IT suppliers have the opportunity to showcase the IHE competency of their company.

v  Health IT buyers can easily search for evidence of supplier’s IHE claims. http://connectathon-results.ihe.net/

Page 6: IHE product selection and acceptance testing

Development In-house pre-release testing

Connectathon participation

In-house final release testing

ISO 9000 QMS ISO 14971 Risk Management IEC 62304 Software Lifecycle Processes

eHealth Product Release

IHE Profiles IHE Integration Statements

Connectathon Results Matrix

Product Registry

Page 7: IHE product selection and acceptance testing

Product Registry

On-line Product Registry for commercially available health IT products that conform to the specifications of a selected set of IHE Profiles.

v  Health IT suppliers have the opportunity to showcase the IHE capabilities of their products.

v  Health IT buyers can easily search for available products fulfilling their IHE integration needs.

http://product-registry.ihe.net/PR/home.seam

Page 8: IHE product selection and acceptance testing

Example: Services of the eSanté platform

Medical Facility Guide

Provider Signature and encryption

Directory structure patient

Empowerment Terminology server

Directory structure security

Repository XDS

Registry XDS-B XDS-I

Patient portal

Multi services portal System of communication and dissemination of information

eHealth platform

Professional portal

Administration portal

Message Broker

SOA Web

services

Actors

National HPD ID

Labs

Hospitals

GPs Secure messaging

Patient ID PIX Manager

E-RCP

Traceability

Pharmacies

epSOS PCN

EAI

CNS API

Medical application SaaS

Care facility

Emergency care

Publ

ic He

alth

Patie

nts

Healt

hcar

e Pr

ofes

siona

lls

Page 9: IHE product selection and acceptance testing

Key health systems objectives

Business Use case A

Profiles

Technical Use case 1

IHE Profile for Content

Custom Profile for

Terms

Technical Use case 2

IHE Profile Sharing Doc

Services

IHE Profile Patient Id

Mgt

Technical Use case 3

IHE Profile for Security

IHE Profile for

Privacy

Project Interoperability Specification

Com

bina

tion

/ Glu

e

IHE Profile for

Content Custom

Profile for Terms

IHE Profile Sharing Doc

Services

IHE Profile for

Security IHE Profile

for Privacy

IHE Profile Patient Id

Mgt

Interoperability Specification

Page 10: IHE product selection and acceptance testing

N.(N-1) 2N

Challenges: semantics of exchanged content, localization, and workflow v  DICOM (images, reports, treatment plans, etc.) v  CDA documents (Lab, Pharmacy, Patient Summary, etc.) v  HL7 v2, v3 message

Complexity of eHealth Integration

Page 11: IHE product selection and acceptance testing

Specifications/Standards

System A

Vendor A System B

Vendor B

Conformance checks

Interoperability testing

Conformance checks

Validators

Simulators Test Management

Tools for Interoperability and Conformance Assessment

Page 12: IHE product selection and acceptance testing

Interoperability & Conformance Tests

ü Configure ü Interacts

Information exchange

Test Management

Test Plan

Value Sets

TF Model

Gazelle Test Platform

ü Configure ü Interacts

ü Get Test Plan ü Find Test Partner ü Log Evidences ü Get Test Report

ü Get Test Plan ü Find Test Partner ü Log Evidences ü Get Test Report

ü Checks Evidences ü Verifies test performs as planned ü Grades

Proxy

Validator Validator Validator Validator Validator

Information exchange

Monitor

System Under Test Simulator

Page 13: IHE product selection and acceptance testing

Available IHE Validation Tools

v HL7v2 messages v DICOM objects v XML documents/messages

Ø  HL7 CDA Structured Document Ø  HL7v3 messages Ø  IHE XD* transactions metadata Ø  DSUB metadata Ø  HPD messages Ø  Sharing Value Set messages content (SVS) Ø  Workflow documents (XDW) Ø  ATNA audit messages Ø  X509 certificates Ø  SAML Assertions

Page 14: IHE product selection and acceptance testing

Available IHE Simulators

v Patient Manager Ø  ITI profiles relative to patient demographics exchange Ø  PAM, PIXv2, PDQv2, ADT part of SWF

v Order Manager Ø  Profiles dealing with management of orders Ø  LAW, LTW, SWF, EYECARE workflow

v XD* Client : Initiators from the XD* profiles, DSUB, XDS-I.b v Sharing Value Set v Healthcare Provider Directory v Hospital Medication Workflow (Pharmacy) v Lab Barcode Labelling v Lab Code Set Distribution

Page 15: IHE product selection and acceptance testing

Contributors to IHE Test Tools v Open source, freely available, yet need on-going development and maintenance v Parties contributing to pool of tools

Ø  Government initiatives funding tool development via eHealth projects •  NIST •  EC •  Japan

Ø  IHE USA, IHE Europe •  Vendors participating in Connectathon

Ø  Professional Societies as IHE Domain sponsors: •  HIMSS •  RSNA •  ACC •  ASTRO •  AAO

v http://ihewiki.wustl.edu/wiki/index.php/Index_to_Preconnectathon_Test_Software#Index_to_IHE_Test_Tools

v http://hitch-project.eu/testing-tools

Page 16: IHE product selection and acceptance testing

Example eSanté: Standalone Document Validation

EVS

Fron

t End

Model Based CDA Validator

1 - HTTP : Upload of document

2 – WS Call

3 – XML Report

System under test

eSanté CDA Guidelines

Page 17: IHE product selection and acceptance testing

Your Contribution to a Sustainable eHealth Interoperability Ecosystem

Test Tools

eHealth Suppliers

IHE Profiles

Healthcare providers

Foster the creation new IHE Profiles for emerging interoperability challenges

Timely release products to market with IHE Integration Statements

Include IHE profiles in eHealth solution architecture and RFPs.

Include IHE Test Tools creation in eHealth programs, and contribute to Open Source pool of IHE Test Tools.

Page 18: IHE product selection and acceptance testing

Value from applying IHE

v Suppliers of eHealth systems Ø  Reduce cost for development and maintenance of product

communication interfaces (reduced diversity, Open Source tool box) Ø  Access to bigger market (reduced market entry threshold)

v Users of eHealth systems Ø  Freedom to choose products with best-fit functionality (competition)

v ICT Department Ø  Reduce integration cost (reduced diversity, reduced complexity,

Open Source tool box) Ø  Reduce on-going maintenance cost for the ICT Application portfolio

(reduced diversity, Open Source tool box)