This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20140218 FGB concall"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
|colspan="2"|Chair/CTO ||colspan="2"|Members ||colspan="2"|Members | |colspan="2"|Chair/CTO ||colspan="2"|Members ||colspan="2"|Members | ||
|- | |- | ||
| − | | ||Ron Parker|| ||George (Woody) Beeler||x ||Ewout Kramer | + | |x ||Ron Parker|| ||George (Woody) Beeler||x ||Ewout Kramer |
|- | |- | ||
|x ||John Quinn || ||Grahame Grieve||regrets ||Hugh Glover | |x ||John Quinn || ||Grahame Grieve||regrets ||Hugh Glover | ||
|- | |- | ||
| − | | || <!--n/a-->|| ||Lloyd McKenzie|| ||<!-- open--> | + | | || <!--n/a-->|| x||Lloyd McKenzie|| ||<!-- open--> |
|- | |- | ||
| Line 59: | Line 59: | ||
***:FHIR focuses strongly on ease of implementation by using open industry open web standards. It adds support for REST-style architectures used by current cloud, social media, and mobile platforms where exchanging partners will exploit FHIR’s flexibility to match the need for continuous change in these markets. It provides interoperability for the majority of health IT system interface right out-of-the box, yet has a framework for manageably extending and adapting the standard to suit specific needs. | ***:FHIR focuses strongly on ease of implementation by using open industry open web standards. It adds support for REST-style architectures used by current cloud, social media, and mobile platforms where exchanging partners will exploit FHIR’s flexibility to match the need for continuous change in these markets. It provides interoperability for the majority of health IT system interface right out-of-the box, yet has a framework for manageably extending and adapting the standard to suit specific needs. | ||
***'''What will happen to HL7 Version 2, Version 3, and CDA®? ''' | ***'''What will happen to HL7 Version 2, Version 3, and CDA®? ''' | ||
| − | ***:Version 2 enjoys wide adoption for communication within hospitals and will remain to do so for years to come. CDA is a growing focus of a large part of the healthcare industry and this growth is likely to continue for some time. HL7 Version 3 forms the underlying semantics of CDA and continues to provide semantics for FHIR though less obtrusively. V3 messaging will continue to be used where it has been adopted. All HL7 standards will continue to be maintained as long as the implementation community requires. | + | ***:Version 2 enjoys wide adoption for communication within hospitals and will remain to do so for years to come. CDA is a growing focus of a large part of the healthcare industry and this growth is likely to continue for some time. HL7 Version 3 forms the underlying semantics of CDA and continues to provide semantics for FHIR though less obtrusively. V3 messaging will continue to be used where it has been adopted. All HL7 standards will continue to be maintained as long as the implementation community requires. HL7 will also be responsive to industry needs through the provision of mappings and profiles to ease FHIR migration, particularly from widely used implementation guides. |
***'''When will it be available? ''' | ***'''When will it be available? ''' | ||
| − | ***:FHIR is now available as a Draft Standard for Trial Use. After a period of trial use to vet the specification, HL7 will develop FHIR as a full normative specification. | + | ***:FHIR has been exercised through many international connectathons and has been experimented with by over 50 organizations. Several reference implementations and test servers are available. FHIR is now available as a Draft Standard for Trial Use. After a period of trial use to further vet the specification, HL7 will develop FHIR as a full normative specification. |
| + | **Need TSC and/or FMG vetting for authority to make these assertions | ||
| + | **Need implementation references for product brief (Lloyd) | ||
| + | |||
| + | No meeting next week; meet in two weeks. | ||
| + | |||
| + | |||
| + | Adjourned 9:29 AM | ||
| + | |||
| + | |||
| + | |||
| + | |||
<!-- --> | <!-- --> | ||
*FMG update - | *FMG update - | ||
Revision as of 14:30, 18 February 2014
| HL7 TSC FGB Meeting Minutes Location: call 770-657-9270 using code 985371# |
Date: 2014-02-18 Time: 8:00 AM U.S. Eastern | |
| Facilitator: Ron Parker | Note taker(s): Lynn Laakso | |
| Quorum = Chair plus 2 | yes/no | ||||
| Chair/CTO | Members | Members | |||
| x | Ron Parker | George (Woody) Beeler | x | Ewout Kramer | |
| x | John Quinn | Grahame Grieve | regrets | Hugh Glover | |
| x | Lloyd McKenzie | ||||
| observers/guests | Austin Kreisler | ||||
| x | Lynn Laakso, scribe | ||||
| Ken McCaslin | |||||
Agenda
- Roll call -
- Agenda Review
- Approve minutes of 20140204 FGB concall (no quorum 2/11)
- Action Item review:
- M&C new candidate solicitation
- Confirm Grahame OK with staggering his term
- Review FHIR "position statement" - HL7's strategic placement of FHIR in the product lineup, banner text, etc.
- M&C new candidate solicitation
- FMG update -
- FHIR Tooling and Electronic Services Support # 1058 update; guidance on addressing use of profiles and expecting participants appointed to work with the project.
- Profiling tool demo scheduled on FMG call Feb 12
- Methodology update-
- Address methodology on "well-formedness"
- Metrics for DSTU
Minutes
Convened at 8:10 AM
- Agenda Review; Ewout notes that a new chair also needs to be discussed; approved by general consent
- Approve minutes of 20140204 FGB concall (no quorum 2/11) Ron/Ewout moves approval; unanimously approved.
- Action Item review:
- M&C new candidate solicitation - Ron has been pointing interested parties to the FGB wiki and describing the appointment and chair election process. Catherine Hoang of VA (provider), JD Nolen of Cerner, Dave Shaver of Corepoint (vendors). Significant discussion ensued. Further discussion at HIMSS may elicit additional candidates. John won't be at Wednesday morning's panel but will try to get Chuck to mediate some conversations. From FMG, Lorraine has a strong interest in governance as well. Paul Knapp also entertained for experience in governance. Chair time commitment of potentially 5 hrs a week with ARB and FGB responsibility is a significant issue.
- New FGB chair(s) also
- Confirm Grahame OK with staggering his term; not yet
- Review FHIR "position statement" - HL7's strategic placement of FHIR in the product lineup, banner text, etc.
- What is FHIR?
- FHIR® – Fast Health Interoperable Resources (HL7.org/fhir) – is a next generation standards framework created by HL7. FHIR builds upon the learnings from the development and implementation of HL7’s Version 2, Version 3 and CDA® product lines while leveraging the latest web standards and with an emphasis on implementability.
- What improvements does FHIR bring over existing standards?
- FHIR focuses strongly on ease of implementation by using open industry open web standards. It adds support for REST-style architectures used by current cloud, social media, and mobile platforms where exchanging partners will exploit FHIR’s flexibility to match the need for continuous change in these markets. It provides interoperability for the majority of health IT system interface right out-of-the box, yet has a framework for manageably extending and adapting the standard to suit specific needs.
- What will happen to HL7 Version 2, Version 3, and CDA®?
- Version 2 enjoys wide adoption for communication within hospitals and will remain to do so for years to come. CDA is a growing focus of a large part of the healthcare industry and this growth is likely to continue for some time. HL7 Version 3 forms the underlying semantics of CDA and continues to provide semantics for FHIR though less obtrusively. V3 messaging will continue to be used where it has been adopted. All HL7 standards will continue to be maintained as long as the implementation community requires. HL7 will also be responsive to industry needs through the provision of mappings and profiles to ease FHIR migration, particularly from widely used implementation guides.
- When will it be available?
- FHIR has been exercised through many international connectathons and has been experimented with by over 50 organizations. Several reference implementations and test servers are available. FHIR is now available as a Draft Standard for Trial Use. After a period of trial use to further vet the specification, HL7 will develop FHIR as a full normative specification.
- What is FHIR?
- Need TSC and/or FMG vetting for authority to make these assertions
- Need implementation references for product brief (Lloyd)
- M&C new candidate solicitation - Ron has been pointing interested parties to the FGB wiki and describing the appointment and chair election process. Catherine Hoang of VA (provider), JD Nolen of Cerner, Dave Shaver of Corepoint (vendors). Significant discussion ensued. Further discussion at HIMSS may elicit additional candidates. John won't be at Wednesday morning's panel but will try to get Chuck to mediate some conversations. From FMG, Lorraine has a strong interest in governance as well. Paul Knapp also entertained for experience in governance. Chair time commitment of potentially 5 hrs a week with ARB and FGB responsibility is a significant issue.
No meeting next week; meet in two weeks.
Adjourned 9:29 AM
- FMG update -
- FHIR Tooling and Electronic Services Support # 1058 update; guidance on addressing use of profiles and expecting participants appointed to work with the project.
- Profiling tool demo scheduled on FMG call Feb 12
- Methodology update-
- Address methodology on "well-formedness"
- Metrics for DSTU
Next Steps
| Actions (Include Owner, Action Item, and due date) | |||
Next Meeting/Preliminary Agenda Items
|
Back to FHIR_Governance_Board
© 2014 Health Level Seven® International. All rights reserved.
