FTSD-ConCalls-20080930

Foundation and Technology Steering Division Conference Call

FTSD - Foundation & Technology Steering Division

Attendees

(expected)

• Implementable Technology Specifications (ITS)
• Implementation/Conformance
  • Jason Rock
• Infrastructure & Messaging (InM)
  • Tony Julian
• RIM-Based Application Architecture (RIMBAA)
• Modeling & Methodology (MnM)
  • Ioana Singureanu
  • Woody Beeler
• Security
  • Glenn Marshall
• Service Oriented Architecture (SOA)
  • Ken Rubin
• Templates
• Vocabulary
  • Beverly Knight

Agenda

1. (05 min) Roll Call
2. (05 min) Approve previous meeting minutes Workgroup Meeting: September 15th 2008 Woody/Beverly 5-0-1, Approve Agenda: 6-0-1
3. (5 min) RIM or BRIDG,

Charlie Mead indicated in an RCRIM meeting that semantic interoperability is based on the BRIDG. The implication is that the RIM cannot provide semantic interoperability. A domain analysis cannot be used for interoperability. RCRIM has a motion to "all messages before going to DSTU have to be harmonized to BRIDG - for RCRIM". The BRIDGE may be maintained as new requirements are developed, if necessary. Individual members of the RCRIM are not in agreement with the RCRIM drafted motion to mandate the use of BRIDG and harmonize.

1. (5 min) RIM balloting: provisionally approve RIM ballot scope statement
   1. • Ioana Singureanu: When is the first ballot planned? Jan 2009. The first iteration will be completed by December 2009.
      • Chuck Meyer:ANSI Essential Requirements states that “standards developers are permitted three options – periodic maintenance, continuous maintenance or stabilized maintenance.” I am not aware of any ANSI definition of projects or project types. An SDO chooses one of the three maintenance processes to manage their standards. The maintenance type employed is not differentiated at the individual standard level. HL7 American National Standards (ANS) are currently maintained under Periodic Maintenance which requires PINS/BS8/BSR9. I have suggested on more than one occasion that HL7 notify ANSI that they are adopting Continuous Maintenance, but with little uptake even though our process matches the definition of continuous maintenance. Although standards under continuous maintenance do not require filing PINS, they do still need BSR8/BSR9. As the title suggests, Stabilized Maintenance is for standards that are mature and not likely to require revision; it extends the “reaffirm/withdraw” window from five years to ten years. I can not envision any circumstance where the RIM, or any other HL7 ANS, could be brought to normative ballot under current process without filing PINS, completing all necessary publishing requirements, and following up with a BSR8 to report the outcome of the ballot.Woody is working with HQ and will make the necessary adjustments.

Motion to approve the scope statement: Woody/Jason 5-0-1

1. (10 min) SAEAF update (Tony Julian): Tony will consolidate the comments from all of us.