MacroHealth Internal

Merge and Translate to X12

Receives flow files containing standard runtime contexts, merges documents that contains transaction sets, and generates an X12 file in a streaming.

Widget
Merge_and_Translate_to_X12.png
Configuration
Merge_and_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 MergeAndTranslateToX12.

    • batchSize: Indicates the maximum number of elements a batch can have. 

      If no batching is required, this needs to be defined with a value of 0. The termination of the merge process will be determined by what’s defined in the expectedCountInBatch runtime attribute.

    • documentName: The name of the document in the incoming runtime context to be merged into the batch (i.e. the document containing the transaction set). The other documents in the incoming context will be dropped.

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

    • repetitionSeperator: The repetition separator. If blank it will be retrieved from the ISA Header (ISA11).

    • componentElementSeperator: The component element separator. If blank it will be retrieved from the ISA Header (ISA16).

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

    • indent: Specifies if the output X12 should be indented. The default is true.

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

    • ReceiveCode: The Interchange Receiver ID (ISA08), 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.

    • transactionSetReference: Shovel Expression of a JSON document to append transaction set to. The Reference will be coming from the Context Document.

      Important

      The document should be very small, has the potential to consume a lot of memory.

      {
  "CaseId": "readField(<builtin:document/claim_AdjReq|builtin:key/metadata/caseId>)",
  "CaseType": "readField(<builtin:document/claim_AdjReq|builtin:key/metadata/caseType>)",
  "DocumentId": "readField(<builtin:document/claim_AdjReq|builtin:key/metadata/documentId>)",
  "DocumentType": "readField(<builtin:document/claim_AdjReq|builtin:key/metadata/documentType>)"
}

    • referenceDocName: Document name to write references to. This is a String arbitrary value that will be added which will contain the references that come from that transaction set.

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

    NotesTab.jpg

  3. Click Save.

    MergeAndTranslateToX12Save.png

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

    MergeAndTranslateToX12CG.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.

Single json representation of a document in standard runtime. Documents are contained within a document context. Document also defines a type and associated metadata for the documents.

A Shovel Expression allows a user to calculate values where useful. Shovel Expressions are used by Shovel Operation in order to provide values to the Shovel Operation

Single json representation of a document in standard runtime. Documents are contained within a document context. Document also defines a type and associated metadata for the documents.

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.