EDI Management

Platform OperationsGlobal adminLast updated:

This area requires global administrator access in the global tenant context. If you do not have those privileges, you will see a warning message and the content will not be displayed.

EDI Management is where you configure how GEMA processes incoming electronic data interchange (EDI) files received from client SFTP folders, and where you monitor files waiting to be processed or already accepted.

Accessing EDI Management

From the left navigation, select EDI Management. The page loads with three tabs:

  • Mappings — Define and manage EDI mapping configurations.
  • Incoming Files — View files that have arrived via SFTP but have not yet been processed.
  • Accepted Files — View files that have been successfully processed and ingested.

Mappings Tab

The Mappings tab shows a searchable table of all EDI mapping configurations. Each row displays the mapping name, parser type (shown as a colored chip), client, priority, and whether the mapping is Active or Deactivated.

Adding a Mapping

  1. Select Add EDI Mapping in the upper right of the Mappings table.
  2. You are taken to the mapping editor where you can define the mapping configuration.
  3. In the Config panel, fill in the mapping name, client, parser, and other settings. No target schema selection is required — the mapping type is inferred automatically from the field mappings you define.

Editing a Mapping

Select any row in the Mappings table, or select the Edit (pencil icon) in the Actions column, to open the full-page mapping editor for that configuration.

In the editor you can modify the mapping rules, parser type, client assignment, priority, and active status. Save your changes when done.

Deleting a Mapping

Select the Delete (trash icon) in the Actions column for the mapping you want to remove. Confirm the deletion in the dialog that appears.

Mapping Editor

How Mapping Type Is Determined

There is no target schema dropdown. The mapping type — patient or business units — is inferred automatically from the root-level paths in your field mappings:

  • Business units — if all paths start with carrier, account, or group (e.g. ["carrier", "id"]).
  • Patient — if all paths start with patient-level roots such as patient, insurance, medications, observations, diagnosis, procedures, or authorizations.

A mapping that mixes both types will display an error and cannot be activated. Split it into two separate mappings if needed.

The inferred type is stored automatically on save so the processor can handle the file correctly.

Sync Mode (Business Units only)

When the field mappings target the business unit schema (carrier / account / group paths), a Sync Mode section appears near the bottom of the Config panel:

  • Upsert Only — Adds new business units and updates existing ones. Units absent from the file are left unchanged. Use this for partial files or incremental feeds.
  • Full Sync — delete missing BUs — After upserting, deactivates any active business units (within carriers present in the file) that did not appear in the file. A warning is displayed when this mode is selected. Use only when the file is a complete, authoritative list for the included carriers.

When Full Sync is selected, a Delete safety threshold (%) field appears. This is a circuit breaker: if a single import would deactivate that percentage or more of the business units under the carriers present in the file, all deletes are skipped, the upserts still apply, and the import is flagged with a clear warning. This protects against a truncated or malformed file wiping out a carrier’s tree. The default is 40%. Because deletes are always scoped to carriers present in the file, entirely absent carriers are never touched — offboarding a whole carrier is done through the business unit screens, not by omitting it from a file.

Activation

The Activation toggle is at the bottom of the Config panel, after all other configuration. A mapping cannot be activated until field mappings are defined and parser configuration is set. If conditions are not met, the reason is shown below the toggle.

AI Field Mapping

The Map with AI button analyzes your loaded source data and generates field mappings automatically. If you already have some mappings, the AI uses the inferred schema type (patient or business units). If there are no existing mappings, the AI inspects the source columns itself and chooses the appropriate schema — mapping to carrier/account/group if the file looks like an org hierarchy, or to patient/insurance/claims fields otherwise.

Load test data first using the Test Data button, then click Map with AI.

Schema Reference Panel

In the main editor view, switch the right panel to Schema to view the JSON schema for the inferred mapping type. For patient mappings, this shows the patient record schema. For business unit mappings, this shows the carrier/account/group schema expected for each row. The schema panel updates automatically as you edit field mappings.

Testing a Mapping

Select Run in the editor header to open the test dialog. Select a file from S3 or paste sample data, then run the test to see transformed records.

Incoming Files Tab

The Incoming Files tab lists files that have been uploaded to the SFTP and are waiting for EDI intake processing. These files have not yet been run through any mapping.

The table shows each file’s client name (displayed as a chip), file name, file size, and upload timestamp. Select Refresh to reload the list with the latest files from the SFTP source.

If no files are shown, all files have either already been processed or no new files have been uploaded.

Accepted Files Tab

The Accepted Files tab shows files that have been successfully processed and accepted into the system. Use this tab to confirm that a specific file was ingested and to look up processing details.