This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Message Infrastructure Fault"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | An ''' | + | An '''Message Infrastructure Fault''' is an abstract term for a communication error encountered at the [[Message Infrastructure Layer]] (MIL) that needs to be communicated back to the application layer. The reason for this need is that this error type cannot be solved by the MIL layer just by retrying to send the HL7 message, and therefore further decision making needs to be sent back to the business entities. |
| − | * | + | == Notes == |
| + | *This concept used to be called [[Application Fault]]. The name was changed because the error is not encountered at the business layer, and the word "application" is somehow misleading. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | Back to the [[Open ATS Issues]] | ||
| + | |||
| + | [[Category:ATS Glossary]] | ||
Latest revision as of 06:42, 21 March 2006
An Message Infrastructure Fault is an abstract term for a communication error encountered at the Message Infrastructure Layer (MIL) that needs to be communicated back to the application layer. The reason for this need is that this error type cannot be solved by the MIL layer just by retrying to send the HL7 message, and therefore further decision making needs to be sent back to the business entities.
Notes
- This concept used to be called Application Fault. The name was changed because the error is not encountered at the business layer, and the word "application" is somehow misleading.
Back to the Open ATS Issues
