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

20161025 US Realm SC Call

From HL7Wiki
Jump to navigation Jump to search

back to US_Realm_Steering_Committee
back to US_Realm_Steering_Committee_Conference_Calls

US Realm Steering Committee Call Agenda/Minutes

Location: call 770-657-9270 using code 156896#
929-752-237

Date: 2016-10-25
Time: 1 PM Eastern
Co-Chairs Ed/Brett Note taker(s) Anne
Attendee / Name
Calvin Beebe Keith Boone x Hans Buitendijk
x Lorraine Constable x Johnathan Coleman Regrets Ed Hammond
Regrets Tony Julian x Paul Knapp x Austin Kreisler
Brett Marquard Ken McCaslin Nancy Orvis
x Brian Pech Regrets Wayne Kubick Mark Roche
Sandra Stuart . Pat Van Dyke x Anne Wizauer
x Danielle Friend x Eric Haas Regrets Jenni Syed
Steve Posnak x David Susanto x Craig Parker
Visitor / Name
no quorum definition


Agenda

Administrivia

  • Agenda review
  • Review notes from 20161011_US_Realm_SC_Call
  • Action Items
    • Ed to get contact info from John Roberts for USDA
    • All to send Ed any ideas regarding financial resources for HL7

Discussion:

  • FMG comments on extension review process (Brian Pech)


Minutes

  • Brian presents feedback from FMG on the extension review process. Discussion had a few points: 1) agree with initial decision point that the WG would determine whether it's core or not and the subsequent referrals. 2) there appears to be two separate repositories; one under the control of HL7 and then a separate US realm extension repository. One suggestion was that there could be a unified repository with US realm extensions tagged appropriately so they could be queried. 3) There appears to be both a repository and a registry and they are not necessarily the same. 4) Questioned how a WG would determine whether or not something is core or realm specific. 5) A suggestion for perhaps changing the workflow; if the extension has already been designated as US-realm specific and it went through a US realm development process, does it make sense that it has to go back to the overall WG for approval, or would it be a courtesy to the WG to notify them that it's been deposited in to the repository with appropriate tagging. Question over criteria to define core vs. non-core.
  • Lorraine: Domain experts should review the content following the development. Brian: If it's a realm-specific extension, once they've completed the work, does it have to go back to the overlording WG? Just a question over whether or not there's a better way to sequence that bottom row.
  • Hans: hopes that this will be taken into context of not just US realm - should apply to all realms.
  • Johnathan: Has there been any more thought put into how to differentiate what qualifies for Core? Brian: Not aware of any further conversation to try to elucidate the criteria. Lorraine: Usually we use core to apply to things that are not extensions. Universal realm vs. affiliate-specific realm is more appropriate language than using core for extensions. Distinction between universal and affiliate is important, but there is a limited need for using core extension as well. Brett: There are core extensions in the build today - there is a need for core extensions. What would you call an extension that is part of the core FHIR build? Lorraine: A universal extension. Brett: If we use the terms universal extension and realm extension, would anyone be confused? Johnathan: That would be helpful.
  • Brett: We did chop out the submit to original WG block on the bottom row. FMG has discussed how WG should be involved. Brett displays updated process diagram. Hans asks to remove the word core - use Universal and realm. Paul: core profile is balloted within the spec and all others are balloted outside. Need to differentiate things which were developed under the US realm and things that are official US artifacts. Johnathan: There's the base FHIR build (or FHIR core), then we've got universal extensions on that, then we've got US- or other realm-specific extensions. Brett asks what we call a US Realm extension that has been approved by US Realm Steering Committee vs. anything else US-based? Is concerned about dropping the word core and not replacing it with something else. Lorraine: It's still a local extension unless it comes here.
  • Brett removes the word core from everywhere and adds explanatory verbiage.
  • Paul asks about the registry vs. the repository. Suggestion to change wording to "Publish in HL7 extension repository as US Realm." Brett updates.
  • Will post for review this week and do approval vote at the start of next call.


Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items


© 2016 Health Level Seven® International. All rights reserved