Difference between revisions of "Open ATS Issues"
Rene spronk (talk | contribs) |
|||
| Line 8: | Line 8: | ||
---- | ---- | ||
| − | (Miroslav) | + | (Miroslav) The items and concepts that are listed below represent some of the major challenges for the ATS document. They are addressed in many Action Items with the InM as well. We list them here for information only - the official proposals are contained with the new version of ATS document that is up for the January 2007 ballot cycle (ATS C1 R2). Please post your balloot votes to that document. |
*'''[[Transport]]''' (in regard to the ATS ballot reconciliation package line item 2) | *'''[[Transport]]''' (in regard to the ATS ballot reconciliation package line item 2) | ||
Revision as of 10:00, 27 November 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.
- Translations: add "derived from .. ID" attribute ?, much like acknowledgementOf. See also MCCI line-item 157.
- Message.id "sameness" discussion after transformation by a Gateway.
- New motion of MnM: 20060113: "At the semantic (or: business process level) the contents of the Transmission wrapper, with the exception of InteractionID, are not relevant when determining if 2 interactions are the same. At the transmission-level 2 Transmissions are the same if they have the same Transmission.id."
- This has the consequence that the sameness of Transmission.id is not linked to the wider topic of semantic-transmission sameness.
- Use of the AttentionLine class to add route-tracing information in a Transmission that's being routed/gatewayed to its destination. Are Gateways/Bridges able to add their own information to the Transmission Wrapper in the form of an additional AttentionLine?
(Miroslav) The items and concepts that are listed below represent some of the major challenges for the ATS document. They are addressed in many Action Items with the InM as well. We list them here for information only - the official proposals are contained with the new version of ATS document that is up for the January 2007 ballot cycle (ATS C1 R2). Please post your balloot votes to that document.
- Transport (in regard to the ATS ballot reconciliation package line item 2)
- Message Exchange Pattern (Action Item 1026)
- Message Infrastructure Fault (in regard to the ATS ballot reconciliation package line item 49, related to Application Fault)
- Gateway, Bridge, Interface Engine, Transformer Bridge, Message Broker (in regard to the ATS ballot reconciliation package line items 53-57)
- HL7 Application
- Source, Destination (unified glossary definition from both ATS as well as webservices perspective)
Miroslav Koncar 08:00, 21 Apr 2006 (CDT) The most recent developments have resulted in the new HL7 Messaging Architecture that is to be discussed at the Out of Cycle Meeting. Plese refer to the separate page HL7 Messaging Architecture for details.
