August 15, 2023

tHL7Input (deprecated) – Docs for ESB 6.x

  2. Talend for ESB Docs
  3. Docs 6.x
  4. tHL7Input (deprecated) – Docs for ESB 6.x

tHL7Input (deprecated)

Reads an HL7 structured file and extracts data row by row.

tHL7Input opens an HL7 structured file and reads it row by row to split
them up into fields then sends the fields as defined in the Schema to the next
component, via a Row link.

tHL7Input Standard properties

These properties are used to configure tHL7Input running in the Standard Job framework.

The Standard
tHL7Input component belongs to the Business family.

The component in this framework is generally available.

Basic settings

Property Type

Either Built-In or Repository:

 

Built-In: No property data stored
centrally.

 

Repository: Select the Repository
file where the properties are stored. The fields that follow are
completed automatically using fetched data.

Save_Icon.png

Click this icon to open a connection wizard and store the Excel
file connection parameters you set in the component Basic settings view.

For more information about setting up and storing file connection
parameters, see
Talend Studio

User Guide.

Multi Schemas Editor

The [Multi Schema Editor] helps
you build and configure the data flow in a multi-structured
delimited file to associate one schema per output.

Segment Lists

Connection: The columns are
automatically retrieved from the input file. The column name is the
segment name.

Column Mapping: The mapping in
this array is retrieved from the mapping you have done in the
editor.

Not Validate HL7 Message

Select this check box if you do not want to validate HL7
messages.

Advanced settings

Advanced separator (for numbers)

Select this check box to modify the separators to be used for the
numbers. Either:

Thousands separator

or

Decimal separator

Encoding

Select the encoding type from the list or select Custom and define it manually. This field
is compulsory.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at each component level.

Global Variables

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an
integer.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage

Usage rule

Usually used as a Start component. An output component is
required.

Scenario: Retrieving information about patients and events from an HL7 file
(deprecated)

This scenario describes a four-component Job which retrieves information about
patients and events from an HL7 file.

Use_Case_tHL71.png

Configuring the editor of tHL7Input

  1. From the Palette, drop an tHL7Input and three tLogRow components onto the design workspace.
  2. Double-click tHL7Input in order to open
    its editor.

    Use_Case_tHL72.png

  3. In the File path field, click [Browse…] and browse the directory to select
    your HL7 file.
  4. In the File Setting area, type in your
    segment Start character and your segment
    End character.
  5. Under Segment(As Schema), in the Schema
    view area, select MSH.
  6. Drop the MSH-3(1)-1-1[IS] and
    MSH-7(1)-1-1[ST
    ] segments from
    the Message View onto the Schema View, and change the User Column value to MSH_LABEL and MSH_DATE
    respectively.
  7. Under Segment(As Schema), in the Schema
    view area, select EVN.

    Use_Case_tHL73.png

  8. Drop the EVN-1(1)-1-1[ID] and
    EVN-2(1)-1-1[ST] segments from the Message View onto the Schema View, and change the User
    Column     value to EVN_ID and
    EVN_DATE respectively.
  9. Under Segment(As Schema), in the Schema
    view area, select PID.

    Use_Case_tHL74.png

  10. Drag and drop the following segments from the Message View onto the Schema
    View    : PID-1(1)-1-1[SI],
    PID-5(1)-1-1[ST],
    PID-5(1)-2-1[ST]    , PID-5(1)-3-1[ST],
    PID-5(1)-4-1[ST],
    PID-5(1)-5-1[ST],
    PID-7(1)-1-1[ST], PID-8(1)-1-1[IS], then change the User
    Column     value to PID_ID,
    PID_FNAME, PID_LNAME, PID_STNUMBER,
    PID_STREET, PID_CITY, PID_BDAY,
    PID_GENDER.

    Note:

    If available, click the Auto map!
    button, located at the bottom left of the interface, to carry out the
    mapping operation automatically.

  11. Click Ok to close the editor.

Configuring the output components

  1. Double-click tLogRow_1 to display its
    Basic settings view and define the
    component properties.
  2. Select Table (print values in cells of a
    table)     mode to display the execution result.
  3. Do the same with tLogRow_2 and tLogRow_3.

Job Execution

  1. Link tHL7Input to the three tLogRow components, using MSH, EVN and PID links respectively.
  2. Save your Job and press F6 to execute
    it.

    Use_Case_tHL75.png

The console displays the three tLogRow tables,
which return different types of information. The first one gives the message header
label and its date. The second table shows the information about the patient. The
third one displays the event ID and its date.

Document get from Talend https://help.talend.com
Thank you for watching.
Docs 6.x
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x