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

Difference between revisions of "20140205 FMG concall"

From HL7Wiki
Jump to navigation Jump to search
Line 4: Line 4:
 
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2014-02-05'''<br/> '''Time: 1:00 PM U.S. Eastern'''
 
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2014-02-05'''<br/> '''Time: 1:00 PM U.S. Eastern'''
 
|-
 
|-
| width="0%" colspan="2" align="right"|'''Chair''':  
+
| width="0%" colspan="2" align="right"|'''Chair''': Lloyd
| width="0%" colspan="1" align="right"|'''Note taker(s)''':   
+
| width="0%" colspan="1" align="right"|'''Note taker(s)''':  Lynn
 
|}
 
|}
  
Line 12: Line 12:
 
|colspan="4" align="center" style="background:#f0f0f0;"| '''yes/no'''
 
|colspan="4" align="center" style="background:#f0f0f0;"| '''yes/no'''
 
|-
 
|-
| Co chairs|| ||Hugh Glover|| ||Lloyd McKenzie
+
| Co chairs|| x||Hugh Glover||x ||Lloyd McKenzie
 
|-
 
|-
 
| ex-officio|| ||Ron Parker, FGB Chair||.||John Quinn, CTO
 
| ex-officio|| ||Ron Parker, FGB Chair||.||John Quinn, CTO
Line 21: Line 21:
 
| colspan="2"| Members ||colspan="2"|Members||colspan="2"|Members ||colspan="2"|Observers/Guests
 
| colspan="2"| Members ||colspan="2"|Members||colspan="2"|Members ||colspan="2"|Observers/Guests
 
|-
 
|-
| ||Lorraine Constable|| ||Paul Knapp|| ||John Moehrke|| || Lynn Laakso, scribe
+
|x ||Lorraine Constable||x ||Paul Knapp||x ||John Moehrke|| x|| Lynn Laakso, scribe
 
|-
 
|-
|regrets ||David Hay || ||Josh Mandel|| regrets||Brian Pech  || || Austin Kreisler  
+
|regrets ||David Hay ||x ||Josh Mandel|| regrets||Brian Pech  || || Austin Kreisler  
 
|-
 
|-
 
| || || || || || ||.||<!--guest-->  
 
| || || || || || ||.||<!--guest-->  
Line 48: Line 48:
  
 
==Minutes==
 
==Minutes==
 +
Convened at 1:06
 +
*Agenda Check - Paul sent a document on governance recommendations for publishing; postpone Profile Tool demo; Hugh asks if we need to address the forking discussion on the chat. Hugh moves approval of amended agenda; second by John; unanimously approved.
 +
*Minutes from [[20140129_FMG_concall]] Hugh moves approval, second by John, unanimously approved.
 +
*Administrative
 +
** Action items
 +
*** Hugh will see proposals for profiles reviewed by FMG Published as part of standard or as separate document - review [[Category:FHIR_Resource_Proposal]] and how should the visibility of the FHIR process descriptions be called out. Paul suggests links from the FHIR main page. He added a profile proposal template and will come up under resource proposal categories. Lloyd suggests you refer to them all as FHIR proposals both resource and profile. The HL7 International ballot candidates go here but we'll need a place for the rest.
 +
****Profiles can be done on both resources and data types notes Lloyd. This could lead to a profile on a resource and multiple profiles on datatypes used in that resource. Profile for "money" as a constraint on quantity, for example. One profile adds an extension for county into "address" for US purposes. Need to have an indicator if it's meant to be balloted and published with the main FHIR specification or elsewhere. Further discussion ensued.
 +
****Naming is also a consideration and formal naming extensions with large numbers of profiles. Realm is another consideration. Does core need to be UV realm only? DCMs will become profiles, IGs for CDA, every realm specific implementation. This is met with resistance. Lloyd describes a best practices profile on data collection for a particular diagnosis. However the majority of them will not be balloted/published by HL7. Interoperability will depend on whether your system can interpret the data from the profile used by the sending system; receiver will see a resource, but not necessarily be able to use all the data in an interoperable fashion.
 +
****Profiles have three levels of recognition: self-registration (publishing) to repository for discoverability; second level is storage in and retrieval from HL7-managed repository. Third level is betting and stamp of approval by a WG aligned with principles, etc.
 +
****Review again next week.
 +
* Policy and Governance Recommendations for Publishing, Tooling and Electronic Services Support for FHIR - this is a result of Brian Lorraine and Paul's action item.
 +
**draft recommendations for FGB in defining governance precepts. Lloyd requests delineation of responsibilities for the different bodies.
 +
**Lorraine adds that TSC had comments on the request for publication and reminds the FMG that publication requests are typically submitted once all the edits are completed. Exceptions to this process can be requested.
 +
 +
Being at time, adjourned 2:00 PM
  
  
Line 59: Line 74:
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
  
 
+
*[[20140212 FMG concall]]
 
|}
 
|}
  

Revision as of 19:01, 5 February 2014

HL7 TSC FMG Meeting Minutes

Location: call 770-657-9270 using code 985371#
https://global.gotomeeting.com/join/450662277

Date: 2014-02-05
Time: 1:00 PM U.S. Eastern
Chair: Lloyd Note taker(s): Lynn
Quorum = chair + 4 yes/no
Co chairs x Hugh Glover x Lloyd McKenzie
ex-officio Ron Parker, FGB Chair . John Quinn, CTO
Members Members Members Observers/Guests
x Lorraine Constable x Paul Knapp x John Moehrke x Lynn Laakso, scribe
regrets David Hay x Josh Mandel regrets Brian Pech Austin Kreisler
.

Agenda

Minutes

Convened at 1:06

  • Agenda Check - Paul sent a document on governance recommendations for publishing; postpone Profile Tool demo; Hugh asks if we need to address the forking discussion on the chat. Hugh moves approval of amended agenda; second by John; unanimously approved.
  • Minutes from 20140129_FMG_concall Hugh moves approval, second by John, unanimously approved.
  • Administrative
    • Action items
      • Hugh will see proposals for profiles reviewed by FMG Published as part of standard or as separate document - review and how should the visibility of the FHIR process descriptions be called out. Paul suggests links from the FHIR main page. He added a profile proposal template and will come up under resource proposal categories. Lloyd suggests you refer to them all as FHIR proposals both resource and profile. The HL7 International ballot candidates go here but we'll need a place for the rest.
        • Profiles can be done on both resources and data types notes Lloyd. This could lead to a profile on a resource and multiple profiles on datatypes used in that resource. Profile for "money" as a constraint on quantity, for example. One profile adds an extension for county into "address" for US purposes. Need to have an indicator if it's meant to be balloted and published with the main FHIR specification or elsewhere. Further discussion ensued.
        • Naming is also a consideration and formal naming extensions with large numbers of profiles. Realm is another consideration. Does core need to be UV realm only? DCMs will become profiles, IGs for CDA, every realm specific implementation. This is met with resistance. Lloyd describes a best practices profile on data collection for a particular diagnosis. However the majority of them will not be balloted/published by HL7. Interoperability will depend on whether your system can interpret the data from the profile used by the sending system; receiver will see a resource, but not necessarily be able to use all the data in an interoperable fashion.
        • Profiles have three levels of recognition: self-registration (publishing) to repository for discoverability; second level is storage in and retrieval from HL7-managed repository. Third level is betting and stamp of approval by a WG aligned with principles, etc.
        • Review again next week.
  • Policy and Governance Recommendations for Publishing, Tooling and Electronic Services Support for FHIR - this is a result of Brian Lorraine and Paul's action item.
    • draft recommendations for FGB in defining governance precepts. Lloyd requests delineation of responsibilities for the different bodies.
    • Lorraine adds that TSC had comments on the request for publication and reminds the FMG that publication requests are typically submitted once all the edits are completed. Exceptions to this process can be requested.

Being at time, adjourned 2:00 PM


Next Steps

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


Back to FHIR_Management_Group

© 2014 Health Level Seven® International