MacroHealth Internal

Translate to X12

Translates into an outgoing X12 file.

Widget
Translate_to_X12.png
Configuration
Translate_to_X12_Config.png

  1. Fill in the following fields:

    • Description: Allows changing the name that appears on the widget. This may be useful to quickly find a particular widget or distinguishing it from other similar shovel operation widgets when building large flows.

      Description.png

    • Shovel Operation: The name of the Shovel Operation. Pre-configured to TranslateToX12.

    • documentName: The name of the Context Document containing the data to create the X12 file from.

    • elementSeperator: The element separator to use. Default is *

    • repetitionSeperator: The repetition separator. If blank, it will be retrieved from the ISA Header (ISA11). (See the Implementation documents or visit https://x12.org)

    • componentElementSeperator: The component element separator. If blank, it will be retrieved from the ISA Header (ISA16). (See the Implementation documents or visit https://x12.org)

    • segmentSeperator: The segment separator to use. Default is ~

    • indent: This property specifies if the output X12 should be indented. The default is true.

    • senderCode: The Interchange Sender ID (ISA06 and GS02), which is the name of the entity who will send the entity. The value is an arbitrary String value (e.g., MacroHealth).

    • receiverCode: The Interchange Receiver ID (ISA08 and GS03), which is the name of the entity that will receive the entity. The value is an arbitrary String value such as the name of the Payer or the Network.

    • isa13SequenceName: The Interchange control number (ISA13), which is an arbitrary String value (e.g., interchangeControlNumberSequence)

    • gs06SequenceName: The Group control number (GS06), which is an arbitrary String value.

  2. If necessary, click the Notes tab and enter any relevant information.

    NotesTab.jpg

  3. Click Save.

    TranslateToX12Save.png

  4. The widget will be marked with a green check.

    TranslateToX12GC.png
In this section:

A Shovel Operation is the simplest building block that can be used to build flows. Shovel Operations define configuration, inputs and outputs and are combined together in order to build more complex flows.

A field in json a document that contains all the information the is saved while the file is moving through the flow and that serves to make decisions at certain stages of that flow.