This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20180605 US Realm SC Call"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 37: | Line 37: | ||
===============================================================================---> | ===============================================================================---> | ||
|- | |- | ||
| − | | || Calvin Beebe || ||Keith Boone|| || Hans Buitendijk | + | |x || Calvin Beebe || ||Keith Boone|| || Hans Buitendijk |
|- | |- | ||
| − | | ||Lorraine Constable || ||Johnathan Coleman|| ||Ed Hammond | + | | ||Lorraine Constable || ||Johnathan Coleman||x ||Ed Hammond |
|- | |- | ||
| − | | ||Tony Julian|| ||Paul Knapp|| ||Austin Kreisler | + | | ||Tony Julian||x ||Paul Knapp||x ||Austin Kreisler |
|- | |- | ||
| − | | ||Brett Marquard|| ||Ken McCaslin|| ||Nancy Orvis | + | |x ||Brett Marquard|| ||Ken McCaslin||x ||Nancy Orvis |
|- | |- | ||
| − | | ||Brian Pech|| ||Wayne Kubick|| ||Christol Green | + | | ||Brian Pech|| x||Wayne Kubick||x ||Christol Green |
|- | |- | ||
| − | | | + | | x ||Sandra Stuart||. ||Pat Van Dyke||. || Craig Parker |
|- | |- | ||
| − | | ||Danielle Friend|| | + | |x ||Danielle Friend||x||Eric Haas||. || Jenni Syed |
|- | |- | ||
| − | | | + | | x ||Steve Posnak||. ||David Susanto||. ||John Roberts |
|- | |- | ||
| border="1" cellpadding="2" colspan="6" align="left"|'''Visitor/ Name''' | | border="1" cellpadding="2" colspan="6" align="left"|'''Visitor/ Name''' | ||
|- | |- | ||
| − | | || | + | |x ||Bo Borgnakke||x || Sarah Gaunt|| x||Richard Ballew |
| + | |- | ||
| + | |x || Nagesh Bagyam||x || Farrah Darbouze||x ||Rachel Roan | ||
| + | |||
|- | |- | ||
|colspan="6" style="background:#f0f0f0;"| | |colspan="6" style="background:#f0f0f0;"| | ||
| Line 86: | Line 89: | ||
===Minutes=== | ===Minutes=== | ||
| + | *Agenda review | ||
| + | *Review notes from [[20180515 US Realm SC WGM]] | ||
| + | *Review Items | ||
| + | **[https://gforge.hl7.org/gf/download/trackeritem/17262/16588/HL7_Project_Scope_Statement_Gaps_In_Care_1.docx HL7 CDA R2 Implementation Guide: Gaps in Care Reporting PSS] | ||
| + | ***Bo Borgnakke describes project. Ed asks if Vocabulary should be involved. Bo states that since they’re not building from scratch, they haven’t involved them. Question about why security risks is checked yes. Question why section 5 has create a new standard if this is an implementation guide. Implementation Guide should be checked instead. Ed suggests that perhaps it’s actually Informative. Paul suggests making updates and bringing it back next week after some cleanup. Need more clarity on what this project is doing. | ||
| + | ****MOTION that the document be brought back next week after edits: Paul/Calvin | ||
| + | ****VOTE: All in favor | ||
| + | **[https://gforge.hl7.org/gf/download/trackeritem/17263/16589/HL7%20Project%20Scope%20Statement%20FHIR%20Implementation%20Guide%20for%20Exchange%20of%20Data%20for%20Quality%20Measures%2020180516%20V1%204.docx FHIR Implementation Guide for Data Exchange for Quality Measures] | ||
| + | ***Bot Dieterle here to represent project. This is from a Da Vinci case dealing with 30 day medication representation. Ed: Seems to be a huge scope of activities. Shouldn’t the Pharmacy WG be involved? Bob states that the PSS was written for a broad scope beyond the first listed deliverable. The intent is to go back and address all the things antecedent to the attestation. Ed: When I’m looking at the implementers – have those groups committed to do this? Bob responds that they have committed to implementation. Ed asks about timeline. For STU 3 it will be fall of this year, for 4 it will be next year. Ed: Dave Hamill said ARB would have to approve this. Bob agrees and will update document. Brett asks how this interacts with existing profiles? Bob states they’d use as much as the argonaut and common core as they can. Brett states that should be listed as well as what artifacts they expect that they’ll have to develop. Scope is unclear regarding final pieces. Ed: Can’t tell what you’re going to produce at the end of this. Bob: We’re not sure how far we’re going to go in the framework. Paul asks if they’re using Argonaut profiles, or US Core? Brett: Argonaut is STU2, US Core is 3. Suggests adding a description of that. Eric: Need to identify repository location. | ||
| + | ****MOTION to approve with suggested edits and updates: Paul/Christol | ||
| + | ****VOTE: All in favor | ||
| + | **[https://gforge.hl7.org/gf/download/trackeritem/17264/16590/HL7%20Project%20Scope%20Statement%20FHIR%20Implementation%20Guide%20for%20Coverage%20Requirements%20Discovery%20%2020180516%20V1%204.docx FHIR Implementation Guide for Coverage Requirements Discovery] | ||
| + | ***Bob also here to describe this project. Gives providers access to payer approval requirements, documentation and rules. | ||
| + | ****MOTION to approve: Paul/Ed | ||
| + | ****VOTE: All in favor | ||
| + | **[https://gforge.hl7.org/gf/download/trackeritem/17308/16605/CRN_2018_HL7_Sep_WG_PSS%205-23-2018.docx Women's Health Technology Coordinated Registry Network] | ||
| + | ***Dragon here to present project. Ed: Increasingly we have groups focusing on creating data elements – need to make sure these all get into a common set. Note that they will need to move to an HL7-managed repository. | ||
| + | ***MOTION to approve: Paul/Calvin | ||
| + | ***VOTE: Eric abstains. Remaining in favor. | ||
| + | **[https://gforge.hl7.org/gf/download/trackeritem/17309/16606/CDMH-HL7-PSS-05-17-2018_BRR_Approved.docx Common Data Model Harmonization (CDMH) - FHIR Implementation Guide] | ||
| + | ***ACTION: Add to next week | ||
| − | + | Discussion: | |
| + | *Review of [http://www.hl7.org/Special/Committees/usrealm/overview.cfm Mission and Charter] | ||
| + | **Carry forward | ||
===Meeting Outcomes=== | ===Meeting Outcomes=== | ||
Latest revision as of 19:34, 5 June 2018
back to US_Realm_Steering_Committee
back to US_Realm_Steering_Committee_Conference_Calls
| US Realm Steering Committee Call Agenda/Minutes |
Date: 2018-06-05 Time: 1 PM Eastern | ||
| Co-Chairs | Ed/Brett | Note taker(s) | Anne |
| Attendee / Name | |||||
| x | Calvin Beebe | Keith Boone | Hans Buitendijk | ||
| Lorraine Constable | Johnathan Coleman | x | Ed Hammond | ||
| Tony Julian | x | Paul Knapp | x | Austin Kreisler | |
| x | Brett Marquard | Ken McCaslin | x | Nancy Orvis | |
| Brian Pech | x | Wayne Kubick | x | Christol Green | |
| x | Sandra Stuart | . | Pat Van Dyke | . | Craig Parker |
| x | Danielle Friend | x | Eric Haas | . | Jenni Syed |
| x | Steve Posnak | . | David Susanto | . | John Roberts |
| Visitor/ Name | |||||
| x | Bo Borgnakke | x | Sarah Gaunt | x | Richard Ballew |
| x | Nagesh Bagyam | x | Farrah Darbouze | x | Rachel Roan |
| Quorum: Chair + 7 | |||||
Agenda
Administrivia
- Agenda review
- Review notes from 20180515 US Realm SC WGM
- Review Items
- HL7 CDA R2 Implementation Guide: Gaps in Care Reporting PSS
- FHIR Implementation Guide for Data Exchange for Quality Measures
- FHIR Implementation Guide for Coverage Requirements Discovery
- Women's Health Technology Coordinated Registry Network
- Common Data Model Harmonization (CDMH) - FHIR Implementation Guide
Discussion:
- Review of Mission and Charter
Minutes
- Agenda review
- Review notes from 20180515 US Realm SC WGM
- Review Items
- HL7 CDA R2 Implementation Guide: Gaps in Care Reporting PSS
- Bo Borgnakke describes project. Ed asks if Vocabulary should be involved. Bo states that since they’re not building from scratch, they haven’t involved them. Question about why security risks is checked yes. Question why section 5 has create a new standard if this is an implementation guide. Implementation Guide should be checked instead. Ed suggests that perhaps it’s actually Informative. Paul suggests making updates and bringing it back next week after some cleanup. Need more clarity on what this project is doing.
- MOTION that the document be brought back next week after edits: Paul/Calvin
- VOTE: All in favor
- Bo Borgnakke describes project. Ed asks if Vocabulary should be involved. Bo states that since they’re not building from scratch, they haven’t involved them. Question about why security risks is checked yes. Question why section 5 has create a new standard if this is an implementation guide. Implementation Guide should be checked instead. Ed suggests that perhaps it’s actually Informative. Paul suggests making updates and bringing it back next week after some cleanup. Need more clarity on what this project is doing.
- FHIR Implementation Guide for Data Exchange for Quality Measures
- Bot Dieterle here to represent project. This is from a Da Vinci case dealing with 30 day medication representation. Ed: Seems to be a huge scope of activities. Shouldn’t the Pharmacy WG be involved? Bob states that the PSS was written for a broad scope beyond the first listed deliverable. The intent is to go back and address all the things antecedent to the attestation. Ed: When I’m looking at the implementers – have those groups committed to do this? Bob responds that they have committed to implementation. Ed asks about timeline. For STU 3 it will be fall of this year, for 4 it will be next year. Ed: Dave Hamill said ARB would have to approve this. Bob agrees and will update document. Brett asks how this interacts with existing profiles? Bob states they’d use as much as the argonaut and common core as they can. Brett states that should be listed as well as what artifacts they expect that they’ll have to develop. Scope is unclear regarding final pieces. Ed: Can’t tell what you’re going to produce at the end of this. Bob: We’re not sure how far we’re going to go in the framework. Paul asks if they’re using Argonaut profiles, or US Core? Brett: Argonaut is STU2, US Core is 3. Suggests adding a description of that. Eric: Need to identify repository location.
- MOTION to approve with suggested edits and updates: Paul/Christol
- VOTE: All in favor
- Bot Dieterle here to represent project. This is from a Da Vinci case dealing with 30 day medication representation. Ed: Seems to be a huge scope of activities. Shouldn’t the Pharmacy WG be involved? Bob states that the PSS was written for a broad scope beyond the first listed deliverable. The intent is to go back and address all the things antecedent to the attestation. Ed: When I’m looking at the implementers – have those groups committed to do this? Bob responds that they have committed to implementation. Ed asks about timeline. For STU 3 it will be fall of this year, for 4 it will be next year. Ed: Dave Hamill said ARB would have to approve this. Bob agrees and will update document. Brett asks how this interacts with existing profiles? Bob states they’d use as much as the argonaut and common core as they can. Brett states that should be listed as well as what artifacts they expect that they’ll have to develop. Scope is unclear regarding final pieces. Ed: Can’t tell what you’re going to produce at the end of this. Bob: We’re not sure how far we’re going to go in the framework. Paul asks if they’re using Argonaut profiles, or US Core? Brett: Argonaut is STU2, US Core is 3. Suggests adding a description of that. Eric: Need to identify repository location.
- FHIR Implementation Guide for Coverage Requirements Discovery
- Bob also here to describe this project. Gives providers access to payer approval requirements, documentation and rules.
- MOTION to approve: Paul/Ed
- VOTE: All in favor
- Bob also here to describe this project. Gives providers access to payer approval requirements, documentation and rules.
- Women's Health Technology Coordinated Registry Network
- Dragon here to present project. Ed: Increasingly we have groups focusing on creating data elements – need to make sure these all get into a common set. Note that they will need to move to an HL7-managed repository.
- MOTION to approve: Paul/Calvin
- VOTE: Eric abstains. Remaining in favor.
- Common Data Model Harmonization (CDMH) - FHIR Implementation Guide
- ACTION: Add to next week
- HL7 CDA R2 Implementation Guide: Gaps in Care Reporting PSS
Discussion:
- Review of Mission and Charter
- Carry forward
Meeting Outcomes
| Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2018 Health Level Seven® International. All rights reserved
