We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 9 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(5)
http://chiapas.sourceforge.net
它可以从命令行执行或集成为 C# 组件。它有一个 76 页的 PDF 手册,其中介绍了许多功能,请查看。
http://chiapas.sourceforge.net
It can be executed from the command line or integrated as a C# component. It has a 76 page PDF manual which goes over many of the features, check it out.
为什么不使用标准映射器而不是尝试编写该野兽的代码?其中有很多雷区(ISA/GS 包络、控制编号、HL 段、段循环),EDI 翻译人员已经有内置字典可供使用。
虽然不是开源的,但有一家公司提供的编程工具可能会对您的事业有所帮助:http://www.edidev .com/(更具体地说:http://www.edidev.com/edidev_hipaa_support.htm< /a>)。
Why not use a standard mapper instead of trying to code that beast? There's a lot of minefields there (ISA/GS enveloping, control numbers, HL segments, segment looping) that EDI translators already have built-in dictionaries to use.
While not open source, there is a company out there who provides programming tools that might help your cause: http://www.edidev.com/ (more specifically: http://www.edidev.com/edidev_hipaa_support.htm).
不是 .net,但是开源的:
http://bots.sourceforge.net
not .net, but is open source:
http://bots.sourceforge.net
查看开源 .NET X12parser。它已经为 X12 医疗保健格式(包括 837)提供了相当强大的支持。您只需提供 XML 格式的 837 数据,它将创建一个有效的 X12 文件。
Check out the open source .NET X12parser. It's already got fairly robust support for the X12 healthcare formats (including 837). You'll just supply the 837 data in a XML format and it will create a valid X12 file.