.NET EDIFACT/X12 框架
我们需要为客户处理一些 EDI 消息，我想知道你们中是否有人可以推荐一些可以完成该任务的组件（不一定是免费的）。 我对一个可以将 EDI 消息解析为 .NET 结构的框架以及某种传输协议（SMTP、FTP、HTTP、AS2）等的实现感兴趣。
We need to process some EDI messages for a client and i was wondering if any of you could recommend some components (not necessarily free) that could do the task.
I'm interested in a framework that can parse EDI messages into .NET structures and some kind of implementation of transport protocols (SMTP, FTP, HTTP, AS2) etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
http://x12parser.codeplex.com 上有一个开源 .NET x12 解析器，它已经存在了一段时间了。现在已经相当成熟了。 它已经支持超过 15 个交易集，包括 HIPAA 集中的大多数交易集。
它非常适合注入您自己的规范，网站上有相关说明。 查看该站点以获取已解析的 X12 消息的 html 序列化。
我喜欢的一个好处是，它允许您将 X12 拆分为单独的 X12 消息，以便您可以单独处理它们。 例如，如果您想取消捆绑索赔，则只需通过循环 ID“2300”即可取消捆绑。 它将以缩进格式重新序列化您的 X12，以便更容易阅读。 例如，以下是一个 837 声明，它被解析为 Interchange 对象，然后用空格序列化：
There is a open source .NET x12 parser at http://x12parser.codeplex.com that has been around for a while and is pretty mature now. It already supports over 15 transaction sets including most of the ones in HIPAA set.
It's pretty extendable for injecting your own specification, instructions for this are on the site. Check out the site for an html serialization of the parsed X12 message.
The nice thing that I like is that it allows you to unbundle your X12 into separate X12 messages so that you can process them individually. For instance if you want to unbundle claims you just have to unbundle it by the loop ID "2300". It will reserialize your X12 in an indented format so it is easier to reader. For example the following is an 837 claim after it has been parsed into an Interchange object and then serialized with whitespace:
在 http://www.sparrow-technologies.com/ 上有一个商业 .NET X12 解析器ediparser.net.aspx 已经存在了一段时间并且也相当成熟。 它支持X12、HL7和SCRIPT标准。 当我在我的一个项目中使用它时，它非常容易理解。 它附带了不同 EDI 消息类型的分配样本，因此它使我更容易编写我的第一个项目。
There is a commercial .NET X12 parser at http://www.sparrow-technologies.com/ediparser.net.aspx that has been around for a while and is also pretty mature. It supports X12, HL7 and SCRIPT standards. When I used it on one of my projects it was pretty easy to understand. It came with allot of samples of the different EDI message types, so it made it much easier for me to code my first project.
如果您没有严格依赖 .Net，我建议您使用 JCAPS B2B 套件最初由 SeeBeyond Corp 开发。
另外，我听说过 InterfaceWare 的 Chameleon 的好消息
If you're not strictly tied to .Net, I'd recommend the JCAPS B2B suite originally by SeeBeyond Corp.
Otherwise, I've heard good things about Chameleon by InterfaceWare
我在 .NET 中对 EDIFACT 文档进行了一些工作，但从未找到可以使用的框架。 幸运的是，我只需要解析两种不同类型的文档。 在我的情况下，最简单的方法是手动解析文件并创建友好的业务对象，以我可以使用的方式保存数据。 框架将为您提供很大的灵活性和更友好的 API，但这可能不是必需的。
I did some work with EDIFACT documents in .NET, and never found a framework I could use. Fortunately, I only had to parse two different types of documents. In my situation, it was easiest to just parse the files manually and create friendly business objects that held the data in a way I could work with. A framework would give you a lot of flexibility and a friendlier API to work with, but it might not be necessary.
看看：http://www.orionhealth.com/products/symphonia/
它可以满足您的需求，尽管您在使用它时会遇到各种限制。
Take a look at: http://www.orionhealth.com/products/symphonia/
It does what you want, although you will run into various limitations as you use it.