适用于CPOE-EMR app的.net规则引擎 [英] .net Rule Engine for CPOE-EMR app

查看:191
本文介绍了适用于CPOE-EMR app的.net规则引擎的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试在基于.net的EMR / EHR应用程序中为计算机化医嘱录入(CPOE)模块的规则引擎制定构建/购买/使用开源决策。我们正在尝试这样做是有意义的使用(MU 2014)兼容。



我对医疗保健领域是全新的,并且非常感谢有关此主题的任何帮助。



问题:有没有人做出这样的决定?你的选择是什么?为什么?如果您决定构建一个自定义引擎,那么请告诉我一些基本的设计策略。



我已经看过像InRule,RulesEngine,Drools和SimpleRuleEngine这样的工具。我发布这个问题的原因不是要启动关于规则引擎的一般性讨论,而是要找出人们是否已经特意做了我想要做的事情:即将药物或实验室订单规则引擎集成到他们现有的CPOE / EMR系统中。在我的研究中,到目前为止,InRule看起来是一个很好的候选者,但是它有相关的成本。如果可能,我的客户正试图避免它。

I am trying to make a 'build/buy/use opensource' decision on a rule engine for the Computerized physician order entry (CPOE) module within the EMR/EHR application which is .net based. We are trying to do this to be Meaningful Use (MU 2014) compliant.

I am totally new to the healthcare domain and would highly appreciate any help on this topic.

Questions: Has anyone made such a decision? What was your choice and why? If you decided to build a custom engine then please tell me some basic design strategies.

I have already looked at tools like InRule, RulesEngine, Drools and SimpleRuleEngine. The reason why I am posting this question is not to initiate a generic discussion on rule engine but to find out if people have done specifically what I am trying to do: i.e. integrate a medication or lab order rule engine into their existing CPOE/EMR system. In my research so far InRule looks like a good candidate but there is a cost associated with it. My customer is trying to avoid it if possible.

推荐答案

是的,我在使用.Net 3.5引擎后评估了规则引擎,虽然规则编辑器有有很多不足之处,特别是因为它是一个示例项目,我发现Microsoft提供的规则引擎是最好的。比Inrule简单得多,Inrule有更好看的编辑但更复杂(另外我发现了一些不足之处)。我以为我听说MS买了InRule,但我可能弄错了,我希望不会。 IBM有一个解决方案,但IBM的典型解决方案是昂贵且臃肿。我已经使用了WCF的MS规则引擎,它运行良好,可以再次使用它。
Hi, yes I've evaluated rules engines after using the .Net 3.5 engine, and although the rules editor has a lot to be desired, especially because it's a sample project, I find the Microsoft provided rules engine is the best. A lot simpler than Inrule, which has better looking editors but is more complex (plus I found several deficiencies). I thought I heard that MS Bought InRule, but I might be mistaken, I hope not. IBM has a solution, but typical of IBM it is expensive and bloated. I've used the MS rules engine with WCF, it worked well and may use it again.


这篇关于适用于CPOE-EMR app的.net规则引擎的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆