MacroHealth Internal

Receive 999 Ack

The Receive 999 Ack is a standard flow that receives the Ack file from the customer and shoes it with the claim.

Receive999Ack.jpg
Configuration of the Flow Widgets

While configuring the widgets composing this standard flow, only the following parameters should be set by the user:

  • UNIQUE_ID

  • FTP_CONNECTION_ID

  • PAYER

  • ENV

  • DOCUMENT_TYPE

BeginningOfFlow.jpg
Receive 999

This shovel operation allows configuring the FTP settings for file ingestion.

Receive999.jpg

  1. id: UNIQUE_ID (where UNIQUE_ID is an arbitrary ID assigned by the user and must be unique across all integrations)

  2. connectionId: FTP_CONNECTION_ID (where FTP is the connection ID that was defined for this implementation)

  3. directory: /PAYER/ENV/in/ (where /PAYER/ENV/in/ is the path to the origin folder in the FTP server. PAYER is the sender’s name and ENV is the environment or lifecycle's stage name for this implementation)

For more information on how to configure this shovel operation, view External Source.

Validate File

This shovel operation allows validating the 999 ack file.

ValidateFile.jpg

For more information on how to configure this shovel operation, view Validate File.

Split Ack Segments

This shovel operation is an auxiliary step.

SplitAckSegments.jpg

For more information on how to configure this shovel operation, view Split Document.

Set Query

This shovel operation allows defining a query to match claims by looking at claims matching the groupControlNumber and the tsControlNumber.

SetQuery.jpg

  1. mappings: DOCUMENT_TYPE is the doc type to retrieve instances from, such as "AdjudicationRequest".

For more information on how to configure this shovel operation, view Remap Document.

Lookup Claims by Group Control Number

This shovel operation allows looking up claims using the specified query.

LookupClaimsByGroupControlNumber.jpg

  1. docTypeFiler: DOCUMENT_TYPE (where DOCUMENT_TYPE is the doc type such as "AdjudicationRequest")

For more information on how to configure this shovel operation, view Lookup Cases.

DoNothingBranch.jpg
Do Nothing
DoNothing.jpg

For more information on how to configure this shovel operation, view Commit Transaction.

Storing and Processing of the Ack Branch
StoreDocBranch.jpg
Store Ack Document in Claim

This shovel operation allows storing the ack document into each related claim.

StoreAckDocInClaim.jpg

  1. parentDocType: DOCUMENT_TYPE (where DOCUMENT_TYPE is the doc type such as "AdjudicationRequest")

For more information on how to configure this shovel operation, view Stage for Store Document.

Extract Case File IDs

This shovel operation is an auxiliary step.

ExtractCaseFileIds.jpg

For more information on how to configure this shovel operation, view Remap Document.

Single Flow File

This shovel operation is an auxiliary step.

SingleFlowFile.jpg

For more information on how to configure this shovel operation, view Merge Documents.

Build Ack Bundle

This shovel operation is an auxiliary step.

BuildAckBundle.jpg

For more information on how to configure this shovel operation, view Remap Document.

Store Ack Reference in Case File

This shovel operation allows storing the ack’s case file ID into the 837’s original case file.

StoreAckReferenceInCaseFile.jpg

For more information on how to configure this shovel operation, view Stage for Store Document.

Commit
Commit.jpg

For more information on how to configure this shovel operation, view Commit Transaction.

In this section: