NavigationTime to Bern 2012
88 days until Bern 2012.
User loginWho's online
There are currently 0 users and 1 guest online.
|
GazelleMission StatementIHE Gazelle Tools. The Gazelle project is aimed at developing testing tools for IHE. This tools shall test the interoperability of medical systems and the compliance of the messages send bu those systems with standards recommender by IHE. Gazelle is replacing Kudu, the tool that was first designed to manage IHE connectathon. ManagementThe Gazelle project is led by Steve Moore from the Mallinckrodt Institute of Technology and Eric Poiseau from INRIA The IHE Testing & Tools committee supervises and coordinates the testing activities conducted by National and Regional Deployment Committees and the development of testing software and other tools used in the testing process. The Gazelle projects is using a set of project management tools. The tools and the link to the tools used by the project are listed below:
RoadmapThe Gazelle Roadmap is made available through our bug tracking system.
ArchitectureThe following diagram shows the architecture of the gazelle tools.
Achievements
Gazelle first components were first used during the IHE European 2009 connectathon in Vienna, Austria. At that time, registration, configuration management and results management were handled by Gazelle. The tests selection, running and grading was still performed using Kudu. Gazelle was used again for the 10th European Connectathon in Bordeaux. This was the first time that Gazelle was used to run the connectathon from the registration to the report of results. Gazelle plateform was used to manage the following events :
Active ProjectsTest Management (TM) Master Model (GMM) Demographic Data Server (DDS) This tool provide simulated demographic data to be used during test session. The tool allow test scenario to use realistic data sets. Patient can have names, lastnames and addresses that looks like real. The tools supports generation of data in different locales : names and lastnames in the context of different countries. Addresses with valid zip codes, and finally support of different character sets. Proxy (PROXY)The proxy allows the capture of the messages exchanged by the participants to a test instance. The captured messages are stored in the proxy. The Gazelle Control Module allow the user to associate capture messages with corresponding test instance for message validation in the context of the instance. External Validation Service (EVS)HL7 (available, used in 2009 Vienna and Chicago)Two services have been defined: one by the NIST and one by INRIA. They both use HL7 Message Profiles. More that 140 HL7 message profiles have been written and are available for download from the INRIA Forge Dicom (available, used in 2009 Vienna and Chicago)Two services available. One based on DVTK and one based on Dave Clunie's tool, dciodvfy. CDA (available, used in 2009 Vienna and Chicago)Service available through the NIST Server EVS Client GUI (rewrite in progress)GUI to access the different EVS available. The Tool is currently rewritten to take into account problem of using the tool behind firewalls. The new version will access the content of the TF through webservices instead of using the JNDI method access. The tool is re-writen using Webservices to access the TF data. Choice of WS will garantee better interoperability behind firewals HL7 Message Profile RepositoryHL7 Message Validation ServiceEVS Client Front EndThe EVS Client Front End is a web application that allows users to interact with the different external validation services that are hooked to Gazelle.
Frequently Asked Questions (FAQ) about GazellePlease visit our FAQ page.
|
SearchRecent blog posts
Book navigationTag Clouds |