This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Message Infrastructure Fault"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
*Discussion: (Miroslav) We might want to look for another term to refer to this type of an error, since this error is not encountered at the business layer, and the word "application" is somehow misleading. | *Discussion: (Miroslav) We might want to look for another term to refer to this type of an error, since this error is not encountered at the business layer, and the word "application" is somehow misleading. | ||
| − | **Paul is suggesting Message Infrastructure | + | **Paul is suggesting Message Infrastructure Fault. To me it sounds good, and I'd be in favour of changing it. |
Revision as of 13:05, 10 March 2006
An Application 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.
- Discussion: (Miroslav) We might want to look for another term to refer to this type of an error, since this error is not encountered at the business layer, and the word "application" is somehow misleading.
- Paul is suggesting Message Infrastructure Fault. To me it sounds good, and I'd be in favour of changing it.
Back to the Open_ATS_Issues
