The Food Line

Keith showing the fruits of his pillaging

Edson piles on the plate, worried there won't be anything left for second time round


All things Artificial Intelligence related: Rules, Processes, Events, Agents, Planning, Ontologies and more :)
Drools San Diego 2010 - More Photos
Drools Meetup San Diego 2010 - Update and Photos
Medical | ||
General | ||
Monday | ||
8:00:00 AM | Breakfast. | |
9:00:00 AM | General Introductions | |
9:15:00 AM | Mark Proctor | Introduction To Drools |
10:15:00 AM | Emory Fry begin_of_the_skype_highlighting end_of_the_skype_highlighting | Requirements For Real-Time CDS: The KMR Project |
11:00:00 AM | Mark Proctor | Rule Authoring Techniques |
12:00:00 PM | Requirements Discussion | |
12:30:00 PM | Lunch | |
2:00:00 PM | Edson Tirelli | Complex Event Processing |
3:00:00 PM | Tom Munnecke | Historic Vista / CHS |
3:30:00 PM | Kris Verlaenen begin_of_the_skype_highlighting end_of_the_skype_highlighting | Building Domain Specific Workflows |
4:30:00 PM | Joe White | Healthcare EDI Processing |
5:00:00 PM | Alejandro Osornio | Rule-Based validations applied to Healthcare Ontology |
5:30:00 PM | Requirements Discussion | |
6:00:00 PM | Closeout | |
Tuesday | ||
8:00:00 AM | Breakfast | |
9:00:00 AM | Geoffrey De Smet | Nurse rostering and hospital bed planning with Drools Planner |
9:45:00 AM | Ken Kawamoto | CDS With HL7 & Drools |
10:45:00 AM | Davide Sottara begin_of_the_skype_highlighting end_of_the_skype_highlighting | Using Drools in Hybrid Systems: From "Semantic" Rules to Soft Computing |
11:45:00 AM | Requirements Discussion | |
12:30:00 PM | Lunch | |
2:00:00 PM | Emory Fry begin_of_the_skype_highlighting end_of_the_skype_highlighting | Distributed Knowledge Management Management Requirements |
3:00:00 PM | Davide Sottara begin_of_the_skype_highlighting end_of_the_skype_highlighting | Rule Uncertainty And Vagueness |
4:00:00 PM | Emory Fry begin_of_the_skype_highlighting end_of_the_skype_highlighting | Rule Authoring: Workbench Requirements |
5:00:00 PM | Requirements Discussion | |
5:30:00 PM | Closeout | |
6:00:00 PM | ||
Wednesday | ||
8:00:00 AM | Breakfast | |
9:00:00 AM | James Taylor begin_of_the_skype_highlighting end_of_the_skype_highlighting | Smarter systems for uncertain times |
10:00:00 AM | John Hall begin_of_the_skype_highlighting end_of_the_skype_highlighting | Semantics of Business Vocabulary and Business Rules (SBVR) |
RuleML | ||
11:00:00 AM | Salatino Mauricio | Spring, Camel, Grid and other Community work |
12:00:00 PM | Requirements Recap | |
12:30:00 PM | Lunch | |
2:00:00 PM | Ray Ploski begin_of_the_skype_highlighting end_of_the_skype_highlighting | JBoss Integration |
3:00:00 PM | Diego Nay / Gustavo Aguirre | Drools within a corporate IT architecture |
4:00:00 PM | Kris Verlaenen begin_of_the_skype_highlighting end_of_the_skype_highlighting | Dynamic Fragments For Non-Linear Adaptive Processes |
5:00:00 PM | Kostas Stathatos | Predictive Analytics |
5:30:00 PM | Requirements Discussion | |
6:00:00 PM | ||
Closeout | ||
Thursday | ||
8:00:00 AM | Breakfast | |
9:00:00 AM | Mark Proctor | Introduction To Drools |
10:00:00 AM | break | |
10:15:00 AM | Kris Verlaenen begin_of_the_skype_highlighting end_of_the_skype_highlighting | Building Domain Specific Workflows |
11:15:00 AM | break | |
11:30:00 AM | Mark Proctor | Rule Authoring Techniques |
12:30:00 PM | Lunch | |
2:00:00 PM | Edson Tirelli | Complex Event Processing |
3:00:00 PM | break | |
3:15:00 PM | Labs - Getting environment setup and working through examples | |
5:30:00 PM | Closeout | |
6:00:00 PM | ||
Friday | ||
8:00:00 AM | Breakfast | |
9:00:00 AM | Hands on Day/One to One time | |
Drools San Diego 2010 Agenda
jBPM5 Request for Comments
Name | Talk |
---|---|
James Taylor![]() | Wed 9am Key Note : Smarter systems for uncertain times |
Mark Proctor (JBoss) | Intro to Drools 5 |
Mark Proctor (JBoss) | Rule Authoring Techniques |
Mark Proctor (JBoss) | Spring, Camel and OSGi integration |
Kris Verlaenen | Building Domain Specific Workflows for Clinical Decision Support |
Kris Verlaenen![]() | Dynamic Fragments for Non-Linear Execution of Adaptive Processes |
Edson Tirelli (JBoss) | Applying Complex Event Processing |
Davide Sottara![]() | Enhancing Rules with Uncertainty and Vagueness |
Davide Sottara![]() | Using Drools in Hybrid Systems: from "Semantic" Rules to Soft Computing |
Ken Kawamoto (Duke University) | Clinical Decision Support with HL7 and Drools |
Emory Fry![]() | Delivering Real-Time Clinical Decision Support |
Emory Fry![]() | Rule Workbench Requirements |
Emory Fry![]() | Distributed Clinical Knowledge Mangement Repositories |
Joe White (Recondo Techology) | Healthcare EDI Processing Using Drools |
Kostas Stathatos (Zementis) | Drools & Predictive Analytics: Follow Your Rules and Listen to Your Data |
Diego Naya![]() | Changing the developer mindset to leverage rules, processes and events |
Tom Munnecke (HealthWave) | Historical perspective of VistA and CHCS as foundations for workflow |
Drools OSS Meeting (Reminder) 19th - 23rd of April now at the Hacienda Hotel (San Diego)
Company: | JDM Systems Consultants |
Location: | 3117 Hamilton Court Suite 200 Farmington Hills, MI 48334 |
Website: | www.jdmconsulting.com |
Drools Job in Healthcare
Drools @ BeJUG on April 27th
When a terminal node is matched instead of adding the Activation to the agenda it inserts it into the WorkingMemory. We have a special builder that allows easy access to the contents.
All declarations are typed fields for the Activation fact, based on the "name" field. So the name field is mandatory. All FactHandles are available via an array accessor, which has type inference for the element being used. We also all bindings on the Activation fact to work this way too. Act is used for compactness, we'll allow that to be optionally user defined:
act1 : Act( someDeclaration == X, fact[0] == Y )
act2 : Act( someDeclaration.value > act1.someDeclaration.value )
Normal facts can also be matched. The RHS of the rule is side effect free, you cannot modify or insert facts; this allows the RHS to execute as soon as it's matched. What you can do is setup rule dependencies - where one rule blocks another:
act1.blockedBy( act2 ).until( Fired )
act1.blockedBy( act2 ).until( IsFalse )
We can even allow facts to block:
act1.blockedBy( someFact )
This means the act1 activation is blocked until a rule executes:
act1.unblockedBy( someFact )
We can probably add an override, something like:
act1.unblockAll()
Only when an Activation is no longer blocked will it be placed on the Agenda as normal.
If an activation on the agenda has not yet fired and something attempts to block it, it will be removed from the agenda until it is no longer blocked.
For this to be effective, especially for large systems, it will need to be combined with design time authoring help.
This work will be eventually be combined with further enhancements to help with parallel execution, in resulting conflicts, see the "Parellel Meta-Rule Language" heading.
Goodbye Conflict Resolution Strategy, Hello Rule Dependency Meta Rules
Drools Engineering Job at Cisco Systems (San Jose, CA)