This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Requirements-Dynamic Model"

From HL7Wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
</div>
 
</div>
  
==Annotation Components==
+
==Dynamic Model Components==
 +
The behavioral aspects of communicating via HL7 V3 information models is referred to in HL7 as the dynamic model.  The dynamic model includes the following:
 +
 
 +
interaction - A single exchange of data between systems (sending/receiving each with an application role) for a particular reason with a set of expected response behaviors (user action, interaction response, state based)
 +
 
 +
interaction binds wrappers with payload - transport wrapper, control act (trigger event) wrapper, payload
 +
 
 +
interaction patterns
 +
user action - trigger event
 +
interaction based (query) -
 +
state based - introduction of state machine, statuses
 +
 
 +
trigger event - reason or action why information is exchanged ; ne and only one action to perform
 +
 
 +
 
 +
application role - functional capability of a system/application
 +
 
 +
parameter model - Identifies a parameter and the static model it is bound to.
 +
 
 +
BoundStaticModel - Identifies a root static model as well as any models bound to parameterized stubs within the model.
 +
 
 +
receiver responsibility - Identifies a possible set of actions to be taken in response to the receipt of an interaction.
 +
 
 +
 
 +
a class (model focus) defined in a state diagram associated with a class in an information model. State diagrams, which show all of the potential states for a class, are developed for classes that are the central subject of an interaction. These classes are called subject classes. Interactions are sometimes motivated by changes in the state of a subject class. For example, Act may be identified as a subject class. The vocabulary domain for the Act.status_cd declares the defined states for the Act. Those states include Active, Suspended, Cancelled, Complete, and Aborted. A state diagram depicts the allowable class states with a box labeled with the name of the state. Changes in state are called state transitions and are depicted in the diagram by a line with a arrowhead showing the direction of the transition. An example of a state transition might be the change in the state of an Act from Active to Complete. The change in state (state transition) is associated with a trigger event that causes the transition. The trigger event in this example might be the fulfillment of an order. An order is a special type of Act. The transition from an Active order to a Completed order is triggered by the fulfillment of the Order. The state diagram depicts the states, trigger event, and state transitions of interest.
 +
model - AMS
 +
 
 +
state machine?
 +
 
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
Line 14: Line 42:
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-core-base.xsd\BasicAnnotation\text (multiple repetitions)
+
* mif-model-dynamic.xsd
* mif-core-base.xsd\BasicAnnotation\text\@lang
 
 
|}
 
|}
  
 
</div>
 
</div>
 
[[Category:V3 Methodology Requirements]]
 
[[Category:V3 Methodology Requirements]]

Revision as of 13:44, 19 October 2009