2017-05-08 Learning Health Systems WGM

From HL7Wiki
Jump to navigation Jump to search
Facilitator John Roberts Note taker(s) Russell Leftwich
Attendee Name Affiliation


X Russell Leftwich InterSystems
X John Roberts Tennessee Department of Health
Stephen Chu Individual
Evelyn Gallego ONC
Kathy Walsh LabCorp
Asim Muhammad Philips Research Europe
X Laura Heermann-Langford Intermountain Healthcare
Emma Jones Allscripts
Jeff Brown Cancerlinq
Lisa Nelson Individual
Dave Carlson VA
X Chris Melo Phillips Healthcare
Michelle Miller Cerner
Benjamin Kummer Columbia University
Matt Rhan
Michael Padula
Serafina Versaggi VA

Minutes

  • Chair: John Roberts
  • Scribe: Russell Leftwich
  • Russ the slide deck which is posted on the wiki: Reverse Engineering a Care Team.
    • The same slides were previewed on the April 28 call
  • a quorum was present but no actions were taken
  • Approach Care Team DAM development by considering from the perspective of individual
    • the virtual care team is everyone who touches the patient (individual)
    • describe relationships of each care team member to the patient
    • relationship between individuals on the care team
    • care team members are professional, family, community
      • everyone who touches the patient (physically, face to face, or virtually)
      • Laura: include the radiologist who interprets images, pathologist who interprets
      • John: include public health; epidemiologists and case workers
      • touches may be episodic, usually are
      • relationships may be time limited, inactive, retired, or active
    • thet care team may include component teams or sub-teams who fulfill a role on whole team
    • Team members usually have only a transactional business relationship (they don’t have the same employer or governance)
    • Roles on team filled by individuals may have a "back-up" or call group to fill in when unavailable
    • each care team is usually unique for an individual
    • Component teams may be assigned by an organization, like the OR team or a Code Team
    • Component teams are assigned by an org, typically play a limited, if any, role in care coordination. They are not high priority for modeling from perspective of care coordination
    • Many attributes of team members/roles need to be defined: relationships, activity status, frequency of contact, transience of members (rehab team), governance (who leads planning, who has execution role), consent (what members on team have what consent from the patient), communication (between team members, including family/community members)
      • one purpose of a DAM is to facilitate automation of consent processes and communication
    • Storyboards from care team value set work could be the starting point for storyboards for a DAM
  • Laura/Russ: next step will be to start to define some of the classes of attributes referenced above
  • for now will keep 4pm ET Care Team DAM call time; survey for alternative times
    • Adjourned at 6:05pm CEDT (Madrid)