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

Difference between revisions of "20140509 FGB FMG WGM Minutes"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::FMG Template}}")
 
 
Line 1: Line 1:
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC FMG Meeting Minutes''' <br/>
+
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 TSC FGB/FMG Joint Meeting Minutes''' <br/>
'''Location: <br>https://global.gotomeeting.com/join/279790597''' <br/>(voice and screen)
+
'''Location: <br>Pima (Hohokam Ballroom)
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2014-mm-dd '''<br/> '''Time: 1:00 PM U.S. Eastern'''
+
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2014-05-09'''<br/> '''Time: 9AM'''
 
|-
 
|-
 
| width="0%" colspan="2" align="right"|'''Chair''':  
 
| width="0%" colspan="2" align="right"|'''Chair''':  
| width="0%" colspan="1" align="right"|'''Note taker(s)''':   
+
| width="0%" colspan="1" align="right"|'''Note taker(s)''':  David
 
|}
 
|}
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
|colspan="3" align="center" style="background:#f0f0f0;"| Quorum = chair + 4
 
|colspan="3" align="center" style="background:#f0f0f0;"| Quorum = chair + 4
|colspan="4" align="center" style="background:#f0f0f0;"| '''yes/no'''
+
|colspan="4" align="center" style="background:#f0f0f0;"| '''yes'''
 
|-
 
|-
| Co chairs|| ||David Hay || ||Lloyd McKenzie
+
| Co chairs|| x||David Hay ||x ||Lloyd McKenzie
 
|-
 
|-
| ex-officio|| ||Woody Beeler,<br/> Dave Shaver <br/>FGB Co-chairs||.||John Quinn, CTO
+
| ex-officio||x ||Woody Beeler,<br/>FGB Co-chairs||.||John Quinn, CTO
 
|}
 
|}
 
<!--  -->
 
<!--  -->
Line 22: Line 22:
 
| 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
 
|-
 
|-
| || Hans Buitendijk|| || Hugh Glover || ||Paul Knapp || || Lynn Laakso, scribe
+
|x || Hans Buitendijk||regrets || Hugh Glover || x||Paul Knapp ||regrets || Lynn Laakso, scribe
 
|-
 
|-
| ||Josh Mandel  || ||John Moehrke|| ||Brian Pech || ||   
+
|regerts||Josh Mandel  ||x ||John Moehrke|| x||Brian Pech || ||   
 
|-
 
|-
| || || || || || ||.||<!--guest-->  
+
|x || Ewout KRamer ||x|| Grahame Grieve ||x ||Lorraine Constable||.||<!--guest-->  
 
|-
 
|-
 
|}
 
|}
Line 33: Line 33:
 
*Roll Call
 
*Roll Call
 
*Agenda Check
 
*Agenda Check
*Minutes from [[2014mmdd_FMG_concall]]
+
**SOA plans for next WGM
*Administrative
+
**Clinician Connectathon
** Action items
+
**FHIR registries
**
+
**OpenEHR/Clinical Review
*Reports
+
**Transfer of liaison responsibilities from Lorraine, adding Attachments WG, CBCC
**Connectathon management (David/Brian)
+
**Discussion of process to approve tooling enhancements
**[[FHIR Governance Board|FGB]] –
+
**PSS for DSTU 2
**MnM –
+
**PSS for PA stuff, PSS for SDC, others?
**[[FMG Liaisons]] –
+
**HL7 Conformance testing?
<!--
+
**Plans for QA & next ballot
*Precepts
+
**Getting Proposals up-to-date
**
+
**Next steps re: governance
-->
+
**Vitality Assessment?
*Process management
+
 
**Ballot Planning
 
<!--**Developing FMG Management Methodology - see [[FHIR Methodology Process]] and [[FHIR Guide to Designing Resources]]
 
**FHIR Design patterns - see [[FHIR Design Patterns]] -->
 
**Ballot content review and QA process [[FHIR QA Guidelines]]
 
*AOB (Any Other Business)
 
  
 
==Minutes==
 
==Minutes==
 +
*'''SOA Plans'''
 +
**DH described - SOA Plans for poster days Q3/4 Monday/Wednesday
 +
**Lloyd has asked that one of the sessions be FHIR joint as 4 quarters probably too much
 +
**JM: All resource proposals have the same state – should they be tidied up.
 +
**Discussion around timing of requests – especially for PSS. Woody suggested that date should be receiving PSS – not it’s approval. LM said we have both dates – they are targets and may slip in some cases.
 +
**Paul: Business process comes first – then resources.
 +
**LM: stick with targets – manage as best as we can.
 +
*'''Clinician Connectathon'''
 +
**LM: Proposal for a clinician connectathon on Friday at the next WGM. Clinicians will have real world scenario and use a tool to enter that data **and ensure that spec meets needs and identify where it does not. Hopefully get enthusiasm from the clinical community about FHIR.
 +
**HB: Interesting to see how different disciplines approach the same problem.
 +
**GG: Intention is to be a prototype for future events.
 +
**LM: work over the next month to finalize.
 +
*'''FHIR Registries'''
 +
**LM: Want registries for things like Profile, ValueSet, Namespace (system), mappings, concept maps for implementers. Working with electronic services. There is some discussion in an associated project – OID registry and some discussion around funding and HL7 resource.
 +
**An offer from furore to build and supply. Suggestion/Discussion to work though Electronic Services.  Discussion around whether the decision rests with the FMG/FGB or the wider organization.
 +
**GG: Not HL7 owned content. Need to clarify governance.
 +
**WB: agree it needs to be done.
 +
**HB: need to allow other companies to ‘bid’ for the work.
 +
**EK: absence of registry is becoming painful.
 +
**Motion: EK to document offer from furore. FMG recommend acceptance. Take to TSC and ask to endorse/process.
 +
**Moved/seconded: WB/LC
 +
**Discussion: A requirement is that access to registry is free. BP: This is an urgent need and HL7 needs to maintain control
 +
**Passed unanimously 10-0-0
 +
*'''OpenEHR (OE) /Clinical Review'''
 +
**GG: Align FHIR Resources to archetypes. Use OE tooling to represent resources. Not necessarily the same but at least differences known. Good for overall profile.
 +
**Will need joint IP licensing – openEHR and FHIR have different Licenses. (contributors need to understand that their goes to both OE and FHIR licenses.
 +
**PK: will this work through HL7 committees. GG: will co-ordinate between co-chairs of HL7 WorkGroups and OE.
 +
**Motion: to proceed with pilot
 +
**Move/second: GG/PK
 +
**Passed unanimously 10-0-0
 +
 +
*'''Liaison transfer'''
 +
**LM: Need to transfer LC’s responsibility. HB to review current list and confirm/propose change off line. Will confirm on next call.
 +
 +
*'''Process to approve tooling enhancements'''
 +
**LM: process to enhance tooling to combine rapid fix/support with FMG ‘need to know’.
 +
**PK: confirm whether spec build or spec presentation.
 +
**GG: hard to separate.
 +
**LM: we know how to manage request to domain content – who approves publication changes.
 +
**LC: different categories of change.
 +
**# visibly changes spec
 +
**#change that impacts maintainers of content
 +
**#tooling operation changes.
 +
** #3 – that’s internal  - just do it.
 +
**LM: for #1 & #2 – ‘heads-up’ to FMG before/after change depending on degree of change.
 +
**WB: should we formally identify those who make change. It’s a change control process – up to group.
 +
**LC: communications important. Use Committers chat for a start but need more.
 +
**LM: provided that affected groups notified then should be OK. If major change then push up (at discretion of maintainers)
 +
**BP: Publishing is available to help out as required.
 +
**Action: LM to document process to approve tracker items
 +
*'''PSS for DSTU2'''
 +
**LM:  defer to call – and other groups
 +
**GG: Core team is developing resources – what PSS is required (resource proposals will be there).
 +
**LM: Make sure that M&M is in PSS for DSTU2 (M&M is owner of core resources)
 +
**LC: be clear that ballot resolution is the responsibility of the work group
 +
*10:30 BP leaves.
 +
*'''Conformance testing'''
 +
**LM: HL7 intends to offer conformance testing for FHIR. Is there a need yet?
 +
*'''Plans for QA & next ballot'''
 +
**LM: QA after sept 21st sept (quality).  Another QA prior to publication (comments)
 +
*'''Getting proposals up to date'''
 +
**LM: Need to approve current proposals.
 +
**LM: How do we want to maintain current proposals? Eg scope could change, name could change etc.
 +
**LC: do we need to change them? They are a work product only...
 +
**LM: approved RP’s have a status with a note that may not reflect
 +
**Motion: check that RP’s for current proposal have correct owner and approve as block.
 +
**Approve/Second LC/HB
 +
**Passed unanimously 10-0-0
  
  
Line 64: Line 127:
 
|-
 
|-
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
[[2014mmdd FMG concall]]
+
[[20140514 FMG concall]]
  
 
|}
 
|}

Latest revision as of 18:12, 14 May 2014

HL7 TSC FGB/FMG Joint Meeting Minutes

Location:
Pima (Hohokam Ballroom)

Date: 2014-05-09
Time: 9AM
Chair: Note taker(s): David
Quorum = chair + 4 yes
Co chairs x David Hay x Lloyd McKenzie
ex-officio x Woody Beeler,
FGB Co-chairs
. John Quinn, CTO
Members Members Members Observers/Guests
x Hans Buitendijk regrets Hugh Glover x Paul Knapp regrets Lynn Laakso, scribe
regerts Josh Mandel x John Moehrke x Brian Pech
x Ewout KRamer x Grahame Grieve x Lorraine Constable .

Agenda

  • Roll Call
  • Agenda Check
    • SOA plans for next WGM
    • Clinician Connectathon
    • FHIR registries
    • OpenEHR/Clinical Review
    • Transfer of liaison responsibilities from Lorraine, adding Attachments WG, CBCC
    • Discussion of process to approve tooling enhancements
    • PSS for DSTU 2
    • PSS for PA stuff, PSS for SDC, others?
    • HL7 Conformance testing?
    • Plans for QA & next ballot
    • Getting Proposals up-to-date
    • Next steps re: governance
    • Vitality Assessment?


Minutes

  • SOA Plans
    • DH described - SOA Plans for poster days Q3/4 Monday/Wednesday
    • Lloyd has asked that one of the sessions be FHIR joint as 4 quarters probably too much
    • JM: All resource proposals have the same state – should they be tidied up.
    • Discussion around timing of requests – especially for PSS. Woody suggested that date should be receiving PSS – not it’s approval. LM said we have both dates – they are targets and may slip in some cases.
    • Paul: Business process comes first – then resources.
    • LM: stick with targets – manage as best as we can.
  • Clinician Connectathon
    • LM: Proposal for a clinician connectathon on Friday at the next WGM. Clinicians will have real world scenario and use a tool to enter that data **and ensure that spec meets needs and identify where it does not. Hopefully get enthusiasm from the clinical community about FHIR.
    • HB: Interesting to see how different disciplines approach the same problem.
    • GG: Intention is to be a prototype for future events.
    • LM: work over the next month to finalize.
  • FHIR Registries
    • LM: Want registries for things like Profile, ValueSet, Namespace (system), mappings, concept maps for implementers. Working with electronic services. There is some discussion in an associated project – OID registry and some discussion around funding and HL7 resource.
    • An offer from furore to build and supply. Suggestion/Discussion to work though Electronic Services. Discussion around whether the decision rests with the FMG/FGB or the wider organization.
    • GG: Not HL7 owned content. Need to clarify governance.
    • WB: agree it needs to be done.
    • HB: need to allow other companies to ‘bid’ for the work.
    • EK: absence of registry is becoming painful.
    • Motion: EK to document offer from furore. FMG recommend acceptance. Take to TSC and ask to endorse/process.
    • Moved/seconded: WB/LC
    • Discussion: A requirement is that access to registry is free. BP: This is an urgent need and HL7 needs to maintain control
    • Passed unanimously 10-0-0
  • OpenEHR (OE) /Clinical Review
    • GG: Align FHIR Resources to archetypes. Use OE tooling to represent resources. Not necessarily the same but at least differences known. Good for overall profile.
    • Will need joint IP licensing – openEHR and FHIR have different Licenses. (contributors need to understand that their goes to both OE and FHIR licenses.
    • PK: will this work through HL7 committees. GG: will co-ordinate between co-chairs of HL7 WorkGroups and OE.
    • Motion: to proceed with pilot
    • Move/second: GG/PK
    • Passed unanimously 10-0-0
  • Liaison transfer
    • LM: Need to transfer LC’s responsibility. HB to review current list and confirm/propose change off line. Will confirm on next call.
  • Process to approve tooling enhancements
    • LM: process to enhance tooling to combine rapid fix/support with FMG ‘need to know’.
    • PK: confirm whether spec build or spec presentation.
    • GG: hard to separate.
    • LM: we know how to manage request to domain content – who approves publication changes.
    • LC: different categories of change.
      1. visibly changes spec
      2. change that impacts maintainers of content
      3. tooling operation changes.
    • #3 – that’s internal - just do it.
    • LM: for #1 & #2 – ‘heads-up’ to FMG before/after change depending on degree of change.
    • WB: should we formally identify those who make change. It’s a change control process – up to group.
    • LC: communications important. Use Committers chat for a start but need more.
    • LM: provided that affected groups notified then should be OK. If major change then push up (at discretion of maintainers)
    • BP: Publishing is available to help out as required.
    • Action: LM to document process to approve tracker items
  • PSS for DSTU2
    • LM: defer to call – and other groups
    • GG: Core team is developing resources – what PSS is required (resource proposals will be there).
    • LM: Make sure that M&M is in PSS for DSTU2 (M&M is owner of core resources)
    • LC: be clear that ballot resolution is the responsibility of the work group
  • 10:30 BP leaves.
  • Conformance testing
    • LM: HL7 intends to offer conformance testing for FHIR. Is there a need yet?
  • Plans for QA & next ballot
    • LM: QA after sept 21st sept (quality). Another QA prior to publication (comments)
  • Getting proposals up to date
    • LM: Need to approve current proposals.
    • LM: How do we want to maintain current proposals? Eg scope could change, name could change etc.
    • LC: do we need to change them? They are a work product only...
    • LM: approved RP’s have a status with a note that may not reflect
    • Motion: check that RP’s for current proposal have correct owner and approve as block.
    • Approve/Second LC/HB
    • Passed unanimously 10-0-0


Next Steps

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

20140514 FMG concall


Back to FHIR_Management_Group

© 2014 Health Level Seven® International