To use this add-on, manually configure the data input with the following input.conf
properties and the add-on will optimize the data automatically.
sourcetype = hl7_v2
These properties will also be utilized by the underlying searches and eventtypes .
The value from this Add-on is derived by it's ability to:
If the logs come from Cloverleaf's Interface engine there are additional extractions for thread_id, client ip, and client port.
*The datetime format can vary for each HL7 message. In lieu of using TIME_FORMAT inside props.conf
a custom datetime.xml was created inside this app. The extracted groups correspond to those specified
in the extracted attribute for define element. The groups (year, month, day, etc.) are specified in
Splunk's default datetime.xml in /etc/system/datetime.xml.
**Repeating Segments will be placed inside multi-value fields.
i.e. If there are four NTE segments in the message there will be one multi-value NTE field with four values.
The subsequent HL7 fields will only be extracted for the first segment in repeating segments.
The reference files used for this Add-on can be found in the cloverleaf_logs directory.
The samples directory contains files used to generate sample messages. If you add Splunk's Eventgen these samples will be replayed and put in the hl7 index. Please see https://github.com/splunk/eventgen and use the develop branch.
You'll also need to modify splunkUser and splunkPass in eventgen.conf to match credentials on your system.
This Add-On currently has prebuilt Panels and Dashboards.
HL7 - Events by Message Type - Over Time
HL7 - Event Count by Message Type - Over Time
HL7 - Raw Events - Over Time
Patient Activity History
TRANSACTION CONVERSION (assumes you also ingest the corresponding HL7 ACKs)
To Davin Studer and The Vancouver Clinic that allowed extensive regression testing on this Add-On.
-Updated Message Type Lookup ( hl7_v2_message_types.csv). Please use Message_Type_Description in lieu of previous Message_Type in your searches.
- Updated files in samples to replay messages with missing patient names and identifiers.
- Put SEDCMD back to replace carriage returns with line feeds.
- Removed indexes.conf
- Added instructions to README.md for extracting individual segments when they are repeating.
- Modified files in samples for eventgen to populate the default/main index instead of previously used hl7 index.
- Modified LINE_BREAKER in props.conf to properly parse HL7 messages that contain "MSH" in the actual message, not just the three first characters.
- Commented out SEDCMD in props.conf for replacing carriage return with line feed.
- Added new sample file in cloverleaf_logs
=== Splunk TA HL7 (Add-On) ===
Author: Joe Welsh - Splunk
Version/Date: 1.05 August 25, 2016
*Note: This app was previously Add-on for HL7
This add-on supports logs containing HL7 v2.X data.
Source type(s): This add-on will process data that is source-typed
Input requirements: N/A
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.