STC | iQ (v. April 2018) User Guide

HL7 Transaction Log Viewer

The HL7 Transaction Log page displays the transaction details of an HL7 message as it moves through PHC Hub to the IIS. This can be helpful when investigating or troubleshooting issues.

To search for and review transaction events that occur during HL7 message processing, click the HL7 Transaction Log Viewer menu link in STC | iQ. The HL7 Transaction Log page opens.

NOTE: Prior to the Issue Resolution Validation event, the system validates and verifies that the facility has permission to query and send data to the IIS. If the message fails to authenticate, the record does not appear in the HL7 Transaction Log.

The organization and facility used are based on the names entered in the main search bar (which may be based on the user's account). Enter the additional filter criteria and click Search. The search/filter fields available on this page are as follows:

Field	Description
Patient Name	Enter at least a few characters of the patient's first or last name.
MRN	Enter the patient ID (medical record number) to search for.
Lot #	To search for patients with a specific vaccine lot number, enter it here.
Dates	To search for patients within a specific date range, enter the from and to dates here.

The search results appear in a table below the filter area. Most of the columns can be sorted by clicking on the header.

The columns displayed in the search results section are listed below. To sort by a column, click on the column header. Click here to see an image of the HL7 Transaction Log page with example search results.

Column	Description
ID	The transaction ID number.
MRN	The patient medical record number.
Patient	The patient's name.
Lot #	The lot number.
Organization	The organization.
Facility	The facility.
Status	The transaction event, such as Issue Resolution Validation or Processing in the IIS.
Date/Time	The date and time of the message import.
Details (button)	Click the Details button to view the entire raw HL7 message and additional information on the Transaction Details page.

Transaction Event Details

Click the Details button for an HL7 message to open the Transaction Details page and view a snapshot of data as it moves through specific processing stages. As the system processes a message, a transaction event is recorded.

At the top of the page, the raw HL7 message is displayed. Under the message, the details are listed in a table with three columns:

Column	Description
Transaction Event	The actual transaction event for the HL7 message, including Authentication, HL7 Validation, Issue Resolution Validation, and Processing in the IIS.
Status	The status of the message, such as Pass or Fail.
Date	The date and time the transaction event occurred.

The table below lists additional information about the transaction and system processing events:

Transaction Event that Displays in the HL7 Transaction Log Viewer	System Processing Event
Issue Resolution Validation	Logical decisions are made to accept or reject the message based on its content. Formatting, grammar, content, logical consistency, and data quality are all evaluated during this process.
Validation/Transformation	Values from multiple EHR formats are interpreted and standardized into a single, consistent IIS format.
Validation/Transformation	HL7 parsing, validation, and transformation processing are finished and the data is handed off to the registry for automated processing.
Processed in IIS	The IIS attempts to match patient and vaccine data within the IIS (deduplication process).
Saved in IIS	Data is inserted or merged into the IIS. Patient and vaccine information can be searched and viewed in the IIS.

Additional Transaction Information

Transaction details provide more specific information on what happened to the HL7 message of a patient record. Details are only available for two transaction events:

Processed in IIS
Saved in IIS

The following sections list all possible transaction details for an HL7 message. Not all of the messages display in the transaction event details. Details depend on what specifically occurred to the HL7 message. For example, if a patient record was placed in Ambiguous ID in the IIS, the A patient's record with the name [Name] and a DOB of [Date of Birth] has been placed in Ambiguous ID and is in line for processing message displays under the transaction event Processed in IIS.

IWeb Messages

The following may display in the HL7 Transaction Log viewer as transaction details for IWeb records.

Processed in IIS Messages

A contraindication is in line for processing for a patient placed in Ambiguous ID with the name [Name] and a DOB of [Date of Birth].
A contraindication is in line for processing.
A patient's record with the name [Name] and a DOB of [Date of Birth] has been placed in Ambiguous ID and is in line for processing.
A patient's record with the name [Name] and a DOB of [Date of Birth] has been placed in manual deduplication and is in line for processing.
A [Vaccination Type] vaccination with an administered date of [Date] is in line for processing for a patient placed in Ambiguous ID with the name [Name] and a DOB of [Date of Birth].
A [Vaccination Type] vaccination with an administered date of [Date] is in line for processing.

Saved in IIS Messages

A new contraindication has been created.
An existing contraindication has been updated.
A new patient's record with the name [Name], a DOB of [Date of Birth] and a SIIS ID of [SIIS ID] has been created.
A patient's record with the name [Name], a DOB of [Date of Birth], and a SIIS ID of [SIIS ID] has been updated.
A new [Vaccination Type] vaccination with an administered date of [Date] has been created.
An existing [Vaccination Type] vaccination with an administered date of [Date] has been updated.

imMTrax Messages

The following may display in the HL7 Transaction Log as transaction details for imMTrax records.

Processed in IIS Messages

A contraindication for [Contraindication Name] with an applies-to-date of [Date] is in line for processing.
A contraindication for [Contraindication Name] with an applies-to-date of [Date] is in line for processing for a client sent to manual merge.
A client record with the name [Name] and a DOB of [Date of Birth] is in line for processing.
A client record with the name [Name] and a DOB of [Date of Birth] has been sent to manual merge.
A client record with the name [Name], a DOB of [Date of Birth], and an imMTrax ID of [New Client ID] was eligible for auto-merge but the matching client is in a manual merge set. The client has been added to the manual merge set.
An immunization of [Vaccination Name] with a vaccination date of [Date] is in line for processing.
An immunization of [Vaccination Name] with a vaccination date of [Date] is in line for processing for a client sent to manual merge.
A responsible person with the name [Name] and a relationship of [Relationship] is in line for processing.
A responsible person with the name [Name] and relationship of [Relationship] is in line for processing for a client sent to manual merge.

Saved in IIS Messages

A contraindication for [Contraindication Name] with an applies-to-date of [Date] has been created.
A contraindication for [Contraindication Name] with an applies-to-date of [Date] has been updated during auto-merge.
A client record with the name [Name], a DOB of [Date of Birth], and a staging ID of [Staging ID] has been marked as a problem record and will not be further processed.
A client record with the name [Name], a DOB of [Date of Birth], and an imMTrax ID of [New Client ID] has been created.
A client record with the name [Name], a DOB of [Date of Birth], and an imMTrax ID of [New Client ID] has been updated.
A client record with the name [Name], a DOB of [Date of Birth], and an imMTrax ID of [New Client ID] has been created during auto-merge.
An immunization of [Vaccination Name] with a vaccination date of [Date] has been created.
An immunization of [Vaccination Name] with a vaccination date of [Date] has been updated during auto-merge.
A responsible person with the name [Name] and relationship of [Relationship] has been created.
A responsible person with the name [Name] and relationship of [Relationship] has been updated.
A responsible person with the name [Name] and relationship of [Relationship] has been updated during auto-merge.