Difference between revisions of "HL7"

From GreenVulcano Wiki
Jump to: navigation, search
m
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==Overview==
 
==Overview==
HL7 is a standard for the exchange, integration, sharing, and retrieval of electronic health information. The standard defines how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world.
+
[http://www.hl7.org/ HL7] is a standard for the exchange, integration, sharing and retrieval of electronic health information. The standard defines how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world.
  
* Created to exchange information related to patiens
+
* Created to exchange information related to patients
 
* Standardizes the health system at clinical data exchange level
 
* Standardizes the health system at clinical data exchange level
 
* Provides interfaces that allow the data flow through various systems
 
* Provides interfaces that allow the data flow through various systems
Line 11: Line 11:
  
 
==HL7 Connector==
 
==HL7 Connector==
The {{GVESB}} HL7 connector enables the inbound and outbound connection using the HL7 protocol in its version 2.x.
+
The {{GVESB}} HL7 connector enables the inbound and outbound connections using the HL7 protocol in its version 2.x.
 
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of HL7 applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the HL7 standard used.  
 
The use of the connector joint with the peculiarities of the {{GVESB}} [[Virtual Layer]] allows the management of HL7 applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the HL7 standard used.  
Basically the connector allows the virtualization of the input/output operations to a HL7 application, making available to the service definition process the interfaces able to hide all the technical details related to HL7 standard. It is possibile to define the message exchange mode transforming with a mapping operation the HL7 messages in XML messages, using any schema. The composition of the integration flowLa realizzazione del flusso di integrazione quindi, comporterà l'utilizzo di interfacce verso i sistemi Hl7 secondo una struttura dati vicina al modello di business che si sta utilizzando e comunque definita dall'utente.
 
  
Il connettore Inbound consente di creare messaggi Hl7 nella versione 2.x inviare messaggi Hl7 a una o più destinazioni
+
Basically the connector allows the virtualization of the input/output operations to a HL7 application, making available to the service definition process the interfaces able to hide all the technical details related to HL7 standard. It is possible to define the message exchange mode transforming with a mapping operation the HL7 messages in XML messages, using any schema. The composition of the integration flow will comprise a data structure close to the business model that user is adopting or anyway a user defined data structure.
  
Il connettore Outbound consente di scegliere che tipo di messaggi accettare e instradare. Possomo essere scelte destinazioni multiple automaticamente in base alle specifiche dei filtri HL7.
+
The Inbound HL7 Connector allows the HL7 message creation (in the version 2.x) to be sent to one or more destinations; the Outbound HL7 Connector allows to choose what message type to accept and route. Multiple destinations can be chosen automatically basing on the HL7 filters specifications.
  
L’interfaccia del DTE di GreenVulcano (Eclipse Based) permette con facilità la creazione dei trasformazioni dati mappatura dei messaggi HL7. La mappatura viene effettuata con dei semplici “Drag and drop”.  
+
{{GVESB}} [[XML Data mapper | Data transformation]] feature allows fast creation of data transformation and mapping of the HL7 messages. The data mapping is made through simple "Drag and Drop" operations.
  
==Connettore Hl7 Outbound==
+
==Outbound HL7 connector==
  
Il connettore Hl7 outbound permette di definire una chiamata ad un sistema Hl7 definendo i parametri di connessione e utilizzando poi l’operazione definita all’interno di un flusso di integrazione definito su GreenVulcano ESB attraverso Vulcon ([[Starting Guide Vulcon|Guida introduttiva a Vulcon]]).
+
Allows to define a call to a HL7 system defining the connection parameters and using the operation defined in an integration flow on {{GVESB}} through [[VulCon]].
I passi da eseguire per la definizione di un canale Hl7 sono i seguenti:
 
  
 +
These are the easy steps to follow to define a HL7 [[Channel]]:
  
Creazione di un sistema e di un canale Hl7 con la definizone di un operazione hl7-call
+
Creation of a [[System]] and of a [[Channel]] with the definition of a [[Hl7-call]] [[Operation]]
[[Image:1100px-ChannelHl7.png]]
 
  
 +
[[File:1100px-ChannelHl7.png|thumb|center|256px]]
  
* host: nome host o indirizzo IP dove l’applicazione Hl7 e in ascolto di messaggi
+
* host: hostname or IP address of the HL7 application waiting for the message
* name: nome dell’operazione del Virtual Layer
+
* name: [[Virtual Layer]] [[operation]] name
* port: porta IP dove l’applicazione Hl7 e in ascolto di messaggi
+
* port: application HL7 port
* timeout: timeout del canale Hl7
+
* timeout: channel HL7 timeout
  
Definizione del un servizio per l’invocazione del canale Hl7 definito:
+
Definition of a service for the invocation of the defined HL7 [[channel]]:
[[Image:1100px-ServizioHl7.png|1100px]]
 
  
Il servizio così definito può essere richiamato utilizzando una qualsiasi modalità prevista da GreenVulcano ESB: web-services, http, tcp-ip etc. Il connettore Hl7 gestisce i messaggi Hl7 trasformandoli in messaggi xml. Per il mapping da un generico messaggio ad un messaggio Hl7 è possibile definire una mappa di trasformazione attraverso il Data Transformation di Vulcon. Per la creazione della mappa accedere alla configurazione della mappa avendo preventivamente definito gli schemi xsd che definiscono il formato del messaggio di input (preveniente da qualsiasi sorgente dati) e il formato HL7 di output:
+
[[File:1100px-ServizioHl7.png|thumb|center|256px]]
  
 +
The service defined in this way can be called in any way allowed by {{GVESB}} i.e. [[Web Services]], http, tcp-ip, etc.
 +
The HL7 connector manages the messages transforming them into XML messages.
  
[[Image:TrasfHl7.png]]
+
For the mapping from a generic message to a HL7 message it is possible to define a transformation map through [[XML Data mapper | VulCon]] tool.
 +
To create the map, go to map configuration after having defined the xsd schema for the input message (incoming from any data source) and the output HL7 format:
  
 +
[[File:TrasfHl7.png|thumb|center|256px]]
  
 +
[[File:1100px-Mapping.png|thumb|center|256px]]
  
[[Image:1100px-Mapping.png|1100px]]
+
==Inbound HL7 Connector==
 +
The inbound HL7 connector allows the definition of a HL7 message listener, associating the message reception to a {{GVESB}} [[service]].
 +
The received HL7 message can be forwarded to one or more systems using any available {{GVESB}} enabled protocol: [[Web Services]], JDBC, email, ftp, etc. After every message received, a response message must be sent as acknowledge of the transaction (or abort). The connector enables the reply message creation with no applicative effort, mapping automatically the flow result with the ACK message to send back to the caller application.
  
 +
The easy steps to follow to define an HL7 [[GVHL7ListenerManager | Listener]] are the following:
  
==Connettore Hl7 Inbound==
+
Definition of a filter to apply to every received HL7 message:
Il connettore Hl7 oubound permette di definire un listner in ascolto di un messaggio Hl7 associando la ricesione del messaggio ad un servizio definito sulla piattaforma GreenVulcano ESB. Quindi la ricezione del messaggio HL7 può essere inoltrata ad uno o più sistemi che secondo tutti i protocolli utilizzabili da GreenVulcano ESB: Web-services, JDBC, email, ftp etc. Ad un messaggio ricevuto deve corrispondere un messaggio di risposta per accettazione o rifiuto della transazione. Il connettore permette di cerare un messaggio di risposta senza nessun sforzo applicativo, in quanto mappa automaticamnete l'esito del flusso di integrazione con il messaggio di ACK da inviare all'applicazione chiamante
+
[[File:1100px-ListnerHl7.png|thumb|center|256px]]
  
I passi da eseguire per la definizione di un canale Hl7 sono i seguenti:
+
Association to a HL7 message to the [[service]] defined on {{GVESB}}:
 
+
[[File:1100px-ListenerServiceHl7.png|thumb|center|256px]]
Definizione del filtro da applicare ai messaggi HL7 ricevuti:
 
[[Image:1100px-ListnerHl7.png|1100px]]
 
 
 
 
 
Associazione messaggio Hl7 con il servizio definito su GreenVulcano ESB:
 
[[Image:1100px-ListenerServiceHl7.png|1100px]]
 
<ol>
 

Latest revision as of 08:40, 4 April 2014

Overview

HL7 is a standard for the exchange, integration, sharing and retrieval of electronic health information. The standard defines how information is packaged and communicated from one party to another, setting the language, structure and data types required for seamless integration between systems. HL7 standards support clinical practice and the management, delivery, and evaluation of health services, and are recognized as the most commonly used in the world.

  • Created to exchange information related to patients
  • Standardizes the health system at clinical data exchange level
  • Provides interfaces that allow the data flow through various systems
  • Makes the health interoperability possible

Message structure

A HL7 message is composed by segments placed in a specific order. Each message is made up of a certain number of different segments (some are optional) that, combined, form a determined message type. A specific segment, identified by a code and a sequence number, represents a logic group of data fields and can be used only once within a specific message.

HL7 Connector

The GreenVulcano® ESB HL7 connector enables the inbound and outbound connections using the HL7 protocol in its version 2.x. The use of the connector joint with the peculiarities of the GreenVulcano® ESB Virtual Layer allows the management of HL7 applications in a simple and efficient way, separating the logic of the process implementation from the specific management of the messages and their structure, independently from the HL7 standard used.

Basically the connector allows the virtualization of the input/output operations to a HL7 application, making available to the service definition process the interfaces able to hide all the technical details related to HL7 standard. It is possible to define the message exchange mode transforming with a mapping operation the HL7 messages in XML messages, using any schema. The composition of the integration flow will comprise a data structure close to the business model that user is adopting or anyway a user defined data structure.

The Inbound HL7 Connector allows the HL7 message creation (in the version 2.x) to be sent to one or more destinations; the Outbound HL7 Connector allows to choose what message type to accept and route. Multiple destinations can be chosen automatically basing on the HL7 filters specifications.

GreenVulcano® ESB Data transformation feature allows fast creation of data transformation and mapping of the HL7 messages. The data mapping is made through simple "Drag and Drop" operations.

Outbound HL7 connector

Allows to define a call to a HL7 system defining the connection parameters and using the operation defined in an integration flow on GreenVulcano® ESB through VulCon.

These are the easy steps to follow to define a HL7 Channel:

Creation of a System and of a Channel with the definition of a Hl7-call Operation

1100px-ChannelHl7.png
  • host: hostname or IP address of the HL7 application waiting for the message
  • name: Virtual Layer operation name
  • port: application HL7 port
  • timeout: channel HL7 timeout

Definition of a service for the invocation of the defined HL7 channel:

1100px-ServizioHl7.png

The service defined in this way can be called in any way allowed by GreenVulcano® ESB i.e. Web Services, http, tcp-ip, etc. The HL7 connector manages the messages transforming them into XML messages.

For the mapping from a generic message to a HL7 message it is possible to define a transformation map through VulCon tool. To create the map, go to map configuration after having defined the xsd schema for the input message (incoming from any data source) and the output HL7 format:

TrasfHl7.png
1100px-Mapping.png

Inbound HL7 Connector

The inbound HL7 connector allows the definition of a HL7 message listener, associating the message reception to a GreenVulcano® ESB service. The received HL7 message can be forwarded to one or more systems using any available GreenVulcano® ESB enabled protocol: Web Services, JDBC, email, ftp, etc. After every message received, a response message must be sent as acknowledge of the transaction (or abort). The connector enables the reply message creation with no applicative effort, mapping automatically the flow result with the ACK message to send back to the caller application.

The easy steps to follow to define an HL7 Listener are the following:

Definition of a filter to apply to every received HL7 message:

1100px-ListnerHl7.png

Association to a HL7 message to the service defined on GreenVulcano® ESB:

1100px-ListenerServiceHl7.png