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

EDI 5010/ASC X12 5010 transaction support #1577

Open
rbeckman-nextgen opened this issue May 11, 2020 · 3 comments
Open

EDI 5010/ASC X12 5010 transaction support #1577

rbeckman-nextgen opened this issue May 11, 2020 · 3 comments

Comments

@rbeckman-nextgen
Copy link
Collaborator

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

implement support for EDI 5010/ASC X12 5010 transactions.

Imported Issue. Original Details:
Jira Issue Key: MIRTH-1582
Reporter: jboby
Created: 2010-09-30T12:58:27.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

See this thread for more information on the request:
http://www.mirthcorp.com/community/forums/showthread.php?t=3070

Imported Comment. Original Details:
Author: jacobb
Created: 2010-10-05T13:39:28.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

More information on the changes from 4010 to 5010 can be found here:

https://www.cms.gov/electronicbillingeditrans/18_5010d0.asp

Imported Comment. Original Details:
Author: geraldb
Created: 2011-10-11T17:47:42.000-0700

@rbeckman-nextgen
Copy link
Collaborator Author

@rbeckman-nextgen rbeckman-nextgen commented May 11, 2020

It sounds like 5010 transactions have pretty much the same message structure so we wouldn't need to change how it's serialized or anything like that. This may be as simple as adding vocabulary for the 005010 message types.

Imported Comment. Original Details:
Author: narupley
Created: 2013-07-03T10:51:08.000-0700

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.