This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">
Requirements-Dynamic Model
From HL7Wiki
This page documents one or more V3 Methodology Requirements
Requirements
| 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. |
| Rationale | This is the definition of an HL7 interaction. |
| MIF |
|
| Requirement | For each interaction, trigger event, and application role, name is required. |
| Rationale | The name property is used to reference artifacts. |
| MIF |
|
| 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 |
|
| Requirement | For each interaction, trigger event, document, and application role, three annotation types are to be supported:
|
| Rationale | Annotations assist with usability. |
| MIF |
|
| 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 |
|
Future Requirements (not complete)
Note that HL7 is currently re-developing and replacing the current dynamic model methodolgy. Below are SOME of the requirements. Requirements are still being determined and documented as part of the HL7 Enterprise Architecture Framework Alpha implementation projects.
| Future Requirement | Communicate conformance of receiver responsibilities. It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility). |
| Rationale | It is necessary to know which receiver responsibilities must happen (mandatory), should happen (required), may happen (optional), and must not happen (usually based on a previous elaboration of a receiver responsibility). |
| MIF |
|
