News and Updates

November 17, 2024

EDI Converter and Parser API Server Getting Started Guide

You can run our EDI conversion and parsing API server locally on your laptop or server using Docker or Java. The server does not connect to any external services. You will need a license key to run it. The API documentation is available here. See this post for a quick intro to our JSON schema/response format. Installation Steps Installation Using Docker The API server runs in a single docker container without any dependencies.

Read the rest of this post »

October 14, 2024

277CA and 277 Examples

We’ve added several interactive examples of 277 transactions to our collection of EDI examples.

277CA (claim acknowledgment) transactions are sent in response to 837 transactions.

They contain processing statuses and failed edits applied by the payer.

277 response can also be initiated separately by sending a 276 status request.

Read the rest of this post »

October 6, 2024

Key Features and Benefits of Our EDI Converters

We offer two modes for converting EDI files: API (our API back-end can be installed locally as a Docker container) and the command-line tool. Both options produce the same output (except for code descriptions); it is up to you to decide which one you want to employ. We also offer a Java parser that can be embedded directly into any Java application. You can convert your EDI files to JSON or a denormalized CSV file.

Read the rest of this post »

April 23, 2024

Converting X12 EDI 835 and 837 to CSV

You can now convert X12 EDI 835 (ERA) and 837 (claim) transactions to the comma-separated values (CSV) format using our EDI conversion API or the CLI tool. You can also use our UI, all you need to do is to upload your EDI files, navigate to “Payments” and click on “Download CSV.” The API is easy to use. You “post” EDI as text (or upload EDI files; see below) and get a “flattened” CSV representation of your 835/837 back.

Read the rest of this post »

December 5, 2023

EDI Parser for Java

Our EDI Parser for Java is now available. If you don’t use Java, consider our API or command-line converter to parse and convert EDI files from any language. The parser is easy to use and requires no EDI knowledge. Here is a quick example: var parser = new EdiParser(ediFile837p); // parse all claims in the file; alternatively you can parse in chunks List<Claim> claims = parser.parse837(-1); Claim sampleClaim = claims.get(0); // get some key attributes of the claim BigDecimal billedAmount = sampleClaim.

Read the rest of this post »

August 13, 2023

Claim and Payment Lists in EDI Viewer

We’ve implemented claim and payment list views in our EDI Viewer. Claims and payments are now displayed in a table with sortable columns: The table contains all the key fields from a claim (837) or from a payment (835), such as billing provider, billed/paid amounts, and so on. Select an item by clicking on a row to see the rest of the fields. This will display the details view. The back button on the details view navigates back to the list:

Read the rest of this post »

July 19, 2023

API for Parsing/Converting X12 EDI 835

We now provide API to convert X12 EDI 835 transactions into “business-friendly” JSON objects. This API is similar to our 837 claim conversion API. X12 EDI text is “posted” in the request body; the service returns an array of payment objects. You can also convert your 835 files into CSV, see this post for details. The schema of the JSON response is loosely based on the X12 EDI structure without any of the EDI’s complexity.

Read the rest of this post »

June 20, 2023

Viewer for NCPDP Telecommunication Format (Pharmacy Claims)

We are pleased to announce the availability of the online viewer for NCPDP telecom format. The viewer is completely free; it supports all HIPAA transactions, such as B1, B2, N transactions, and so on. The viewer has many features to help you deal with the NCPDP format: Provides a human-readable description for all NCPDP segments and fields; Supports data conversion of NCPDP numeric fields; Decodes NDC numbers and other healthcare codes; Visualizes non-printable NCPDP separators, such as ␞ (RS-Record Start) and ␜ (FS-Field Start); Converts NCPDP to JSON; you can also use our API to do it automatically.

Read the rest of this post »

June 7, 2023

Separators in NCPDP Telecom Format

NCPDP telecommunication format relies on non-printable ASCII characters to denote segments and fields. NCPDP batch standard adds several more non-printable separators to indicate the start/end of transactions and headers/trailers. This is needed to package multiple NCPDP telco transactions in the same file. Non-printable characters are shown as spaces in all browsers and in many text editors. This makes it difficult to work with text containing hidden characters. To solve this problem, more advanced editors and IDEs show small symbols representing non-printable characters, such as ␞ and ␜.

Read the rest of this post »

Blog

Blog

News and Updates