This wiki has undergone a migration to Confluence found Here
Context Conduction in RIMBAA Applications
Revision as of 19:59, 16 January 2009 by Rene spronk (talk | contribs)
Summary
- HL7 v3 contains a definition for Context Conduction. Particulary for RIMBAA implementations the support for this methodology is crucial - querying part of an object tree without knowing what conducts where could lead to real problems. This page seeks to discuss ways in which people have implemented this, and to document best practices.
Analysis
There seem to be two options when one received a serialized v3 model in a RIMBAA context:
- denormalize the conduction, i.e. replicate the conducted context (participations, act relationships) where appropiriate. The RIMBAA application (except when importing/exporting the data) is agnostic as to the meaning of context conduction.
- deal with the conductivity at 'run-time', i.e. whenever a query is made determine what conducts and include that in the response. There are obvious performance issues associated with this option.
- What are the advantages/drawbacks of these two options? Whi has chosen to use what option?
- There are problems with the current definition of context conduction. What are its feasblae parts, what parts are broken (based on RIMBAA implemenetation experiences, not in theory)?
