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 7: Line 7:
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
| An interaction binds one trigger event, one payload model, one control act wrapper, one transport wrapper, a sending application role, a receiving application role, and one or more receiver responsibilities.
+
| Each trigger event must have a unique name
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
| This is the definition of an HL7 interaction.
+
| The trigger events must be able to be precisely referenced when creating interactions.  The trigger event is the reason for communicating information.
 
|-
 
|-
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-model-dynamic.xsd
+
* ?
 +
|}
 +
 
 +
 
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| Each application role must have a unique name
 +
|-
 +
| ''Rationale''
 +
| The sending and receiving application role must be able to be precisely referenced when creating interactions.
 +
|-
 +
| ''MIF''
 +
|
 +
* ?
 
|}
 
|}
  
Line 20: Line 33:
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
| For each interaction, trigger event, and application role, name is required.
+
| Each receiver responsibility must have a unique name
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
| The name property is used to reference artifacts.
+
| The receiver responsibilities must be able to be precisely referenced when creating interactions.
 
|-
 
|-
 
| ''MIF''  
 
| ''MIF''  
 
|
 
|
* mif-model-dynamic.xsd
+
* ?
 
|}
 
|}
  
Line 46: Line 59:
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
{| border="2" cellspacing="0" cellpadding="3" width="600"
 
| '''Requirement'''  
 
| '''Requirement'''  
| For each interaction, trigger event, document, and application role, three annotation types are to be supported:  
+
| For each interaction, trigger event, document, and application role, annotations must be supported:  
* Annotation (Descriptive info),
 
* Documentation (Contains 'plain' comments.  Plain comments are those with no additional XML elements, except possibly one which identifies the 'type' of comment
 
* AppInfo (Contains complex comments.  Complex comments are those with additional XML elements, above and beyond the 'type' of comment
 
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  

Revision as of 20:04, 20 October 2009