This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2017-02-23 Patient Care FHIR Call"
Jump to navigation
Jump to search
(Created page with "{{subst::Patient_Care_FHIR_Call_Template}}") |
|||
| (25 intermediate revisions by 2 users not shown) | |||
| Line 25: | Line 25: | ||
https://cerner.webex.com/cerner/j.php?MTID=macd64a688fdc3410ab4178adab5820fb</nowiki> | https://cerner.webex.com/cerner/j.php?MTID=macd64a688fdc3410ab4178adab5820fb</nowiki> | ||
<!-- ******** CHANGE Date and Time ON NEXT LINE **********************--> | <!-- ******** CHANGE Date and Time ON NEXT LINE **********************--> | ||
| − | | width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''Date: 2017- | + | | width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''Date: 2017-02-23'''<br/> '''Time: 5-6:30pm ET''' |
|- | |- | ||
<!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | <!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | ||
| Line 53: | Line 53: | ||
|- | |- | ||
<!-- ********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 | ||
|- | |- | ||
| Line 59: | Line 59: | ||
|colspan="2"| | |colspan="2"| | ||
|- | |- | ||
| − | | | + | | X || Stephen Chu |
|colspan="2"| The Australian Digital Health Agency (ADHA) | |colspan="2"| The Australian Digital Health Agency (ADHA) | ||
|- | |- | ||
| Line 65: | Line 65: | ||
|colspan="2"| EMI Advisors LLC | |colspan="2"| EMI Advisors LLC | ||
|- | |- | ||
| − | | || Eric Haas | + | | X|| Eric Haas |
|colspan="2"| Haas Consulting | |colspan="2"| Haas Consulting | ||
|- | |- | ||
| − | | || Rob Hausam | + | |X || Rob Hausam |
|colspan="2"| Hausam Consulting LLC | |colspan="2"| Hausam Consulting LLC | ||
|- | |- | ||
| Line 74: | Line 74: | ||
|colspan="2"| Intermountain Healthcare | |colspan="2"| Intermountain Healthcare | ||
|- | |- | ||
| − | | || Emma Jones | + | | X|| Emma Jones |
|colspan="2"| Allscripts | |colspan="2"| Allscripts | ||
|- | |- | ||
| Line 95: | Line 95: | ||
|colspan="2"| Cerner | |colspan="2"| Cerner | ||
|- | |- | ||
| − | | | + | | X || Michelle M Miller |
|colspan="2"| Cerner | |colspan="2"| Cerner | ||
|- | |- | ||
| Line 110: | Line 110: | ||
|colspan="2"| Intermountain Healthcare | |colspan="2"| Intermountain Healthcare | ||
|- | |- | ||
| − | | || Joe Quinn | + | | X|| Joe Quinn |
|colspan="2"| Optum | |colspan="2"| Optum | ||
|- | |- | ||
| Line 144: | Line 144: | ||
<!-- ***** Delete instructions and fill in agenda items ON NEXT LINES ****--> | <!-- ***** Delete instructions and fill in agenda items ON NEXT LINES ****--> | ||
#Agenda review | #Agenda review | ||
| − | #Approve previous meeting minutes | + | #Approve previous meeting minutes [[2017-02-16_Patient_Care_FHIR_Call]] |
| − | #*'''Motion:''' | + | #*'''Motion:''' Emma/Stephen |
#Prior Action Item Follow-up | #Prior Action Item Follow-up | ||
# gForge change request | # gForge change request | ||
| Line 198: | Line 198: | ||
<!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | <!-- **** Delete instructions and fill in minutes ON NEXT LINES ******--> | ||
| − | === | + | === gForge Change Requests === |
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12868 GF#12868] Linkage QA issues that Lloyd pre-applied | ||
| − | === | + | === STU3 Publication TO DOs === |
| + | * Replacing the workflow "planned change" text with "This resource is an event resource from a FHIR workflow perspective - see Workflow" -- is there a preference about making this the first or last sentence in the Scope and Usage sections? '''Motion Eric/Joe: Add sentence at the beginning of "Scope and Usage" 5-1-0 | ||
| + | * Does Patient Care want Linkage to be FMM=0 or FMM=1? '''Keep as FMM=0''' | ||
| + | * Linkage/Person boundaries need to be updated -- '''add Boundaries to say "The Person resource should be used to represent a person independent of a specific health-related context. Linkage can be used for all other use cases.''' | ||
| + | * More examples needed for resolved trackers: | ||
| + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8604 GF#8604] FamilyMemberHistory needs explanation of how to record Patient's own history (Russell McDonell) Applied note, but not example <p> Will add a section to FamilyMemberHistory noting that a List representing a patient's "family history" can include Conditions and Observations that capture "family-history" relevant assertions about the patient themselves that would typically be captured as part of a family history. Â Will ensure at least one family history example instance includes such content.</p> <p> add reference to | ||
| + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9795 GF#9795] Create examples that are principally narrative (Lloyd McKenzie) Resolved - Change required <p> Add examples for CarePlan and Procedure that are primarily narrative with minimal if any discrete data.</p> <p> Profiles can further communicate when and if it is appropriate or encouraged to use discrete data.</p> | ||
| + | * Remaining gForges that need more attention | ||
| + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=5546 GF#5546] Clarify Timing - Condition vs. Concern (Lawrence McKnight) We haven't done the Motion 1 analysis; Motion 2 has been addressed as part of [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10090 GF#10090]. <p> Motion 1: Need an analysis of the distinction of data attributes in condition vs. concern to determine if new concern resource is needed. </p> <p> Motion 2:  Clarify in the FHIR specification that this resource is to be used as a point in time observation of a condition (event). Larry/David  11-8-3</p> | ||
| + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7057 GF#7057] 2015May core #123 - Update RIM and CDA mappings (Brett Marquard) - We only prioritized RIM mappings for FMM = 3 resources <p> Will update RIM mappings for all PC resources. Â C-CDA mappings will be done if time allows - they really belong in the C-CDA on FHIR profile.</p> | ||
| + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10662 GF#10662] Clarify how medical history should be handled (Grahame Grieve) Grahame didn't think our resolution addressed everything.... <p> The List resource already includes guidance on medical history as follows:</p> <p> "The List resource is a flat possibly ordered collection of records. List resources are used in many places including allergies medications alerts family history <strong> medical history</strong> etc. List resources can be used to support patient-specific clinical lists as well as lists that manage workflows such as tracking patients managing teaching cases etc. Resources supported by the List resource can be homogenous consisting of only one type of resource (e.g. allergy list); as well as <strong>heterogeneous </strong> containing a variety of resources (e.g. a problem list including Conditions, AllergyIntolerances, Procedures etc.)."</p> <p> List will have more examples included per <a href="http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11473">http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11473</a></p> <p> Within the scope of Condition expand usage section to include example of condition as a result of a procedure:</p> <p> Amputee-BKA could be a condition following a surgical procedure of amputation</p> | ||
| + | * QA Volunteers [https://fhirblog.com/2017/02/03/fhir-qa/] -- Elaine, Emma (+ Michelle and Rob H) | ||
=== Adjourn === | === Adjourn === | ||
| − | Adjourned at | + | Adjourned at 6:30pm Eastern. |
==Meeting Outcomes== | ==Meeting Outcomes== | ||
Latest revision as of 23:34, 23 February 2017
Contents
Meeting Information
| Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2017-02-23 Time: 5-6:30pm ET | ||
| Facilitator | Michelle M Miller | Note taker(s) | Michelle M Miller |
| Attendee | Name | Affiliation
| |
| X | Elaine Ayres | NIH/Department of Clinical Research Informatics | |
| Pushpalatha Bhat | |||
| X | Stephen Chu | The Australian Digital Health Agency (ADHA) | |
| Evelyn Gallego | EMI Advisors LLC | ||
| X | Eric Haas | Haas Consulting | |
| X | Rob Hausam | Hausam Consulting LLC | |
| Laura Heermann-Langford | Intermountain Healthcare | ||
| X | Emma Jones | Allscripts | |
| Russ Leftwich | InterSystems | ||
| Tony Little | Optum 360 | ||
| Jay Lyle | Ockham Information Services LLC, VA | ||
| Russell McDonell | Telstra Health | ||
| Lloyd McKenzie | Gevity (HL7 Canada) | ||
| Larry McKnight | Cerner | ||
| X | 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 | ||
| X | Joe Quinn | Optum | |
| Simon Sum | Academy of Nutrition and Dietetics | ||
| Iona Thraen | Dept of Veterans Affairs | ||
| Serafina Versaggi | Dept of Veterans Affairs | ||
| Quorum Requirements Met: yes | |||
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes 2017-02-16_Patient_Care_FHIR_Call
- Motion: Emma/Stephen
- Prior Action Item Follow-up
- gForge change request
Supporting Information
STU 3 Timeline
From FHIR_Ballot_Prep
- Sun. Feb. 19 Publication substantive resource freeze
- Sun. Feb 26 Publication total freeze
- Mon. Feb 27 QA period opens
- Tue. Feb 28 FMM QA spreadsheet updated for all WG resources
- Sun. Mar. 13 QA period closes
- Sun. Mar. 20 All QA applied
The "following week" STU 3 is published!
FHIR Maturity Levels
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
Target FMM levels for STU3 publication
- AllergyIntolerance = 3
- Condition = 3
- Procedure = 3
- CarePlan = 1
- Goal = 1
- CareTeam = 1
- FamilyMemberHistory = 1
- ReferralRequest = 1
- Flag = 1
- Communication = 1
- CommunicationRequest =1
- ClinicalImpression = 0
- Linkage = 0
STU3 Action Items
- Review Tracker Issues - https://docs.google.com/a/lmckenzie.com/uc?id=0B285oCHDUr09Mzh3b09rMFhEV1E
- Resolve QA Warnings to have resource FMM > 0
- Resolve QA Information messages to achieve FMM = 3
- Update QA checklist for resources that we want to be FMM = 3
- Apply changes (all "substantive" changes have been applied, except workflow patterns)
Minutes
gForge Change Requests
- GF#12868 Linkage QA issues that Lloyd pre-applied
STU3 Publication TO DOs
- Replacing the workflow "planned change" text with "This resource is an event resource from a FHIR workflow perspective - see Workflow" -- is there a preference about making this the first or last sentence in the Scope and Usage sections? Motion Eric/Joe: Add sentence at the beginning of "Scope and Usage" 5-1-0
- Does Patient Care want Linkage to be FMM=0 or FMM=1? Keep as FMM=0
- Linkage/Person boundaries need to be updated -- add Boundaries to say "The Person resource should be used to represent a person independent of a specific health-related context. Linkage can be used for all other use cases.
- More examples needed for resolved trackers:
- GF#8604 FamilyMemberHistory needs explanation of how to record Patient's own history (Russell McDonell) Applied note, but not example
Will add a section to FamilyMemberHistory noting that a List representing a patient's "family history" can include Conditions and Observations that capture "family-history" relevant assertions about the patient themselves that would typically be captured as part of a family history. Â Will ensure at least one family history example instance includes such content.
add reference to
- GF#9795 Create examples that are principally narrative (Lloyd McKenzie) Resolved - Change required
Add examples for CarePlan and Procedure that are primarily narrative with minimal if any discrete data.
Profiles can further communicate when and if it is appropriate or encouraged to use discrete data.
- GF#8604 FamilyMemberHistory needs explanation of how to record Patient's own history (Russell McDonell) Applied note, but not example
- Remaining gForges that need more attention
- GF#5546 Clarify Timing - Condition vs. Concern (Lawrence McKnight) We haven't done the Motion 1 analysis; Motion 2 has been addressed as part of GF#10090.
Motion 1: Need an analysis of the distinction of data attributes in condition vs. concern to determine if new concern resource is needed.Â
Motion 2:  Clarify in the FHIR specification that this resource is to be used as a point in time observation of a condition (event). Larry/David  11-8-3
- GF#7057 2015May core #123 - Update RIM and CDA mappings (Brett Marquard) - We only prioritized RIM mappings for FMM = 3 resources
Will update RIM mappings for all PC resources. Â C-CDA mappings will be done if time allows - they really belong in the C-CDA on FHIR profile.
- GF#10662 Clarify how medical history should be handled (Grahame Grieve) Grahame didn't think our resolution addressed everything....
The List resource already includes guidance on medical history as follows:
"The List resource is a flat possibly ordered collection of records. List resources are used in many places including allergies medications alerts family history medical history etc. List resources can be used to support patient-specific clinical lists as well as lists that manage workflows such as tracking patients managing teaching cases etc. Resources supported by the List resource can be homogenous consisting of only one type of resource (e.g. allergy list); as well as heterogeneous containing a variety of resources (e.g. a problem list including Conditions, AllergyIntolerances, Procedures etc.)."
List will have more examples included per <a href="http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11473">http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11473</a>
Within the scope of Condition expand usage section to include example of condition as a result of a procedure:
Amputee-BKA could be a condition following a surgical procedure of amputation
- GF#5546 Clarify Timing - Condition vs. Concern (Lawrence McKnight) We haven't done the Motion 1 analysis; Motion 2 has been addressed as part of GF#10090.
- QA Volunteers [1] -- Elaine, Emma (+ Michelle and Rob H)
Adjourn
Adjourned at 6:30pm Eastern.
Meeting Outcomes
| Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.
