This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "20180821 US Realm SC Call"

From HL7Wiki
Jump to navigation Jump to search
Line 101: Line 101:
 
****Last week we decided two hours a week is too much for this group, but 60% of calls could be applicable
 
****Last week we decided two hours a week is too much for this group, but 60% of calls could be applicable
 
****Need to define our appropriate number of members and roles
 
****Need to define our appropriate number of members and roles
*****Ed: Most members represent a particular interest. Brett and Ed cover each other, but each interest represented by other members isn’t duplicated in the same way as the cochairs. Need to determine if people have lost interest so we can look for an alternate person to represent their position. Calvin: The TSC benefits from redundancy on the perspectives – two cochairs per steering division, etc. Austin: The TSC’s role are clearly defined. The members’ roles in this group aren’t clearly defined. Ed: The bigger the size, the more difficult it is to do conference calls. Johnathan asks about having different domains represented, like privacy, security, etc. Austin: That would be especially useful if this group begins doing content development. It’s a decision at the board or executive committee-level committee to change what the group is supposed to accomplish. Ed: We don’t have the very best model for doing work in HL7 anymore. Need to re-examine how we do work and the relationship between groups. Austin: The TSC is looking at a number of these things – have reorganized the steering divisions, etc. and are looking at trying to streamline processes. Ed: Does the USRSC want to have an input to the TSC? Austin: That’s definitely something to look at. Ed mentions app development and their trustworthiness. Steve:  There are some areas where we’re looking into the future with US Core data for interoperability. It appears there is a groundswell of work in the WGs that have a US Realm focus. We may be able to be receptive here to the needs of the community. What does it mean when an app says it’s FHIR compliant? Is there something from the US Realm perspective that they should do to be able to say that? Ed: We’ve entered into an SOU with Web 3D which will open the door for a number of health-related applications and virtual reality applications. Need to think about how we can accommodate this and other groups coming in.  
+
*****Ed: Most members represent a particular interest. Brett and Ed cover each other, but each interest represented by other members isn’t duplicated in the same way as the cochairs. Need to determine if people have lost interest so we can look for an alternate person to represent their position.  
 +
*****Calvin: The TSC benefits from redundancy on the perspectives – two cochairs per steering division, etc. Austin: The TSC’s role are clearly defined. The members’ roles in this group aren’t clearly defined. Ed: The bigger the size, the more difficult it is to do conference calls.  
 +
*****Johnathan asks about having different domains represented, like privacy, security, etc. Austin: That would be especially useful if this group begins doing content development. It’s a decision at the board or executive committee-level committee to change what the group is supposed to accomplish. Ed: We don’t have the very best model for doing work in HL7 anymore. Need to re-examine how we do work and the relationship between groups.  
 +
*****Austin: The TSC is looking at a number of these things – have reorganized the steering divisions, etc. and are looking at trying to streamline processes. Ed: Does the USRSC want to have an input to the TSC? Austin: That’s definitely something to look at.  
 +
*****Ed mentions app development and their trustworthiness. Steve:  There are some areas where we’re looking into the future with US Core data for interoperability. It appears there is a groundswell of work in the WGs that have a US Realm focus. We may be able to be receptive here to the needs of the community. What does it mean when an app says it’s FHIR compliant? Is there something from the US Realm perspective that they should do to be able to say that?  
 +
*****Ed: We’ve entered into an SOU with Web 3D which will open the door for a number of health-related applications and virtual reality applications. Need to think about how we can accommodate this and other groups coming in.  
 
*****Members need to have access to and have read PSS before the call. Nancy notes that she has trouble getting the PSSs. Discussion over how to get them to people.
 
*****Members need to have access to and have read PSS before the call. Nancy notes that she has trouble getting the PSSs. Discussion over how to get them to people.
 
*****Austin: Could publicize who is attending the meetings on a spreadsheet.
 
*****Austin: Could publicize who is attending the meetings on a spreadsheet.
 +
*Adjourned at 2:00 pm Eastern
  
 
===Meeting Outcomes===
 
===Meeting Outcomes===

Revision as of 13:46, 27 August 2018

back to US_Realm_Steering_Committee
back to US_Realm_Steering_Committee_Conference_Calls

US Realm Steering Committee Call Agenda/Minutes

Location: https://global.gotomeeting.com/join/929752237]

Date: 2018-08-21
Time: 1 PM Eastern
Co-Chairs Ed/Brett Note taker(s) Anne
Attendee / Name
Calvin Beebe Keith Boone Hans Buitendijk
Lorraine Constable Johnathan Coleman Ed Hammond
Tony Julian Paul Knapp Austin Kreisler
Brett Marquard Ken McCaslin Nancy Orvis
Brian Pech Wayne Kubick Christol Green
Sandra Stuart . Pat Van Dyke . Craig Parker
Danielle Friend . Eric Haas . Jenni Syed
Steve Posnak . David Susanto . John Roberts
Visitor/ Name
Quorum: Chair + 7

Agenda

Administrivia

Discussion:

  • Continued discussion on TSC attendance policy from GOM 09.01.03:
    • Criteria for removal shall include:
      • mismanagement or obfuscation of TSC projects or processes
      • failure to attend two consecutive Work Group Meetings without notice or the subsequent presentation of mitigating circumstances; or
      • failure to participate in at least 60% of the TSC teleconferences held in the preceding calendar year;
      • failure to meet the commitment of at least two hours per week to the TSC.
      • undesirable or disruptive behavior that deviates from the Code of Conduct (§05.05)
        • Last week we decided two hours a week is too much for this group, but 60% of calls could be applicable
        • Need to define our appropriate number of members and roles


Minutes

Discussion:

  • Continued discussion on TSC attendance policy from GOM 09.01.03:
    • Criteria for removal shall include:
      • mismanagement or obfuscation of TSC projects or processes
      • failure to attend two consecutive Work Group Meetings without notice or the subsequent presentation of mitigating circumstances; or
      • failure to participate in at least 60% of the TSC teleconferences held in the preceding calendar year;
      • failure to meet the commitment of at least two hours per week to the TSC.
      • undesirable or disruptive behavior that deviates from the Code of Conduct (§05.05)
        • Last week we decided two hours a week is too much for this group, but 60% of calls could be applicable
        • Need to define our appropriate number of members and roles
          • Ed: Most members represent a particular interest. Brett and Ed cover each other, but each interest represented by other members isn’t duplicated in the same way as the cochairs. Need to determine if people have lost interest so we can look for an alternate person to represent their position.
          • Calvin: The TSC benefits from redundancy on the perspectives – two cochairs per steering division, etc. Austin: The TSC’s role are clearly defined. The members’ roles in this group aren’t clearly defined. Ed: The bigger the size, the more difficult it is to do conference calls.
          • Johnathan asks about having different domains represented, like privacy, security, etc. Austin: That would be especially useful if this group begins doing content development. It’s a decision at the board or executive committee-level committee to change what the group is supposed to accomplish. Ed: We don’t have the very best model for doing work in HL7 anymore. Need to re-examine how we do work and the relationship between groups.
          • Austin: The TSC is looking at a number of these things – have reorganized the steering divisions, etc. and are looking at trying to streamline processes. Ed: Does the USRSC want to have an input to the TSC? Austin: That’s definitely something to look at.
          • Ed mentions app development and their trustworthiness. Steve: There are some areas where we’re looking into the future with US Core data for interoperability. It appears there is a groundswell of work in the WGs that have a US Realm focus. We may be able to be receptive here to the needs of the community. What does it mean when an app says it’s FHIR compliant? Is there something from the US Realm perspective that they should do to be able to say that?
          • Ed: We’ve entered into an SOU with Web 3D which will open the door for a number of health-related applications and virtual reality applications. Need to think about how we can accommodate this and other groups coming in.
          • Members need to have access to and have read PSS before the call. Nancy notes that she has trouble getting the PSSs. Discussion over how to get them to people.
          • Austin: Could publicize who is attending the meetings on a spreadsheet.
  • Adjourned at 2:00 pm Eastern

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items


© 2018 Health Level Seven® International. All rights reserved