Difference between revisions of "2014-06-23 TSC Call Agenda"
Jump to navigation
Jump to search
Line 89: | Line 89: | ||
#**See [http://www.hl7.org/documentcenter/public/wg/projectServices/PBSMetricGuidanceforSDCoChairsFinal.doc PBS Metrics Guidance for SD Co-Chairs] | #**See [http://www.hl7.org/documentcenter/public/wg/projectServices/PBSMetricGuidanceforSDCoChairsFinal.doc PBS Metrics Guidance for SD Co-Chairs] | ||
#Reports: (attach written reports below from Steering Divisions et al.) | #Reports: (attach written reports below from Steering Divisions et al.) | ||
+ | #*TRAC: | ||
+ | #** Would measurements from before and after the changed process to disallow a single check box to enroll in all of the ballots be meaningful for ballot quality assessment? | ||
+ | #**TRAC report/recommendation on governance metric for project scope statements submitted late for deadline<!-- leave as 'vitality trigger'--> | ||
<!-- #WGM Planning - --> | <!-- #WGM Planning - --> | ||
#[http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 Open Issues List] | #[http://gforge.hl7.org/gf/project/tsc/tracker/?action=TrackerItemBrowse&tracker_id=313 Open Issues List] |
Revision as of 14:05, 20 June 2014
TSC Agenda/Minutes
Meeting Info/Attendees
Standing Conference Calls
TSC will hold a Conference Call at 11AM Eastern time, each Monday except during scheduled face-to-face Working Group Meetings unless otherwise noted at TSC_Minutes_and_Agendas.
- GoToMeeting at https://global.gotomeeting.com/join/426505829 using VOIP
- For those without access to microphone/speakers:
- US: +1 (224)501-3318
- Canada: +1 (647)497-9379
- Italy: +39 0 230 57 81 80
- Access Code: 426-505-829
- GoToMeeting ID: 426-505-829
HL7 TSC Meeting Minutes Location: call 770-657-9270 using code 985371# |
Date: 2014-06-23 Time: 11:00 AM U.S. Eastern | |
Facilitator: Ken McCaslin | Note taker(s): Dave Hamill |
Quorum = chair + 5 including 2 SD represented | yes/no | ||||||
Chair/CTO | ArB | International Affiliate Rep | Ad-Hoc | ||||
. | Ken McCaslin | . | Tony Julian | . | Jean Duteau | . | Austin Kreisler |
. | John Quinn | . | Lorraine Constable | . | Giorgio Cangioli | . | |
Domain Experts | Foundation and Technology | Structure and Semantic Design | Technical and Support Services | ||||
. | Melva Peters | . | Woody Beeler | . | Calvin Beebe | . | Freida Hall |
. | John Roberts | . | Paul Knapp | . | Pat van Dyke | . | Andy Stechishin |
ex officio | Invited Guests | Observers | HL7 Staff | ||||
. | Stan Huff (HL7 Chair) w/vote | . | . | obs1 | regrets | Lynn Laakso | |
. | Don Mon (Vice Chair) |
. | . | . | obs2 | . | Dave Hamill |
. | Chuck Jaffe (CEO) |
. | . | . | . | ||
Agenda
Housekeeping
- Introduction of visitors (including declaration of interests)
- Agenda review and approval -
- Approve Minutes of 2014-06-16 TSC Call Agenda
Governance
- Approval items:
- Discussion topics:
Management
- Review action items –
- Paul will edit and bring back updates to our naming conventions and DSTU release guidance.
- 2585 Define list of machine-processable artifacts for membership benefit - Ken will follow up with Stan on who is the Marketing committee chair and the Board's intent with the list
- Woody will craft a motion for the TSC position statement on new projects using R2B
- Approval items:
- Project Approval (update) request of Harmonization of Health Quality Information Models for CQI WG of DESD at Project Insight # 1045 and TSC Tracker #3027
- Discussion topics:
- Status of problem identification and response between HL7 and GS1 (P. Knapp)
- J. Quinn suggests: 1 week: flag as yellow; 2 weeks: flag as red
- Review of definition of 'implementation guide' and 'conformance'
- 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 behavior. 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 fulfillment 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.
- Implementation Guide
- Final Definitions
- WG Health – Impact on SD project approval
- Status of problem identification and response between HL7 and GS1 (P. Knapp)
- Reports: (attach written reports below from Steering Divisions et al.)
- TRAC:
- Would measurements from before and after the changed process to disallow a single check box to enroll in all of the ballots be meaningful for ballot quality assessment?
- TRAC report/recommendation on governance metric for project scope statements submitted late for deadline
- TRAC:
- Open Issues List
Minutes
Minutes/Conclusions Reached:
Please don't forget to hang up from the conference call (VOIP users)
Next Steps
Actions (Include Owner, Action Item, and due date)
| |||
Next Meeting/Preliminary Agenda Items |
© 2014 Health Level Seven® International. All rights reserved.