2014-05-04 TSC WGM Minutes

TSC Sunday meeting for 2014May WGM

back to TSC Minutes and Agendas

TSC WGM Agenda/Minutes

HL7 TSC Meeting Minutes Location: Sonora		Date: 2014-05-04 Time: 5:15PM
Facilitator: Ken McCaslin		Note taker(s): Lynn Laakso
Attendee	Name	Affiliation
x	Calvin Beebe	HL7 SSD SD Co-Chair
x	Woody Beeler	HL7 FTSD Co-Chair
regrets	Giorgio Cangioli	HL7 Affiliate Representative
regrets	Lorraine Constable	HL7 ArB Vice Chair
x	Jean Duteau	HL7 Affiliate Representative
x	Katherine Duteau	observer
x	Grahame Grieve	FGB member
x	Freida Hall	HL7 TSS SD Co-Chair
x	David Hay	FMG co-chair
x	Stan Huff	HL7 Board Chair (member ex officio w/ vote)
	Chuck Jaffe	HL7 CEO (member ex officio w/o vote)
x	Tony Julian	HL7 ARB Chair
x	Paul Knapp	HL7 FTSD Co-Chair
x	Austin Kreisler	Ad-hoc member
x	Lynn Laakso (scribe, non-voting)	HL7 HQ
x	Ken McCaslin	TSC Chair, Ad-Hoc Member
x	Lloyd McKenzie	FHIR FMG co-chair
	Don Mon	HL7 Board Vice-Chair (member ex officio w/o vote)
x	Melva Peters	HL7 DESD Co-Chair
regrets	John Quinn	HL7 CTO (TSC member ex officio w/vote)
x	John Roberts	HL7 DESD Co-chair
regrets	Andy Stechishin	HL7 T3SD Co-Chair
x	Pat Van Dyke	HL7 SSD SD Co-Chair
Quorum Requirements (Co-chair +5 with 2 SD Reps) Met: (yes/No)

Agenda Topics

1. ArB
   1. (Sept) Review and re-confirm ArB membership (even numbered years)
   2. Normative notification /approval (Project Scope Statement update) for ArB initially balloted at Project Insight 786 and TSC Tracker 3214
2. BAM
3. FHIR
4. Ballot Naming Conventions (see homework from Saturday) - Do we need to expand the names available (Freida Hall/Lorraine Constable/Tony Julian)
   1. The section in the GOM is 12.0.2.0.2.
5. (45 mins) Review Open Issues List
6. Report: congratulations to RCRIM WG on Version 3 Standard: Regulated Studies; CDISC Content to Message - Study Participation, Release 1 at Project Insight # 205 request for normative publication at TSC Tracker 3198.

Minutes/Conclusions Reached:

Ken convened at 5:18 PM

1. Agenda review: Melva noted the International Council was told the TSC would identify the next conformance profiles and the TSC should discuss further. Ken has not yet had a chance to speak to Chuck about it.
2. ArB
   1. Normative notification /approval (Project Scope Statement update) for ArB initially balloted at Project Insight 786 and TSC Tracker 3214
      • Purpose is to take the SAIF CD normative after one year's DSTU extension. This is not the same as the SAIF IG. Motion: Tony moves approval, Woody seconds. Vote: Unanimously approved.
      • Tony requests that any comments need to be posted to the DSTU comments site; they have had none so far.
3. FHIR
   • Lloyd reports on the status of the DSTU, published shortly after the last WGM. They are informing WGs of their expectations for readiness for the next DSTU ballot planned for 2015Jan cycle. It includes a set of quality criteria for existing and new resources and profiles. Profiles in development as well as proposed profiles to support CCDA will be coming.
   • Calvin note that CCDA was a funded project taking consultants a couple years to complete. Does he anticipate such funding for this effort? Lloyd notes that they have done the work in the CCDA and so the constraints are already identified. Comments from WGs are welcome to the next release of CCDA but the constraints will be developed in FHIR exactly from the CCDA release. This is a technical exercise.
   • Calvin further asks about interest in a profile on just CDA as a first step before taking on the largest profile with consistency to be maintained between the two going forward? Class level changes are not going to be part of CDA R2.1 or R3 but vocabulary bindings. They will be sufficiently distinct. They will not be creating transforms either uni- or bi-directionally Lloyd asserts. There is some work to create transforms but not part of this effort. What is the use case for doing it then? It allows CDA folks to understand how FHIR is applied.
   • Lloyd next comments on the connectathon - 50 people with 5 or 6 observers some of whom became developers during the session. There was enthusiasm over how valuable it is. Most of the connectathon participants are staying on with the WGM and some are interested in engaging as developers. They had good feedback for next time as well notes David.
   • Lloyd would like to see some education up front to ramp up before the connectathon begins. This may be a webinar or perhaps move into offerings on Friday (needs more discussion and planning into the future).
   • Austin asks about Structured Data Capture project with SDWG. Lloyd makes disclosure that he is a paid consultant on the project. What is the plan with the PSS and which WG will sponsor it? CDE (Common Data Elements) are also of interest with CDC in addition to ONC. Austin notes that they are asserting they intend to ballot this next cycle but FHIR won't go back to ballot until January. Lloyd notes it will be a comment-only ballot to include a snapshot of FHIR development environment and profiles applied to that version. Lloyd is meeting with Doug Fridsma on Tuesday to discuss ballot timelines.
   • They will talk to WGs this week for endorsement and have already discussed with US Realm Task Force.
   • Woody notes that Ed Hammond is taking over stewardship of the US Realm Task Force and recommends Lloyd discuss with him.

     Paul joins.

4. BAM
   • Tony provides status:
   • BAM 2b is a 12 step project with steps 0 through 11. They have only accomplished steps 0 and 1. Modeling is done and 6 of 8 chapters in document should be finished this week.
     The rest of the steps are at the discretion of the TSC.

     HL7 Business Architecture Model(2b):

     A 12 step project.

     • 0.product Line definition
     • 1.Product-Line Adoption Planning
     • 2.Product Line Inventory
     • 3.CONCEPTUAL LEVEL Requirements
     • 4.Logical level artifact definition
     • 5.Logical level bindings
     • 6.Implementation Guide development
     • 7.Balloting Publication and Balloting
     • 8.DSTU Testing
     • 9.External publication of Specifications
     • 10.Education and Marketing
     • 11.Artifact Versioning and Retirement (primarily controlled by ANSI et al).

     Steps 0 and 1 involve Product/product Families Management, Governance, and methodology, and will be presented as BAM 'lite'.

     Modelling is done, and 6 of the eight chapters of the document are done.

     Chapters 7 and 8 should be finished this week to be shared with the TSC.

   • ARB will flesh out the rest if there is direction from the TSC to do so.
   • ARB is having membership trouble with various members losing support from their employers and if anyone is interested please let them know.
   • ACTION ITEM: Add BAM review to the next TSC call (in June)
   • Need sort of job description and responsibilities needed now. Tony suggests they may address that Thursday Q4.
5. Ballot Naming Conventions (see homework from Saturday) - Do we need to expand the names available (Freida Hall/Lorraine Constable/Tony Julian)
   1. The section in the GOM is 12.0.2.0.2.
   2. This was referred to Andy to take up with publishing
6. (45 mins) Review Open Issues List
   • Define list of machine-processable artifacts for membership benefit TSC Tracker 2585
     • Suggestion to close tracker - This was presented to the Board. to be closed. Board put it on the back burner for consideration as member benefit.
     • Latest release of MWB put in members-only section as it is currently the 'use at your own risk' status. This has renewed discussion on the topic.
     • We don't really know what the status is. Ken will ask the Board what their intention is with the list; Tracker reassigned.
     • Stan confirms there is still interest in making this a member benefit.
     • Grahame joins
   • TSC Definition of Domain Analysis Models and Functional Profiles TSC Tracker 2165
     • DAM definition is balloted and undergoing reconciliation.
     • EHR provided a definition of a Profile in the tracker. This was intended to cover all profiles not just EHR Functional Profile. This may have been one of the 19 artifact definitions. Sample template for profile definition on wiki only a shell. Assign to Pat and Tony to work with ArB.
     • Freida notes that they had an action item to define 'implementation guide' and 'conformance' from the 2013Sep WGM. She emailed a document today, but defer discussion to the first meeting in June.
       • Final Definitions
         • Implementation Guide

           An implementation guide is often created to organize a collection of conformance profiles, functional requirement specifications, or templates for specifying a set of related interactions described in a use case or use cases. Implementation guides typically describe broader conformance requirements such as application behaviour. Such requirements may include how a set of interactions (messages, documents, etc.) are to be used to enact certain application functionality among applications (actors).

         • Conformance

           Conformance is defined as the fulfilment of a product, process, or service of specified requirements [ISO-17000, OASIS]. The concept of conformance is essential to any standard for providing an objective measure of how closely implementations satisfy the requirements defined in the standard.

     • JohnR notes they had an action item to define relationship between help desk and WG cochairs. This is not ready yet. It will not be ready until after June.
     • TSC review of projects >5 years old: TSC Tracker 2788 Ken suggests pulling these out and sending it to the Steering Divisions for review. SD should review with the WGs.
     • The list is better than it was last year; and shows improvement.
     • Line 4 Woody notes a whoopsy with schematron needed correction and will be in this NE and future ballot. Calvin asks if the change needed to be made in CDA. If CDA is a separate distribution it needs to be made separately. SDWG will discuss on their agenda Tuesday afternoon.
       • Lynn will extract by Steering Division for review by SD cochairs with their WGs.
7. Ken reports the IP issue is still not fully resolved and he describes what he will report at the cochairs meeting. Woody suggests he recommend to the cochairs they not share final versions of the standards prior to publication on any public site, but otherwise there are no changes to what they currently do until clear guidance is available.
8. Report: congratulations to RCRIM WG on Version 3 Standard: Regulated Studies; CDISC Content to Message - Study Participation, Release 1 at Project Insight # 205 request for normative publication at TSC Tracker 3198.

Adjourned 6:15 PM

Actions (Include Owner, Action Item, and due date) Melva noted the International Council was told the TSC would identify the next conformance profiles and the TSC should discuss further. Ken has not yet had a chance to speak to Chuck about it. Add BAM review to the next TSC call (in June) ARB needs some sort of job description and responsibilities for seeking additional participants Add review of definition of 'implementation guide' and 'conformance' to the first meeting in June Add review of action item to define relationship between help desk and WG cochairs to agenda in June Lynn will extract the 5 year old projects by Steering Division for review by SD cochairs with their WGs.

Next Meeting/Preliminary Agenda Items .

© 2014 Health Level Seven® International. All rights reserved.