INM Pre-May WGM out-of-cycle Meeting

INM will hold an out-of-cycle meeting (the board has approved it) related to Transmission and Transports in San Antonio immediately prior to the WGM.

Dates: Saturday May 6 Q1-Q4, and Sunday May 7 Q1 & Q2. Location: The WGM conference hotel.

Topics

Our intent is to do mini-harmonization for the Transmission and Transport domains, and in addition, to find solutions for some of the festering issues that exist in the overlapping areas between these areas. These issues are long running issuesthat do not fit well into the ballot process, and we have been struggling to find time or a process to give them any substantial consideration.

There is a large number of outstanding issues. Generally,there is a scope question relating the concept of interactions, transmissions, transports, how they inter-relate with each other, and how the historical HL7 approach relates to approaches taken in other industries or by other standards bodies (note that we use these other standards for actual transport).

See below for an agenda; also see the list of confirmed attendees.

Agenda (Draft)

Saturday 6 May

• Q1 Meeting Overview
  • Topic: Transmission Addressing (at all levels and layers)
  • Topic: Interaction Pattern (abstract) and Transmission Pattern (HL7 Messaging Architecture) - useful? or change definitions?
  • Topic: is Batch a unit of processing (i.e. does it exist at the abstract level) or is it just a Transmission grouper?
• Q2 SOA, see SOA versus Message Transmission
  • Topic: discussion of a mapping of current V3 artifacts to the SOA approach
  • Topic: discussion of v3 Artefacts that should be left to other protocol and technology standards and any constraints that should be imposed on those elements (probably in the form of requirements)
  • Topic: methodology for defining services and creating service implementations, including approaches to conformance and profiling
• Q3 ATS
  • Topic: ATS Glossary definitions
• Q4 MCCI-ATS
  • Topic: (after SOA discussions): create a HL7 Messaging Architecture document instead of ATS, group with MCCI in 1 ballot?
  • Topic: (after SOA discussions) It has been suggested by proponents of SOA architectures that the current Transmission Wrapper contains classes and attributes which are not related to Transmission. Where should these be moved to?
  • Topic: MCCI Glossary definitions
• Evening (not part of the "official" agenda)

Sunday 7 May

• Q1 Meeting Overview
  • Note: Miroslav unavailable
• Q2 xx
  • Note: Miroslav unavailable

• Q3 xx (not part of the "official" agenda)
  • Note: Miroslav unavailable
• Q4 x (not part of the "official" agenda)
  • Note: Miroslav unavailable

---

Specifically, there is a long list of issues on our plate. For further details, our open issue lists on which would base some of our agenda can be found on the wiki:

• Open ATS Issues, Open Transmission Wrapper Issues, Open Control Act Issues
• Other then the open issues on the wiki, there is also these issues:
  • relation of the Abstract Transport Specification to SOA message delivery patterns, see SOA versus Message Transmission
  • SOA vs Webservices & ebXML, overlapping functionality between HL7 & the transport protocol (reliability, commit ack, sequence number protocol)