Click here to Skip to main content
16,016,022 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
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.
Posted
Updated 1-Feb-14 0:36am
v2

1 solution

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.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900