Difference between revisions of "Transmission Wrapper (new wrapper mechanism)"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 4: | Line 4: | ||
The scope of the Transmission Wrapper is limited to data which (in essence) is relevant for the [[MIL]]. Data processed by the [[Receiver|receiving application]] instead of by the [[MIL]] does '''not''' belong in the Transmission Wrapper. In advanced [[MIL]]s (e.g. Webservices, ebMS) the data as contained in the Transmission Wrapper have a direct equivalent in the form of [[MIL]]-specific transport headers. | The scope of the Transmission Wrapper is limited to data which (in essence) is relevant for the [[MIL]]. Data processed by the [[Receiver|receiving application]] instead of by the [[MIL]] does '''not''' belong in the Transmission Wrapper. In advanced [[MIL]]s (e.g. Webservices, ebMS) the data as contained in the Transmission Wrapper have a direct equivalent in the form of [[MIL]]-specific transport headers. | ||
| + | |||
| + | *Open issue: information related to [[Transmission SLA]] | ||
Revision as of 15:52, 5 October 2006
This page documents an INM Workitem, i.e. an issue within scope of the INM Committee that either is still being discussed, or the resolution of which has not yet been included in an INM ballot.
A Transmission Wrapper includes information needed by a sending HL7 Application to package and route the V3 interaction to the HL7 Application which is the designated Receiver. All HL7 Version 3 Interactions have an appropriately configured HL7 Transmission wrapper.
The scope of the Transmission Wrapper is limited to data which (in essence) is relevant for the MIL. Data processed by the receiving application instead of by the MIL does not belong in the Transmission Wrapper. In advanced MILs (e.g. Webservices, ebMS) the data as contained in the Transmission Wrapper have a direct equivalent in the form of MIL-specific transport headers.
- Open issue: information related to Transmission SLA
