dimitris1ps/edi-835-parser

A simple EDI 835 file format parser.

EDI 835 Parser

edi-835-parser: a lightweight EDI 835 file parser

This package provides a simple-to-use Python interface to EDI 835 Health Care Claim Payment and Remittance Advice files.

This package is made publicly available by Senscio Systems, the company behind the Ibis Program, an industry leading healthcare initiative that helps people take control of their chronic condition management.

Installation

Binary installers for the latest released version are at the Python Package Index. Please note that you need to run Python 3.9 or higher to install the edi-835-parser.

pip install edi-835-parser

Usage

To parse an EDI 835 file simply execute the parse function.

from edi_835_parser import parse

path = '~/Desktop/my_edi_file.txt'
transaction_set = parse(path)

The parse function also works on a directory path.

from edi_835_parser import parse

path = '~/Desktop/my_directory_of_edi_files'
transaction_sets = parse(path)

In both cases, parse returns an instance of the TransactionSets class. This is the class you manipulate depending on your needs. For example, say you want to work with the transaction sets data as a pd.DataFrame.

from edi_835_parser import parse

path = '~/Desktop/my_directory_of_edi_files'
transaction_sets = parse(path)

data = transaction_sets.to_dataframe()

And then save that pd.DataFrame as a .csv file.

data.to_csv('~/Desktop/my_edi_file.csv')

The complete set of TransactionSets functionality can be found by inspecting the TransactionSets class found at edi_parser/transaction_set/transaction_sets.py

Tests

Example EDI 835 files can be found in tests/test_edi_835/files. To run the tests use pytest.

python -m pytest

Contributing to edi-835-parser

All contributions, bug reports, bug fixes, documentation improvements, enhancements, and ideas are welcome.

Not all EDI 835 elements and segments are currently parsable and not all EDI codes are mapped. If you are interested in contributing to edi-835-parser, please feel free to fork the project and/or reach out by emailing [email protected].

Acknowledgements

A special thank you to Github user gizquier2 for his interest in this project and continued feedback.