This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Requirements-Dynamic Model"
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 | + | | 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 - | + | {| border="2" cellspacing="0" cellpadding="3" width="600" |
− | + | | '''Requirement''' | |
− | + | | For each interaction, trigger event, document, and application role, three annotation types are to 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'' | ||
+ | | 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=== |