1 / 26

Gazelle Project

Gazelle Project. Eric Poiseau, INRIA Steve Moore, MIR. Plan. Introduction Objectives Architecture Community Plans. Introduction. IHE started 1998 Users and vendors joining forces to improve interoperability Started from Radiology Testing Tools (MESA) Benefit to participants

huyen
Télécharger la présentation

Gazelle Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gazelle Project Eric Poiseau, INRIA Steve Moore, MIR

  2. Plan • Introduction • Objectives • Architecture • Community • Plans

  3. Introduction • IHE started 1998 • Users and vendors joining forces to improve interoperability • Started from Radiology • Testing Tools (MESA) • Benefit to participants • Connectathon

  4. MESA Tools • Developed by MIR (Steve Moore) • Set of perl scripts and C++ applications • Database: PostgreSQL and SQL Server • Test S.U.T for conformance with TF • Distribution package for • Win32, Linux, (Sun in the past) • Yearly cycle • Include new written profile

  5. Kudu Tool • Developed in Rennes (Eric Poiseau) • Started in 2002 with Paris C.A.T • Web based Testing Management tool • Registration • Pre-Connectathon testing • Connectathon testing • Does not interact with S.U.T !

  6. Problems • IHE is growing • 10 domains • 75 integration profiles • 101 actors • Increasing number of used standards • Demand for testing tools increases • Companies, Users, Government… Kudu and MESA need to scale up

  7. Gazelle = MESA + Kudu • Proposal to combine MESA and Kudu • 2nd generation of tool • Avoid 1st generation design errors • Target more use cases • Allowscalability • More developers • Better software, bettercoverage • Improved support

  8. Gazelle Requirements

  9. Objectives • Improve the overall quality of testing • Conformance and Interoperability • Broaden the use of the application • Build a framework for Healthcare interoperability testing

  10. 5 Use Cases • Connectathon • Virtual Connectathon • Company Internal Testing tool • Healthcare Enterprise Testing tool • Governmental organizations

  11. Requirements • Synchronous testing of multiple systems • Multilingual • Scalable

  12. Gazelle Architecture

  13. Architecture Gazelle Control System Database External Validation Services External Validation Services Gazelle Actor (Simulators) External Validation Services Configuration Info Gazelle Test Engine Gazelle Actor (Simulators) External Validation Services Control Gazelle Actor (Simulators) Gazelle Actor (Simulators) Feedback Gazelle Actor (Simulators) System Under Test System Under Test System Under Test System Under Test Tests Scenario Proxy Network

  14. System under test • More than one system can be tested at the same time • One S.U.T, many simulators (~mesa) • Many S.U.T, no simulators (~kudu) • S.U.T management • Web application to provide instruction

  15. Database • Model of TF concepts • Storage of test related information • Assertion to be tested • Ideally provided by the IHE technical committees Test Scenario

  16. External Validation Services • Web services • DICOM Validation • HL7 V2 and V3 message validation • CDA document validation • Common API • Calling Service • Specifycontextual information • Validation Report

  17. Actor Simulators • IHE actorswith Web service interface for control by Gazelle • We are currentlyworking on the API • Configuration • Control • Feedback • Re-use of existing software • Need to adapt to fit API

  18. Proxy • Capture messages • Necessary for EVS services • Currently investigating MIRTH for HL7 • Kudu to create Mirth channel • Call to HL7 EVS for captured messages • To be used during Oxford Connectathon

  19. Test Engine • Controlssimulators • API iswork in progress • Controls proxy • Based on ActiveBpel • Work of Umberto Capellini (Tiani-Spirit)

  20. Building a Community

  21. Participants • 3 IHE Regions • NorthAmerica : MIR • Europe : INRIA • Japan : Shizuoka University • DVTK • NIST • Tiani-Spirit • David Clunie • Offis

  22. Contacts • OHF (USA) • OHT (USA) • GIP-DMP (France) • AHML (Australia) • MITRE (USA) • IHE-China

  23. Roadmap • DB model redesign • EVS API Definition • Finalize licence • EVS at Chicago connectathon • DICOM • EVS at Oxford connectathon • HL7, DICOM, CDA • Project web page • Finalize API for Simulators • Replace Kudu for 2008-2009 season • Test in gazelle for PIX PDQ SWF LTW

  24. Project Management • Testing and ToolCommittee • Overview of IHE testingactivities • Choice of the licenses • Testing Management Group • Project Management • Eric and Steve

  25. Licensing • Agreement of an opensourcelicense • Final choice of the licensestill in discussion • Licensingdoes not concerntoolsdeveloped by 3rd party • Typically EVS, Simulators

  26. Thanks Contact : eric.poiseau@inria.fr moores@mir.wustl.edu

More Related