20130221 arb minutes

ARB - Meeting (Date in Title)

Agenda

1. Call to order
2. Roll Call
3. Approval of Agenda
4. Approval of Minutes
5. Report from Architecture Project

A.	Lifecycle Activity Diagrams – Bo and Charlie
	1.	Review Frieda’s process model and update process lifecycle diagram. – Charlie 
	2.	Create initial activity diagrams and state transition diagrams. – Charlie 
	1.	Formalize diagrams above into EA – Bo 
	3.	Update meta-model profiles, spreadsheets, and models so far to reflect i and ii. – Bo 
	4.	Create a high-level product hierarchy / taxonomy – 
		Bo and Charlie to put together very high level first draft
		1.	Product Lines
		2.	Product families
		3.	Product family sub-components
B.	Data Capture Spreadsheet – Jane, Ron & AMS
	5.	Embed definitions for the data capture tool items in the reference section 
		of the spreadsheet – Mostly done – Ron and Jane
	6.	Harmonize the lists of things in the reference section to the work done by 
		AMS in the product catalog and Ron has done for FHIR – Ron, Jane and AMS
	7.	Further segment the lists of roles / behaviors etc… by life-cycle stage 
	8.	Steps 1 and 2 need to be redone in new data collection tool – 
		Step 1 done and most of Step 2 done – Ron and Jane
C.	Update Existing BAM – TBD 
	9.	Update BAM from previous steps – Bo 
	10.	Map flattened UML to proper UML – AMS (to be confirmed)
D.	BAM New Work – Pass 1 – Fill in remaining lifecycle steps for artifacts, 
	behaviors, participants, roles, and parties – TBD 
	11.	TSC assigns responsibilities to fill out data collection tool for remaining 
		lifecycle stages for ballotable products 
	12.	ArB models the work resulting from TSC assignments
E.	BAM New Work – Pass 2 – Vitality processes and reusable patterns – TBD 
	13.	Harvest and model the reusable process patterns such as publications,
		 balloting, project scope planning
	14.	Model vitality process
	15.	Model processes for context neutral components (data types, cmets, 
		harmonization processes)
	16.	Modify BAM to reference reusable processes and patterns where appropriate
F.	BAM New Work – Pass 3 – Include on the why and values – TBD 
	17.	Add to the model and the spreadsheets constructs for the why (means and ends),
		 the value statements and the conformance criteria 
G.	BAM Instance – TBD 
	18.	Start creating exemplary instances from the BAM
UNSURE WHERE THESE GO:
•	Using TSC Risk Assessment, identify organizational and typical product Governance
	 Points and corresponding precepts, metrics, and processes 
•	Conformity assessment processes to guide current or imminent new product 
	development

1. Other business and planning
2. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes Location: Telcon		Date: 20130221 Time: 5:00pm U.S. Eastern
Facilitator	Parker, Ron	Note taker(s)	Julian, Tony
Attendee	Name	Affiliation
.	Bond,Andy	NEHTA
.	Constable, Lorraine	Constable Consulting Inc.
X	Curry, Jane	Health Information Strategies
X	Dagnall, Bo	HP Enterprise Services
.	Grieve, Grahame	Health Intersections Pty Ltd
.	Hufnagel, Steve	U.S. Department of Defense, Military Health System
X	Julian, Tony	Mayo Clinic
.	Loyd, Patrick	ICode Solutions
.	Lynch, Cecil	Accenture
.	Mead, Charlie	National Cancer Institute
X	Milosevic, Zoran	Deontik Pty Ltd
X	Parker, Ron	CA Infoway
.	Quinn, John	Health Level Seven, Inc.
.	Guests
.	Kreisler, Austin	HL7 TSC Chair
.	Luthra, Anil	NCI
.	Pech, Brian	Kaiser Permanente
X	Shakir, Abdul Malik	City of Hope National Medical Center
.
.	Legend
X	Present
.	Absent
R	Regrets
Quorum Requirements Met: Yes

Minutes

1. Call to order at 5:00pm Eastern
2. TSC BAM Modeling:
   1. Kickoff was held
3. Phase 2
   1. BO: AMS accepted assignments, but will not be done in the next 2 weeks.
   2. Ron: Item B should be done in 2 weeks.
   3. Bo: Charlie does not have the bandwidth to do his tasks(1,2,3) at this time. I will pick it up.
4. Walk though the BAM tool.
   1. Austin is wanting us to start quickly.
   2. Product definition and approval is pretty well done.
   3. Product planning is the next - there is a lot.
      1. Added reference sheet artifact entries.
      2. Bo: Are you finding step 0 and one on par with the Phoenix steps?
      3. Ron: I dont think they are that much more granular. One of the definitions of granularity "Should document steps that result in working of formal artifacts that have an identity and are persisted as siehter published works, or are required for continuity across role/activity transitions of for corporate memory."
   4. Ron:We only document nominal path as steps. Exception processes or iterative processes are not documented in the data capture tool.
   5. AMS: Might it change the state of an existing artifact?
   6. Ron: We have added revised.
   7. Walked through BAM tool
   8. Spreadsheet will be posted in GFORGE.
   9. Definitions will be on the WIKI.
   10. Ron and Jane will send the BAM tool to Tony for upload to gforge.
5. Meeting adjourned at 6:00pm Eastern

--Tony Julian 14:48, 22 February 2013 (UTC)

A.	Lifecycle Activity Diagrams – Bo and Charlie
	1.	Review Frieda’s process model and update process lifecycle diagram. – Charlie 
	2.	Create initial activity diagrams and state transition diagrams. – Charlie 
	1.	Formalize diagrams above into EA – Bo 
	3.	Update meta-model profiles, spreadsheets, and models so far to reflect i and ii. – Bo 
	4.	Create a high-level product hierarchy / taxonomy – 
		Bo and Charlie to put together very high level first draft
		1.	Product Lines
		2.	Product families
		3.	Product family sub-components
B.	Data Capture Spreadsheet – Jane, Ron & AMS
	5.	Embed definitions for the data capture tool items in the reference section 
		of the spreadsheet – Mostly done – Ron and Jane
	6.	Harmonize the lists of things in the reference section to the work done by 
		AMS in the product catalog and Ron has done for FHIR – Ron, Jane and AMS
	7.	Further segment the lists of roles / behaviors etc… by life-cycle stage 
	8.	Steps 1 and 2 need to be redone in new data collection tool – 
		Step 1 done and most of Step 2 done – Ron and Jane
C.	Update Existing BAM – TBD 
	9.	Update BAM from previous steps – Bo 
	10.	Map flattened UML to proper UML – AMS (to be confirmed)
D.	BAM New Work – Pass 1 – Fill in remaining lifecycle steps for artifacts, 
	behaviors, participants, roles, and parties – TBD 
	11.	TSC assigns responsibilities to fill out data collection tool for remaining 
		lifecycle stages for ballotable products 
	12.	ArB models the work resulting from TSC assignments
E.	BAM New Work – Pass 2 – Vitality processes and reusable patterns – TBD 
	13.	Harvest and model the reusable process patterns such as publications,
		 balloting, project scope planning
	14.	Model vitality process
	15.	Model processes for context neutral components (data types, cmets, 
		harmonization processes)
	16.	Modify BAM to reference reusable processes and patterns where appropriate
F.	BAM New Work – Pass 3 – Include on the why and values – TBD 
	17.	Add to the model and the spreadsheets constructs for the why (means and ends),
		 the value statements and the conformance criteria 
G.	BAM Instance – TBD 
	18.	Start creating exemplary instances from the BAM
UNSURE WHERE THESE GO:
•	Using TSC Risk Assessment, identify organizational and typical product Governance
	 Points and corresponding precepts, metrics, and processes 
•	Conformity assessment processes to guide current or imminent new product 
	development

1. Meeting adjourned at 6:00pm Eastern