对于.NET HL7对象模型 [英] HL7 object model for .NET

问题描述

在搜索库或框架，提供一个对象模型，分析，验证，等等

这个想法是要能够旋转起来类型HL7 V2或V3的新对象。然后，也许称它为消息类型ORU_R01或ADT，或ORM。

难道没有生命是伟大的，如果我们能够做这样的事：

  HL7V2 myMessage =新HL7V2（）;
myMessage.Type = V2MsgTypes.ORU_R01;
myMessage.TryParse（someHL7_string）;

如果（myMessage.IsValid）
{
  //做一些工作
  //也许访问PID段
  如果（myMessage.Patient.Names.FamilyName ==强生）
  {
    //做更多的工作
  }
}
 

解决方案

您想要 nHAPI 我用它在一个项目previously，和它的工作太棒了。事实上，它是开源救了我的熏肉也作为输入源没有precisely遵循HL7规范，所以我不得不砍源一点点地让nHAPI的解析器允许这些消息对（我无法改变他们）。

Searching for a library or framework that would provide an object model, parsing, validating, etc

The idea would be to be able to spin up a new object of type hl7 v2 or v3. Then perhaps call it message type ORU_R01 or ADT, or ORM.

Wouldn't life be great if we were able to do something like this:

HL7V2 myMessage = new HL7V2();
myMessage.Type = V2MsgTypes.ORU_R01;
myMessage.TryParse(someHL7_string);

if (myMessage.IsValid)
{
  //do some work
  //maybe access the PID segment
  if (myMessage.Patient.Names.FamilyName =="Johnson")
  {
    //do more work
  }
}

解决方案

You want nHAPI I used it on a project previously, and it worked great. The fact that it's open source saved my bacon too, as one of the input sources didn't precisely follow the HL7 spec, so I had to hack on the source a little bit to make nHAPI's parser allow those messages (as I couldn't change them).

这篇关于对于.NET HL7对象模型的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！