Difference between revisions of "ConCall-20070410"

From HL7 TSC
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
T3F - Transitional Technical Task Force
 
T3F - Transitional Technical Task Force
 
Conference Call is scheduled for 1.0 hour
 
  
 
Tuesday Apr 10, 2007 12:00 PM (US Eastern Time, GMT -5)
 
Tuesday Apr 10, 2007 12:00 PM (US Eastern Time, GMT -5)
  
Please consult [http://www.timeanddate.com/worldclock http://www.timeanddate.com/worldclock] for your local times
+
=Present=
 +
Beeler, Buitendijk, Hamill, Lorenzi, McCay
  
'''Telephone conference''' Information - HL7 Conference Service
+
=Minutes & Agenda=
:Phone Number: 973-582-2813
+
Approved the Agenda and the Minutes from April 03, 2007
:Participant Passcode: 124466
+
=Status of tasks for Cologne Deliverable (see [[ConCall-20070327|3/27 Minutes]])=
 
+
We discussed briefly the deliverables set out two weeks ago for the "Cologne Deliverable," as:
'''Online Meeting''' service - GoToMeeting
+
#*Beeler - [[T3F Cologne Deliverable|TD organization documentation]]
:[https://www.gotomeeting.com/join/791835615 https://www.gotomeeting.com/join/791835615]
 
:GoToMeeting ID: 791-835-615
 
=Expected=  
 
Beeler, Blobel, Buitendijk, Case, McCay, Lorenzi, Parker
 
=Homework=
 
=Preliminary Agenda=
 
#''(05 min)'' Roll Call & Accept agenda
 
#''(30 min)'' Status of tasks for Cologne Deliverable (see [[ConCall-20070327|3/27 Minutes]])
 
#*Beeler - TD organization documentation
 
 
#*McCay - Advancing "Success Criteria" statement
 
#*McCay - Advancing "Success Criteria" statement
 
#*Lorenzi - Responsibilities for TD
 
#*Lorenzi - Responsibilities for TD
 
#*Case - Decision making Practices
 
#*Case - Decision making Practices
#*Parker - Time0lane (tactical plan for establishing TD)  
+
#*Parker - Time-line (tactical plan for establishing TD)  
#''(15 min)'' Other business
+
 
 +
We reviewed (and modified) the preliminary outline for the "[[T3F Cologne Deliverable]]".  We agreed to maintain this on the Wiki, using the assigned responsibilities as included in the outline.  We adopted a goal of having edited material for people (ourselves) to review and have it available by midnight Sunday.  This will allow us to review it on the call of 4/17, with a view to finalizing it 4/24 for Cologne.
 +
 
 +
=Architecture Project=
 +
We discussed the task of defining an "Architecture" for HL7.  We agreed that definition and maintenance of an Architecture should be discussed in the ''"Success Criteria", "Responsibilities" and "Relationships"'' sections of the deliverable document.  We also agreed that the Architecture effort that has been started should continue to progress in Cologne.
 +
 
 +
In discussion, it was noted that Architecture defines the common elements among our efforts, their relationships to each other and the relationships to other specification architectures.  Answers to questions of ''"When I do use what technology?"'' or ''"How do I do SOA within HL7?"'' should be based on the Architecture, but not embodied in it.
 +
 
 +
We propose that the Architecture should be a Project that is defined and managed by the T3F, where the project participants include both T3F members and others.  The goal should be to have a defined Architecture draft at about the same time that the TD is established (September WGM). At that point, the project becomes a TD project, that will proceed to seek formal adoption of the Architecture as an "HL7 Informative Document."  To that end, a project proposal should be drafted for review in Cologne. (Bernd Blobel)
  
=[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]=
+
==Adjourned at 1:30 pm==
=[[T3F Action item list|Click for T3F Action Item List]]=
 

Latest revision as of 17:43, 10 April 2007

T3F - Transitional Technical Task Force

Tuesday Apr 10, 2007 12:00 PM (US Eastern Time, GMT -5)

Present

Beeler, Buitendijk, Hamill, Lorenzi, McCay

Minutes & Agenda

Approved the Agenda and the Minutes from April 03, 2007

Status of tasks for Cologne Deliverable (see 3/27 Minutes)

We discussed briefly the deliverables set out two weeks ago for the "Cologne Deliverable," as:

    • Beeler - TD organization documentation
    • McCay - Advancing "Success Criteria" statement
    • Lorenzi - Responsibilities for TD
    • Case - Decision making Practices
    • Parker - Time-line (tactical plan for establishing TD)

We reviewed (and modified) the preliminary outline for the "T3F Cologne Deliverable". We agreed to maintain this on the Wiki, using the assigned responsibilities as included in the outline. We adopted a goal of having edited material for people (ourselves) to review and have it available by midnight Sunday. This will allow us to review it on the call of 4/17, with a view to finalizing it 4/24 for Cologne.

Architecture Project

We discussed the task of defining an "Architecture" for HL7. We agreed that definition and maintenance of an Architecture should be discussed in the "Success Criteria", "Responsibilities" and "Relationships" sections of the deliverable document. We also agreed that the Architecture effort that has been started should continue to progress in Cologne.

In discussion, it was noted that Architecture defines the common elements among our efforts, their relationships to each other and the relationships to other specification architectures. Answers to questions of "When I do use what technology?" or "How do I do SOA within HL7?" should be based on the Architecture, but not embodied in it.

We propose that the Architecture should be a Project that is defined and managed by the T3F, where the project participants include both T3F members and others. The goal should be to have a defined Architecture draft at about the same time that the TD is established (September WGM). At that point, the project becomes a TD project, that will proceed to seek formal adoption of the Architecture as an "HL7 Informative Document." To that end, a project proposal should be drafted for review in Cologne. (Bernd Blobel)

Adjourned at 1:30 pm