Difference between revisions of "2016-07-07 Patient Care FHIR Call"
Elaine Ayres (talk | contribs) |
|||
(12 intermediate revisions by 2 users not shown) | |||
Line 52: | Line 52: | ||
|- | |- | ||
<!-- ********add attendee information here *********--> | <!-- ********add attendee information here *********--> | ||
− | | || Elaine Ayres | + | |X || Elaine Ayres |
|colspan="2"| NIH/Department of Clinical Research Informatics | |colspan="2"| NIH/Department of Clinical Research Informatics | ||
|- | |- | ||
− | | | + | | X || Stephen Chu |
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
Line 61: | Line 61: | ||
|colspan="2"| Haas Consulting | |colspan="2"| Haas Consulting | ||
|- | |- | ||
− | | || Rob Hausam | + | |X || Rob Hausam |
|colspan="2"| Hausam Consulting LLC | |colspan="2"| Hausam Consulting LLC | ||
|- | |- | ||
Line 67: | Line 67: | ||
|colspan="2"| Intermountain Healthcare | |colspan="2"| Intermountain Healthcare | ||
|- | |- | ||
− | | || Emma Jones | + | |X || Emma Jones |
|colspan="2"| Allscripts | |colspan="2"| Allscripts | ||
|- | |- | ||
− | | || Russ Leftwich | + | |X || Russ Leftwich |
|colspan="2"| InterSystems | |colspan="2"| InterSystems | ||
|- | |- | ||
Line 85: | Line 85: | ||
|colspan="2"| Telstra Health | |colspan="2"| Telstra Health | ||
|- | |- | ||
− | | || Lloyd McKenzie | + | | X|| Lloyd McKenzie |
|colspan="2"| Gevity (HL7 Canada) | |colspan="2"| Gevity (HL7 Canada) | ||
|- | |- | ||
Line 109: | Line 109: | ||
|colspan="2"| Kaiser Permanente | |colspan="2"| Kaiser Permanente | ||
|- | |- | ||
− | | || Simon Sum | + | |X || Simon Sum |
|colspan="2"| Academy of Nutrition and Dietetics | |colspan="2"| Academy of Nutrition and Dietetics | ||
|- | |- | ||
Line 138: | Line 138: | ||
#Agenda review | #Agenda review | ||
#Approve previous meeting minutes [[2016-06-30_Patient_Care_FHIR_Call]] | #Approve previous meeting minutes [[2016-06-30_Patient_Care_FHIR_Call]] | ||
− | #*'''Motion:''' | + | #*'''Motion:''' Stephen/Rob H. |
#Prior Action Item Follow-up | #Prior Action Item Follow-up | ||
− | # gForge change request | + | #Address workflow changes proposed for "request" and "event" resources |
+ | #Rob H - re allergy and intolerance negation proposal | ||
+ | # gForge change request for questionnaire | ||
==Supporting Information== | ==Supporting Information== | ||
Line 228: | Line 230: | ||
=== Prior Action Item Follow-up === | === Prior Action Item Follow-up === | ||
+ | |||
+ | Did not tackle prior action item list except for Rob H negation work for allergy and intolerance. | ||
+ | |||
+ | Rob displayed is his proposed changes to the allergy and intolerance resource. The proposal is to add a repeating group that includes a + and a - statement such as reacts to or does not react to. The group reviewed the possible approaches to handling negation - e.g. take no action and use current code such as "no known allergies", or adopt the repeating group approach or add the repeating group as an extension. | ||
+ | |||
+ | The group agreed that Rob should go ahead and add his proposed repeating group approach to the core resource prior to the deadline. This will allow comment during the ballot cycle as well as allow implementers to test. | ||
+ | |||
+ | |||
+ | ===Work Flow discussion for Event and Request=== | ||
+ | |||
+ | The group reviewed the proposal to add consistent data elements to resources which are used to capture requests (orders) and events (responses to requests). Patient Care has the following resources that were considered as a part of this proposal: | ||
+ | |||
+ | *ClinicalImpression -- Event | ||
+ | *Communication -- Event | ||
+ | *Procedure -- Event | ||
+ | *Condition -- Event | ||
+ | *FamilyMemberHistory -- Event | ||
+ | *QuestionnaireResponse -- Event | ||
+ | *CarePlan -- Request | ||
+ | *CommunicationRequest -- Request | ||
+ | *ProcedureRequest -- Request | ||
+ | *ReferralRequest -- Request | ||
+ | |||
+ | The group considered the proposal for the change to include standard data elements to these resources as per the suggestions of the Work Flow group. | ||
+ | The outcome of this discussion is captured in this GFORGE item: http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10293&start=0 | ||
=== gForge Change Requests === | === gForge Change Requests === | ||
+ | |||
+ | The group addressed one change request related to the questionnaire resource to support the work of the ONC SDC initiative: | ||
+ | |||
+ | GFORGE 10289: http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10289&start=0 | ||
+ | |||
+ | Lloyd announced that he had reviewed remaining change requests and will have a block vote for some of the outstanding items during the call on 7/14/16. | ||
=== Adjourn === | === Adjourn === | ||
− | Adjourned at | + | Adjourned at 6:40 PM ET |
==Meeting Outcomes== | ==Meeting Outcomes== | ||
Line 249: | Line 282: | ||
| width="100%" align="left" style="background:#f0f0f0;"|'''Actions''' '' | | width="100%" align="left" style="background:#f0f0f0;"|'''Actions''' '' | ||
− | * | + | * Review GFORGE items for block vote on 7/14/16 |
− | |||
− | |||
|- | |- |
Latest revision as of 01:51, 8 July 2016
Contents
Meeting Information
Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2016-07-07 Time: 5-6:30pm ET | ||
Facilitator | Elaine Ayres | Note taker(s) | Elaine Ayres |
Attendee | Name | Affiliation
| |
X | Elaine Ayres | NIH/Department of Clinical Research Informatics | |
X | Stephen Chu | ||
Eric Haas | Haas Consulting | ||
X | Rob Hausam | Hausam Consulting LLC | |
Laura Heermann-Langford | Intermountain Healthcare | ||
X | Emma Jones | Allscripts | |
X | Russ Leftwich | InterSystems | |
Jay Lyle | Ockham Information Services LLC, VA | ||
Sarah Maulden | VA | ||
Jim McClay | Univ of Nebraska Medical Center | ||
Russell McDonell | Telstra Health | ||
X | Lloyd McKenzie | Gevity (HL7 Canada) | |
Larry McKnight | Cerner | ||
Michelle M Miller | Cerner | ||
Lisa Nelson | Life Over Time Solutions | ||
Viet Nguyen | Lockheed Martin, Systems Made Simple | ||
M'Lynda Owens | Cognosante | ||
Craig Parker | Intermountain Healthcare | ||
Scott Robertson | Kaiser Permanente | ||
X | Simon Sum | Academy of Nutrition and Dietetics | |
Iona Thraen | Dept of Veterans Affairs | ||
Quorum Requirements Met: yes |
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes 2016-06-30_Patient_Care_FHIR_Call
- Motion: Stephen/Rob H.
- Prior Action Item Follow-up
- Address workflow changes proposed for "request" and "event" resources
- Rob H - re allergy and intolerance negation proposal
- gForge change request for questionnaire
Supporting Information
STU 3 Timeline
- Wed, June 1
- All resource and IG proposals for STU3 have been completed, reviewed by WG and submitted
- Connectathon tracks for Sept have been proposed
- Feedback on gForge submitted to FMG
- Sun, July 17 - Substantive content freeze for ballot -- core resources
- Sun, July 24 - Total content freeze, start of QA
- Wed, Aug 10 (midnight) - All QA changes applied
- Fri, Aug 12 - FHIR ballot opens
- Fri, Sept 12 - FHIR ballot closes
- Fri, Sept 16 - FHIR triage complete and ballot content loaded to gForge (or alternate)
- Sept 17-23 - Baltimore WGM
- Sun, Dec 11
- Reconciliation complete/substantive changes applied
- Just over 10 weeks
- Will re-evaluate at Baltimore based on volume of ballot comments
- Dec 31 - Publish
FHIR Maturity Levels
- Level 3 requires the artifact has been verified by the work group as meeting the DSTU_2_QA_guidelines and has been subject to a round of formal balloting; has at least 10 implementer comments recorded in the tracker drawn from at least 3 organizations resulting in at least one substantive change
- Substantive changes (element names, sort order, vocabulary bindings, etc.) need to be applied by ballot freeze (Aug 10).
- Unapplied QA checklist changes can be logged as ballot issues to be applied Sept-Dec. Substantive changes after ballot should be driven by ballot.
- Non-substantive changes are fine
- Level 2 requires artifact has been tested and successfully exchanged between at least three independently developed systems leveraging at least 80% of the core data elements using semi-realistic data and scenarios based on at least one of the declared scopes of the resource (e.g. at a connectathon). These interoperability results must have been reported to and accepted by the FMG.
Resource |
Current FMM Level | Goal FMM Level | QA Status | QA Reviewer | Implementation | Comments |
AllergyIntolerance | 1 | 3 | Rob | Argonaut | ||
Condition | 2 | 3 | PCWG | Argonaut | ||
Procedure | 1 | 3 | Argonaut | |||
CarePlan | 1 | 3 | Argonaut | |||
Goal | 1 | 3 | ||||
QuestionnaireResponse | 2 | 2 | Lloyd | Lloyd will QA to get to level 3 | ||
Questionnaire | 0 | 2 | Lloyd | Lloyd will QA to get to level 3 | ||
CareTeam | 0 | 2 | NA | NA | Aggressive goal (e.g. whether we'll get the implementations needed) | |
FamilyMemberHistory | 1 | 2 | NA | NA | Aggressive goal (e.g. whether we'll get the implementations needed) | |
ClinicalImpression | 0 | 1 | NA | NA | ||
ReferralRequest | 1 | 1 | NA | NA | ||
ProcedureRequest | 1 | 1 | NA | NA | ||
Linkage | 0 | 1 | NA | NA | ||
Flag | 1 | 1 | NA | NA | ||
Communication | 1 | 1 | NA | NA | ||
CommunicationRequest | 1 | 1 | NA | NA |
Note: Bold denotes top 20 resource based on survey
Note: Contraindication and Risk Assessment are owned by CDS, not Patient Care
Minutes
Prior Action Item Follow-up
Did not tackle prior action item list except for Rob H negation work for allergy and intolerance.
Rob displayed is his proposed changes to the allergy and intolerance resource. The proposal is to add a repeating group that includes a + and a - statement such as reacts to or does not react to. The group reviewed the possible approaches to handling negation - e.g. take no action and use current code such as "no known allergies", or adopt the repeating group approach or add the repeating group as an extension.
The group agreed that Rob should go ahead and add his proposed repeating group approach to the core resource prior to the deadline. This will allow comment during the ballot cycle as well as allow implementers to test.
Work Flow discussion for Event and Request
The group reviewed the proposal to add consistent data elements to resources which are used to capture requests (orders) and events (responses to requests). Patient Care has the following resources that were considered as a part of this proposal:
- ClinicalImpression -- Event
- Communication -- Event
- Procedure -- Event
- Condition -- Event
- FamilyMemberHistory -- Event
- QuestionnaireResponse -- Event
- CarePlan -- Request
- CommunicationRequest -- Request
- ProcedureRequest -- Request
- ReferralRequest -- Request
The group considered the proposal for the change to include standard data elements to these resources as per the suggestions of the Work Flow group. The outcome of this discussion is captured in this GFORGE item: http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10293&start=0
gForge Change Requests
The group addressed one change request related to the questionnaire resource to support the work of the ONC SDC initiative:
GFORGE 10289: http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10289&start=0
Lloyd announced that he had reviewed remaining change requests and will have a block vote for some of the outstanding items during the call on 7/14/16.
Adjourn
Adjourned at 6:40 PM ET
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.