This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Fragmenting Large Transmissions"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new page) |
Rene spronk (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{INM Workitem}} | + | {{INM Finalized Workitem}} |
| − | + | {{INM Approval|20060510|The INM committee decides not to support a mechanism to fragment large messages. Any fragmentation for transmission/transport purpose should be dealt with within the Message Infrastructure Layer. The receiving HL7 Application has the option of refusing an interaction because of its size. Motion by Rene/Miroslav, 13-1-0}} | |
| − | + | HL7 does not support a generic mechanism to fragment large messages. Any fragmentation for transmission/transport purpose should be dealt with within the [[Messaging Infrastructure Layer]]. The receiving HL7 Application has the option of refusing an interaction because of its size. | |
| − | + | ||
| + | Fragmentation is present in v2 (in the form of the DSC segment, as a site negotiation option). The concept is problematic in HL7 v3: fragmentation is a post-serialization ITS specific issue. | ||
Latest revision as of 00:04, 15 September 2006
This page documents an INM Finalized Workitem, i.e. an issue within scope of the INM Committee that has been finalized, and which (if applicable) has been included in an INM ballot.
HL7 does not support a generic mechanism to fragment large messages. Any fragmentation for transmission/transport purpose should be dealt with within the Messaging Infrastructure Layer. The receiving HL7 Application has the option of refusing an interaction because of its size.
Fragmentation is present in v2 (in the form of the DSC segment, as a site negotiation option). The concept is problematic in HL7 v3: fragmentation is a post-serialization ITS specific issue.
