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 34: Line 34:
  
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
| '''Requirement'''  
+
| '''Term'''
 +
| '''Definition'''
 +
|-
 +
| 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).  Definition of the interaction includes declaration of the trigger event, transport wrapper, control act wrapper, and payload.
 +
|-
 +
| 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.
 +
 
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Term'''  
 
| Descriptive free-text metadata about an artifact must be able to be captured in a primary language along with translations to other languages
 
| Descriptive free-text metadata about an artifact must be able to be captured in a primary language along with translations to other languages
 
|-
 
|-
| ''Rationale''  
+
| ''Definition''  
 
| Many HL7 specifications are used by many countries.  Even within a country, there is often a need to publish multiple languages to meet official language requirements or to satisfy the needs of local implementers.
 
| Many HL7 specifications are used by many countries.  Even within a country, there is often a need to publish multiple languages to meet official language requirements or to satisfy the needs of local implementers.
 
|-
 
|-

Revision as of 13:49, 19 October 2009