2023-08-16 Meeting notes

Date

Aug 16, 2023

Attendees

Name

Organization

Role

 Present?

Name

Organization

Role

 Present?

 Andrea Pitkus

 University of Wisconsin-Madison

 Steering Committee member

 Yes

 Eric Crugnale

 Sonic Healthcare

 Steering Committee member

 Yes

Nanguneri Nirmala

 Tufts Medical Center

Steering Committee member

Yes

Mehdi Nassiri

Indiana University

Steering Committee member

Yes

Aaron Green

Labnostic

Steering Committee member

Yes

Agenda

  • Workgroup Leadership

    • All chosen Workgroup leaders are to be Co-Chairs (as per Shield Community Charter).  At least one selected leader must be a Steering Committee member.

  • ·Review/Develop Workgroup Charge

    • Workgroup charges shall include the Workgroup's purpose, leadership, objectives, scope, deliverables, timeline, and proposed Member participation.

    • Initial purpose for discussion drafted by Eric: The Branding and Communication Workgroup is responsible for communicating information, recommendations, accomplishments and other work product of the SHIELD Community.  The Workgroup will strive to deliver these communications in a consistent, effective and professional manner through various communication channels including, web, email, industry publications, industry conferences, webinars, white papers and other means as required.   

  • Meeting cadence and schedule

Discussion topics

Catalog/inventory of current content/assets

  • Mehdi Nassiri’s article: https://www.mlo-online.com/information-technology/lis/article/21253050/how-far-and-how-well-will-your-data-travel. Medhi is willing to write this up as a paper supporting the activities of SHIELD.

  • Other recent publications that are relevant:

    • Interoperability in Genomics Paper: Carter AB, Abruzzo LV, Woolworth Hirschhorn J, Jones D, Jordan DC, Nassiri M, Ogino S, Patel NR, Suciu C, Temple-Smolkin RL, Zehir A, Roy S. Electronic Health Records and Genomics –There’s Still a Lot of Work to Do: Perspectives from the Association for Molecular Pathology Electronic Health Record (EHR) Interoperability for Clinical Genomics Data Working Group. Journal of Molecular Diagnostics. 2022 Jan;24(1):1-17. doi: 10.1016/j.jmoldx.2021.09.009. PMID: 34656760.

  • The workgroup spent most of the meeting discussing the purpose of the workgroup. As per the SHIELD Charter, workgroups must establish a “charge” which includes their purpose.

    • Significant discussion and questions raised as to what the purpose is:

      • The Branding and Communication Workgroup is responsible for establishing the ongoing communication strategy for SHIELD Community. 

      • Document/Inventory content.

      • Manage communication channels (website, social media, email, etc.).

      • Question: Should the Communication Workgroup be responsible for ongoing communications (ex, all social media posts would need to be published by the workgroup) or is the function more administrative and Steering Committee is ultimately responsible?

      • Role in reviewing and approving content (presentations, publications), delegated by Steering Committee?

    • There was concern that it may be impractical for all communications to have to go through the Workgroup (for example, content created by other workgroups) or to think that the workgroup was responsible for editing/approving/issuing all communications as opposed to having a more strategic role.     

    • Strategy - What are the best forums (ex, conferences) for presentations? Is the workgroup responsible for determining/finding the best venues

    • Are we responsible for creating/obtaining a logo? Who would build this? Budget/Donation? Can we use free logo design services?

  • Meeting Schedule

    • Move next Workgroup meeting from 8/30 to 9/6

Action items

  • Eric to send updated meeting invite and update SHIELD calendar for next meeting

  • Aaron will provide examples of Communications Group purposes from other committees he’s been a part of.

Quick decisions not requiring context or tracking

For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.

Decisions requiring context or tracking

For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.