EDI Converter 2.15.2 Release: Expanded 835 CSV Output and Windows Installer

August 14, 2026

We’re pleased to announce version 2.15.2 of our EDI Converter, along with version 2.15.3 of the CLI and desktop application.

This release expands 835 CSV conversion with separate files for provider-level adjustments and transaction-level payment data. It also adds the payee tax ID to claim-level CSV output, fixes a high-priority 835 adjustment parsing issue, improves CLI logging, and introduces a Windows installer that bundles Java and configures the CLI automatically.

You can view all model changes in GitHub diff format.

Scroll down to openapi/components/schemas/model to review the schema changes.

CSV Conversion of Provider-Level Adjustments for 835

EDI Converter now creates a separate CSV file for provider-level adjustments from the PLB segment. These adjustments apply to the provider rather than a specific claim or service. They can include accelerated payments, fiscal-year cost report settlements, and timeliness-related penalties.

The file uses the -ProviderAdjustments suffix. The converter creates it even when the input 835 file does not contain provider-level adjustments, in which case the file is empty.

See the provider adjustment data dictionary for column definitions and EDI mappings.

You can also review an example provider adjustment CSV file.

CSV Conversion of Transaction-Level Data for 835

EDI Converter now creates a separate CSV file for transaction-level payment data. Its columns include the check number, total paid amount, receiver account number, and other payment fields.

Although some transaction fields also appear in the main claim-level CSV file, the separate transaction file provides one record per payment and avoids duplicate payment data across claims.

The file uses the -Transactions suffix. See the transaction data dictionary for column definitions and EDI mappings.

You can also review an example transaction CSV file.

Windows Installer for the CLI and Desktop Application

Windows users can now install the EDI Converter CLI and desktop application with a single installer. The installer:

  • Installs the application for the current user without requiring administrator privileges.
  • Bundles a Java runtime, so you do not need to install Java separately.
  • Adds ediconvert to your user PATH.
  • Creates a desktop shortcut for the EDI Converter application.

After installation, open EDI Converter, select Help > Manage License…, and choose your edi-license.txt file. Then open a new Command Prompt and run ediconvert -V to verify the installation.

The installer is currently unsigned, so Microsoft Edge or Windows SmartScreen may display a warning. See the EDI Converter CLI installation guide for download instructions and the steps for allowing the installer to run.

Bug Fixes

We’ve fixed a high-priority defect that affected adjustment parsing in 835 files.

CSV Layout Changes

We’ve added the Payee Tax ID column to the claim-level CSV file for 835 transactions.

The CLI now writes conversion logs to ~/.ediconvert/logs on Linux and macOS, or C:\Users\<username>\.ediconvert\logs on Windows. Previously, it wrote logs to each directory where a conversion was performed.

We’ve also made file-processing logs easier to follow: each processed file is numbered, and completion messages report the result more clearly.

How to Upgrade

API Docker Container

Pull the 2.15.2 image:

docker pull myarch/ediconvert:2.15.2

If you use Docker Compose, update the image tag to myarch/ediconvert:2.15.2 and run docker compose pull.

EDI Parser for Java

Update your Gradle or Maven dependency:

implementation "hdi:edi:2.15.2"

AWS Lambda Function

Update the Lambda deployment from our S3 bucket:

aws lambda update-function-code --function-name <your-function-name> \
  --s3-bucket ediconverter \
  --s3-key ediconvert-lambda-2.15.2.zip

CLI Tool

On Windows, download and run the 2.15.3 installer. If you have not configured a license, open EDI Converter, select Help > Manage License…, and choose your edi-license.txt file. Open a new Command Prompt after installation, then run ediconvert -V and verify that the output includes ediconvert 2.15.3.

On macOS with Homebrew:

  1. Run brew upgrade healthcare-data-insight/tap/ediconvert if the CLI is already installed, or brew install healthcare-data-insight/tap/ediconvert for a new installation.
  2. Keep your license file at ~/.ediconvert/edi-license.txt.
  3. Run ediconvert -V and verify that the output includes ediconvert 2.15.3.

On Linux, or for a portable installation on Windows or macOS:

  1. Download the ZIP distribution.
  2. Keep edi-license.txt at C:\Users\<username>\.ediconvert\edi-license.txt on Windows or ~/.ediconvert/edi-license.txt on Linux and macOS.
  3. Extract the archive and replace your existing installation files, including the lib and conf directories.
  4. Run ediconvert -V and verify that the output includes ediconvert 2.15.3.

The ZIP distribution requires Java 17 or later. See the installation guide for platform-specific setup instructions.