Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assertion Error when Trying to transform to Pandas #6

Open
javigoncompte opened this issue Jun 18, 2021 · 4 comments
Open

Assertion Error when Trying to transform to Pandas #6

javigoncompte opened this issue Jun 18, 2021 · 4 comments

Comments

@javigoncompte
Copy link

~/miniconda3/envs/835_parser/lib/python3.9/site-packages/edi_835_parser/transaction_set/transaction_set.py in to_dataframe(self)
45 datum = TransactionSet.serialize_service(
46 self.financial_information,
---> 47 self.payer,
48 claim,
49 service

~/miniconda3/envs/835_parser/lib/python3.9/site-packages/edi_835_parser/transaction_set/transaction_set.py in payer(self)
34 def payer(self) -> OrganizationLoop:
35 payer = [o for o in self.organizations if o.organization.type == 'payer']
---> 36 assert len(payer) == 1
37 return payer[0]
38

AssertionError:

@keironstoddart
Copy link
Owner

@javigoncompte, thank you for your interest in this library. I should find time to take a look at this issue over the weekend.

@javigoncompte
Copy link
Author

i think it happens when the 835 has the same payer but multiple payer segments for multiple claims

@keironstoddart
Copy link
Owner

Look into 'joined' 835s.

@Abdelzero
Copy link

Hello,

I am running to the same issue here. What I noticed is that the 835 files for my clearinghouse comes most of the time with different payer name for each claim. it doesn't mean it is an entire different payer but just a different plan. is it possible to make this loop through payer and as it does for patient name if applicable. Thank you

rposborne referenced this issue in affect-therapeutics/edi-835-parser May 30, 2024
added code changes to write remit_adjustments table
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants