INRIA HL7v2.x Message Validation Service (Now named Gazelle HL7 Validator)

Click to here to access EVS client

Important News !!!

The INRIA HL7v2.x validator is not more maintained and the web service has been removed at the end of August 2012. The definition of the new web service is available at the URL given in the GazelleHL7v2Validator's documentation. A JAR gathering the client-side classes and an API is also available in our Nexus repository. For more information about the new validation service, read documentation at http://gazelle.ihe.net/content/GazelleHL7v2Validator

 

Inria HL7v2.x validator

Project Overview

The Gazelle HL7v2.x Message Validation Service is part of the External Validation Service provided by the Gazelle project. It allows you to validate HL7v2.x messages against message profiles written at INRIA. For each message you want to validate, you will be asked to provide the context in which this message will be sent, in order to help the application to choose the appropriate message profile. All those profiles are gathered in a database called InriaHL7MessageProfileRepository.

The HL7v2.x Message Validation Service provides a Web Service interface as well as a Web User Interface. validation service is under development.

HL7 Message Profiles

A new web application is now available for browsing, viewing and downloading the HL7v2.x message profiles used by the Message Validation Service. Read the documentation here or direct access the InriaHL7MessageProfileRepository GUI.

Web GUI

Users can access the logger of the HL7v2.x Message Validation Service through the Web GUI available here.

Actually, each time the validation service is called, the message and its validation results are stored in database. This Web GUI lists all the messages and their results and the user can look for a message in particular. Multiple criteria research is enabled. You can retrieve a message thanks to its OID or one or several of the criteria that follow:

• the profile OID the message has been validated against
• the validation date
• a part of the content of the message
• the validation result (PASSED, FAILED ...)
• the IP address of the system which called the validator

Webservice

The WSDL file describing the web service is here. You can also download an example of a soapUI project that uses these methods at here.

Functionalities

HL7v2.x Message Profile Repository implements various web service methods to validate HL7v2.x messages knowing the OID of the appropriate message profile and to retrieve the results of a validated message.

Functionalities of HL7v2.x Message Validation Service can be used by web service methods. Those ones are listed below:

• getValidationServiceStatus : tests if the validation service is available
• validateMessage : validates a message against the given profile and returns the result
• getDetailedResults : returns the detailed results of a validation for a given message OID
• getSummaryResults : returns a summary result of a validation for a given message OID
• getXmlTransformedMessage : returns the message (selected by its OID) using XML formatting
• clearResultCache : clears cache
• aboutThisApplication : returns the information about current application release running on server

WS Client for HL7v2.x Message Validation Service

A Maven project has been developed to help you with accessing the validation web service from your Java applications. Information for retrieving the web service client are:

<dependency>
 <groupId>net.ihe.gazelle.maven</groupId>
 <artifactId>InriaHL7ValidatorClient</artifactId>
 <version>1.5</version> 
</dependency>

You will just need to instanciate the class HL7v2Validator using the URL of the Web Service deployed by InriaHL7Validator application. If you want to use ours, the URL is ... You will be asked to provide the OID of the message profile to use for the message validation, all the profiles we have developed are gathered in one application you can access at http://gazelle.ihe.net/InriaHL7MessageProfileRepository. Those profiles are sorted by domain, actor, transactions and trigger event.

The result is an XML string, an XSL to pretty display these results in HTML has been written and is available here.

 

Our Maven repository is available at http://gazelle.ihe.net/nexus.