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 82: Line 82:
 
{| 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. Note that the identification of artifacts is by identifier.
+
| 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.
 
|-
 
|-
 
| ''Rationale''  
 
| ''Rationale''  
Line 92: Line 92:
 
|}
 
|}
  
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| For each interaction, trigger event, and application role, name is required.
 +
|-
 +
| ''Rationale''
 +
| The name property is used to reference artifacts.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd
 +
|}
 +
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| Interactions have to be able to bind to a message model or a document as the payload.
 +
|-
 +
| ''Rationale''
 +
| There are two 'types' of static model content at HL7.  RMIMs which represent workflow-type communications and Documents which represent point-in-time information.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd
 +
|}
  
Trigger Event Annotation, Documentation, AppInfo
 
Interaction Annotation, Documentation, AppInfo
 
StructuredDocument Annotation, Documentation, AppInfo
 
Application Role Annotation, Documentation, AppInfo
 
Static Model vs. Structured Document
 
for queries and query responses, also ParameterModel
 
Standalone XML document?  GlobalTriggerEvent, Global...
 
  
trigger event - name is required.
+
{| border="2" cellspacing="0" cellpadding="3" width="600"
interaction - name is required
+
| '''Requirement'''
application role - name is required
+
| For each interaction, trigger event, document, and application role, three annotation types are to be supported:
models are referred to by identifier
+
* Annotation (Descriptive info),
two types of static model; RMIMs (static model) and Documents
+
* 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''
 +
| Annotations assist with usability.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd
 +
|}
 +
 
 +
 
 +
{| border="2" cellspacing="0" cellpadding="3" width="600"
 +
| '''Requirement'''
 +
| For each query interaction, an additional binding to the parameter list is required.  Note this includes query requests as well as query responses.
 +
|-
 +
| ''Rationale''
 +
| The parameter list is required for both requests and responses.
 +
|-
 +
| ''MIF''
 +
|
 +
* mif-model-dynamic.xsd
 +
|}
  
 
===Future Requirements===
 
===Future Requirements===

Revision as of 15:35, 20 October 2009