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 18: Line 18:
  
 
===Requirements===
 
===Requirements===
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| HL7 requires a structure for the dynamic model components.  The primary structure is the interaction (described above).
 +
|-
 +
| ''Rationale''
 +
| A formal structure is needed to produce formalized, harmonized standards.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd/Interaction
 +
|}
 +
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
Line 27: Line 39:
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-model-dynamic.xsd/Interaction/@invokingTriggerEvent
+
* mif-model-dynamic.xsd/TriggerEvent
 +
* mif-model-dynamic.xsd/Interaction/invokingTriggerEvent
 
|}
 
|}
  
Line 46: Line 59:
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
| Each trigger event must include a type. There are three types.
+
| Each trigger event must include a type.
*interaction-based
 
*state-based
 
*user-based
 
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
 
| The trigger event types communiate the 'pattern' expected as far as receiver responsibilities.  For example, and interaction-based trigger event is 'kicked off' when a triggering interaction is communicated.   
 
| The trigger event types communiate the 'pattern' expected as far as receiver responsibilities.  For example, and interaction-based trigger event is 'kicked off' when a triggering interaction is communicated.   
 +
|-
 +
| ''Methodology''
 +
| There are three types:
 +
*interaction-based - An interaction caused by the receipt of another interaction.  For example query reponse.
 +
*state-based - An interaction caused by a change in status.  For example, putting a repeating order on hold (to suspend action on that order)
 +
*user-based  - An interaction caused by a user interacting with a system or some other environmental occurrence.
 
|-
 
|-
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* Interaction-based: mif-model-dynamic.xsd/TriggeringEvent/@interaction
+
* Interaction-based: mif-model-dynamic.xsd/TriggeringEvent/interaction
* State-based:  mif-model-dynamic.xsd/TriggeringEvent/@stateTransition
+
* State-based:  mif-model-dynamic.xsd/TriggeringEvent/stateTransition
* User-based:  mif-model-dynamic.xsd/TriggeringEvent/@environmentalOccurrence
+
* User-based:  mif-model-dynamic.xsd/TriggeringEvent/environmentalOccurrence
 
|}
 
|}
  
Line 71: Line 87:
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-model-dynamic.xsd/EnvironmentalOccurrence/@text
+
* mif-model-dynamic.xsd/EnvironmentalOccurrence/text
 
|}
 
|}
 +
 +
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| State-based trigger events must reference the model being acted upon.
 +
|-
 +
| ''Rationale''
 +
| Required to know which information model to update.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd/EnvironmentalOccurrence/text
 +
|}
 +
  
  
Line 97: Line 127:
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-model-dynamic.xsd/Interaction/@argumentMessage
+
* mif-model-dynamic.xsd/Interaction/argumentMessage
 
|}
 
|}
  

Revision as of 15:49, 21 October 2009