Open ATS Issues

• 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) Adding the defintions of the terms used throught ATS. The aim of this section is to identify the most important ATS notions and artefacts, and word smith their defintions. Once we reach the consensus, we'll transfer them to the normative material.

• Transport (in regard to the ATS ballot reconciliation package line item 2, database record number 5)
  • Definition: "Transport is the abstract term used by the HL7 community for the infrastructure serving the HL7 messages transfer from the Sending Application Role to the Receiving Application Role. In other words, from the HL7 perspective transport refers to OSI layers 1-6. The OSI layers 1-6 are perceived by the HL7 applications as the unified interface for message transfer, meaning that a HL7 application is not required to (and usually doesn't) posses any specific knowledge for technology components residing at OSI layers 1-5."
  • Discussion:
• Message Exchange Pattern (Action Item 1026)
  • Definition
• Application Fault (in regard to the ATS ballot reconciliation package line item 49, database record number 61)
  • Definition: "Application Fault (Section 2.2.1.2) 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 any of these error types cannot be solved on the MIL layer just by retrying to send the HL7 message, and therefore further processing needs to be sent back to the business layer."
  • Discussion: (Miroslav) We might want to look for another term to refer to this type of an error, since this definitely does not reflect the errors encountered on the business layer.
• Interface Engine
• Gateway