ContextControlActRelationship A code that specifies if this ActRelationship propagates associations from the source act to the target act, as well as whether this act relationship can itself be propagated. Discussion: Act relationships and participations that are marked "propagatable" can be propagated along ActRelationships that are marked "conductive." Propagation of object associations is transitive and unidirectional from source to target (i.e., if A propagates to B and B propagates to C then A propagates to C; and propagation always occurs from source to target, never the other way around). The total of all propagated associations along an uninterrupted chain of conductive links leading back from a target act towards the source of act relationships is called the propagated context of that act. All propagated context is lost at an act relationship marked non-conductive. Context propagation can be additive or overriding. Additive propagation adds new associations into the context while overriding propagation replaces previously propagated associations of the same or more specific type with this association. Examples: 1. An observation event has a patient participation marked propagatable and has component observation events linked through act relationships that are marked conductive. This means that the patient participation is a patient participation of those component observation events. 2. A composite order has a patient-participation, an author-participation, and a reason-relationship to a diagnosis, all marked as propagatable. The order further has three detail orders as components (A, B and C). The component associations for A and B are marked as conductive. The component association for C is marked non-conductive. Both A and B also have participations for Author. A's participation is marked as propagating. B's participation is marked as propagating with override. The interpretation is as follows: A has the same patient, author and reason as the parent, as well as an additional co-author. B has the same patient and reason, but only the single author pointing to it directly (the parent author was overridden). C is not associated with any patient, author or reason. Rationale: When building an information model, one often wants to avoid repetition. If a model has many constituent parts which all share a set of properties, it is desirable to propagate those properties to the parts, rather than to repeat the properties for each part. However, there are circumstances where unrestrained propagation to constituent parts is undesirable. In many modeling schemes, the propagation is implicit. If there is an author associated with the top element in a hierarchy, the assumption is made that all components within the hierarchy share the same author. If one of the components happens to be a reference to some external document a human reader will likely cease assuming that the author is the same. However, computers and inference engines do not have that same capability of reasoning where propagation of information is appropriate. As a result, there is a need to make this explicit. I.e. there is a need to control (a) what propagates and (b) whether propagation is allowed to occur at all. The context control code provides this capability. |
|||||
Lvl | Type, Domain name and/or Mnemonic code | Concept ID | Mnemonic | Print Name | Definition/Description |
---|
Last Published: 09/01/2005 8:33 AM
HL7® Version 3 Standard, © 2005 Health Level Seven®, Inc. All Rights Reserved.
HL7 and Health Level Seven are registered trademarks of Health Level Seven, Inc. Reg. U.S. Pat & TM Off