This functionality is available in a Stedi module. Contact us for details.
Once you configure fragments for an inbound transaction setting, Stedi splits the translated transaction payload into chunks based on the selected segment.

​
Processing events

Stedi emits two types of events for inbound transactions with fragments enabled: transaction.processed.v2 and fragment.processed.v2. For example, if you enable fragments on Loop 2000 (Member Level Detail) in an 834 Healthcare Benefit Enrollment. Stedi will fragment a translated 834 file and emit the following events:
  • One transaction.processed.v2 event for each unique transaction set that was included in the original file.
  • One or more fragment.processed.v2 events. Each fragment contains several iterations of Loop 2000 (Member Level Detail), the start of which is indicated by the presence of the required initial INS segment.

​
Ingest fragments

You have two options for ingesting fragments from processed inbound transactions into your downstream system.

​
Fragment processed events

Configure a webhook for fragment processed events. As Stedi emits these events, use the Get Fragment endpoint to retrieve each processed fragment from Stedi.

​
Transaction processed events

Configure a webhook for transaction processed events only. After you receive a transaction processed event, use the API to retrieve associated fragments in batches according to your system’s requirements. The event payload includes a fragments object with general information about the fragments that Stedi created.

​
Retrieve inbound transaction with fragments

Stedi does not store the complete transaction for inbound files with fragments enabled. When you use Stedi’s Get Transaction endpoint to retrieve inbound transactions with fragments, Stedi always returns the fragment wrapper (the transaction minus fragments). You cannot retrieve the complete transaction with fragments included - you must use the Get Fragment endpoint to retrieve the fragments separately.