This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "INM Pre-May WGM out-of-cycle Meeting"

From HL7Wiki
Jump to navigation Jump to search
Line 14: Line 14:
  
 
== Agenda (Draft) ==
 
== Agenda (Draft) ==
 +
 +
The agenda for Saturday Q4 and Sunday Q1/Q2 will be determined by "triaging" the open issues list at the start of the Saturday Q4 meeting.
  
 
'''Saturday 6 May'''
 
'''Saturday 6 May'''
* Q1 MCCI - overview of issues
+
* Q1 MCCI - issues
 +
**Overview: the INM co-chairs will present an overview of open MCCI issues. See [[Open Transmission Wrapper Issues]] and [[Open Control Act Issues]].
 
**Topic: [[Transmission Addressing]] (at all levels and layers)
 
**Topic: [[Transmission Addressing]] (at all levels and layers)
 
**Topic: [[Interaction Pattern]] (abstract) and [[Transmission Pattern]] ([[HL7 Messaging Architecture]]) - useful? or change definitions?
 
**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?
 
**Topic: is [[Batch]] a unit of processing (i.e. does it exist at the abstract level) or is it just a Transmission grouper?
 +
**Topic: overlapping functionality between HL7 & the transport protocol (e.g. reliability, commit ack, sequence number protocol)
 
**Topic: (after SOA discussions): create a [[HL7 Messaging Architecture]] document instead of ATS, group with MCCI in 1 ballot?
 
**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: (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: [[:Category:INM Glossary|MCCI Glossary definitions]]
 
**Topic: [[:Category:INM Glossary|MCCI Glossary definitions]]
* Q2 SOA - overview of issues (see also [[SOA versus Message Transmission]])
+
* Q2 SOA - issues
 +
**Overview: The SOA SIG will present a whitepaper with an overview of the various issues, see [[SOA versus Message Transmission]] and the [http://hssp.wikispaces.com/ HSSP and SOA SIG website].
 
**Topic: discussion of a mapping of current V3 artifacts to the SOA approach  
 
**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: 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  
 
**Topic: methodology for defining services and creating service implementations, including approaches to conformance and profiling  
* Q3 ATS - overview of issues
+
* Q3 ATS - issues
 +
**Overview: Miroslav will present an overview of open ATS issues. See [[Open ATS Issues]].
 
**Topic: [[:Category:ATS Glossary|ATS Glossary definitions]]
 
**Topic: [[:Category:ATS Glossary|ATS Glossary definitions]]
 
* Q4 Open
 
* Q4 Open
Line 33: Line 39:
  
 
'''Sunday 7 May'''
 
'''Sunday 7 May'''
* Q1 Open (Miroslav unavailable)
+
* Q1 Open  
 
** Agenda planned SAT Q4
 
** Agenda planned SAT Q4
* Q2 Open (Miroslav unavailable)
+
* Q2 Open  
 
** Agenda planned SAT Q4
 
** Agenda planned SAT Q4
 
 
 
----
 
 
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)
 

Revision as of 16:42, 10 April 2006

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. The meeting room has a 35-person capacity.

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)

The agenda for Saturday Q4 and Sunday Q1/Q2 will be determined by "triaging" the open issues list at the start of the Saturday Q4 meeting.

Saturday 6 May

  • Q1 MCCI - issues
  • Q2 SOA - issues
    • Overview: The SOA SIG will present a whitepaper with an overview of the various issues, see SOA versus Message Transmission and the HSSP and SOA SIG website.
    • 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 - issues
  • Q4 Open
    • Agenda planning Q4 and SUN Q1,Q2: Determine priorities and quarters when as-yet undiscussed topics should be discussed

Sunday 7 May

  • Q1 Open
    • Agenda planned SAT Q4
  • Q2 Open
    • Agenda planned SAT Q4