Difference between revisions of "2013-04-04 Activities SDO Call"

From HL7 TSC
Jump to navigation Jump to search
(Created page with '__NOTOC__ ==TSC: HL7 Activities with Other SDOs == ===Meeting Info/Attendees=== Category:2013 TSC Minutes {|border="1" cellpadding="2" cellspacing="0" | width="0%" cols…')
 
 
Line 28: Line 28:
 
|  || Keith Boone ||IHE
 
|  || Keith Boone ||IHE
 
|-
 
|-
| || Christian Hay||GS1
+
| X || Christian Hay||GS1
 
|-
 
|-
| ||Austin Kreisler||HL7 TSC Chair
+
| X ||Austin Kreisler||HL7 TSC Chair
 
|-
 
|-
 
| regrets||Lynn Laakso ||HL7 staff support  
 
| regrets||Lynn Laakso ||HL7 staff support  
Line 36: Line 36:
 
| ||John Quinn ||CTO
 
| ||John Quinn ||CTO
 
|-
 
|-
| ||John Roberts  ||TN
+
| X ||John Roberts  ||TN
 
|-
 
|-
| ||Scott Robertson  || ORC
+
| X ||Scott Robertson  || ORC
 
|-
 
|-
 
| ||Ken Rubin ||HP, OMG, SOA
 
| ||Ken Rubin ||HP, OMG, SOA
Line 45: Line 45:
 
|-
 
|-
 
| ||Sandy Stuart||KP
 
| ||Sandy Stuart||KP
 
+
|-
 +
| regrets||Rita Scichilone||AHIMA
 
|-
 
|-
 
|colspan="3" style="background:#f0f0f0;"|
 
|colspan="3" style="background:#f0f0f0;"|
Line 66: Line 67:
 
===Minutes===
 
===Minutes===
 
'''Minutes/Conclusions Reached:'''<br/>
 
'''Minutes/Conclusions Reached:'''<br/>
#Agenda review and approval - Austin Kreisler
+
#Austin reviewed the draft message for soliciting participants put together by Ken & Scott. The only recommended change is to highlight the request for panel participants section of the email.
#Agenda planning for Atlanta
+
#Austin will work with HL7 staff to get the email distributed to multiple email lists over the next few days. It will probably go out early next week
 +
# The next call will be 4/18 followed by a call on 4/25.
 +
 
 +
===Draft Email Text===
 +
Subject:  HL7 May Working Group Meeting, Sun Q4 Invitation
 +
 
 +
HL7 Members:
 +
 
 +
An Invitation:  You are invited to participate in a community forum on “Q4” Sunday, May 5, where we will be discussing “Improving HL7 Communications:  What can we learn from other organizations.”    HL7 communication is a particularly challenging area.  Given the vast number of workgroups that we have, and the multitude of activities, keeping the membership and the public informed without drowning people in detail is a serious challenge.  Add to that the multinational representation of HL7 and the activities that are happening within our Affiliates, and the challenge is compounded.
 +
 
 +
Why Have this Session?  Communication challenges are not unique to HL7, and we believe that this is a perfect opportunity to learn from the HL7 community some best-practices, techniques, or approaches that have proven themselves to be useful in other settings.  The hope is that some of those “gems” will be a nice fit for HL7, and could help us improve our communications strategy and activities.
 +
 
 +
What about the Cross-SDO Session?  As many of you may be aware, this timeslot has been used in the past for “cross-SDO” discussion.  This topic is an extension of that agenda, bringing to bear NOT ONLY experiences from other SDO’s but from any other organization that has done well with effective communication strategies.
 +
 
 +
Can I participate?  We are seeking individuals whom have an interest in this subject, experiences to share, and willing to participate on a panel.  Ideally, participants will be people whom engage in multiple different communities (not necessarily HIT communities) with examples that have worked (or have not worked), and whom can relate those experiences to HL7.  You do not need to be a formal representative from another organization.  To put your name forward for the panel, send an email to emailaddress@domainname.suffix
 +
 
 +
Further, while the panel will serve as a backdrop to get discussion going, this is intended to be a community engagement discussion.  All attendees will be able to contribute.
 +
 
 +
So what comes out of this?  Our aim is to identify a “short list” of ideas that we believe might positively affect communications in HL7.  Achieving a consensus position within an hour or so may not be possible. The goal is to narrow the universe of ideas into a short list of strong contenders.  With this actionable list, we have the potential to improve communications for the whole of HL7.
 +
 
  
 
   
 
   

Latest revision as of 17:34, 4 April 2013

TSC: HL7 Activities with Other SDOs

Meeting Info/Attendees

HL7 Activities with Other SDOs

Location: call 770-657-9270 using code 985371#

Date: 2013-04-04
Time: 1 PM U.S. Eastern Daylight Time
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso


Attendee Name Affiliation
Keith Boone IHE
X Christian Hay GS1
X Austin Kreisler HL7 TSC Chair
regrets Lynn Laakso HL7 staff support
John Quinn CTO
X John Roberts TN
X Scott Robertson ORC
Ken Rubin HP, OMG, SOA
Lisa Spellman ISO TC/215 US TAG
Sandy Stuart KP
regrets Rita Scichilone AHIMA


Quorum Requirements Met: n/a

Agenda

Agenda Topics

  1. Agenda review and approval - Austin Kreisler
  2. Agenda planning for Atlanta
    • Panel topic: dialogue on communication strategy and areas of improvement.
    • Panel composition review - review Scott and Ken's draft message to solicit participants

Minutes

Minutes/Conclusions Reached:

  1. Austin reviewed the draft message for soliciting participants put together by Ken & Scott. The only recommended change is to highlight the request for panel participants section of the email.
  2. Austin will work with HL7 staff to get the email distributed to multiple email lists over the next few days. It will probably go out early next week
  3. The next call will be 4/18 followed by a call on 4/25.

Draft Email Text

Subject: HL7 May Working Group Meeting, Sun Q4 Invitation

HL7 Members:

An Invitation: You are invited to participate in a community forum on “Q4” Sunday, May 5, where we will be discussing “Improving HL7 Communications: What can we learn from other organizations.” HL7 communication is a particularly challenging area. Given the vast number of workgroups that we have, and the multitude of activities, keeping the membership and the public informed without drowning people in detail is a serious challenge. Add to that the multinational representation of HL7 and the activities that are happening within our Affiliates, and the challenge is compounded.

Why Have this Session? Communication challenges are not unique to HL7, and we believe that this is a perfect opportunity to learn from the HL7 community some best-practices, techniques, or approaches that have proven themselves to be useful in other settings. The hope is that some of those “gems” will be a nice fit for HL7, and could help us improve our communications strategy and activities.

What about the Cross-SDO Session? As many of you may be aware, this timeslot has been used in the past for “cross-SDO” discussion. This topic is an extension of that agenda, bringing to bear NOT ONLY experiences from other SDO’s but from any other organization that has done well with effective communication strategies.

Can I participate? We are seeking individuals whom have an interest in this subject, experiences to share, and willing to participate on a panel. Ideally, participants will be people whom engage in multiple different communities (not necessarily HIT communities) with examples that have worked (or have not worked), and whom can relate those experiences to HL7. You do not need to be a formal representative from another organization. To put your name forward for the panel, send an email to emailaddress@domainname.suffix

Further, while the panel will serve as a backdrop to get discussion going, this is intended to be a community engagement discussion. All attendees will be able to contribute.

So what comes out of this? Our aim is to identify a “short list” of ideas that we believe might positively affect communications in HL7. Achieving a consensus position within an hour or so may not be possible. The goal is to narrow the universe of ideas into a short list of strong contenders. With this actionable list, we have the potential to improve communications for the whole of HL7.



Next Steps

Actions (Include Owner, Action Item, and due date)
Next Meeting/Preliminary Agenda Items