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

Difference between revisions of "2017-02-02 Patient Care FHIR Call"

From HL7Wiki
Jump to navigation Jump to search
Line 184: Line 184:
 
* Block Vote (see below) scheduled for Feb 2, 2017 for low hanging fruit, i.e. non-ballot comments
 
* Block Vote (see below) scheduled for Feb 2, 2017 for low hanging fruit, i.e. non-ballot comments
 
* Apply changes (all "substantive" changes have been applied, except allergy, care team invariant, and workflow patterns)
 
* Apply changes (all "substantive" changes have been applied, except allergy, care team invariant, and workflow patterns)
−
 
−
=== 16 Deferred Ballot Comments ===
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7185 GF#7185] 2015May core #244  - ClinicalImpression is poorly thought out (Clem McDonald) Waiting for Input
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10387 GF#10387] CommunicationRequest needs ability to describe the location that the communication is about (John Moehrke)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10621 GF#10621] QA 4a: Consider whether CarePlan.activity.detail.category should be bound to an external code system (Michelle Miller) 
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10622 GF#10622] QA 4a: Consider whether Goal.category should be bound to codes from an external code system (Michelle Miller)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10635 GF#10635] QA 5a: Resource references exist in both directions for Condition and ClinicalImpression (Michelle Miller) -- deferred, but asking for MnM exemption
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11026 GF#11026] Relationship between Condition and Observation - 2016-09 core #45  (Jay Lyle)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11209 GF#11209] Feedback on ClinicalImpression - 2016-09 core #363  (Riki Merrick)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11355 GF#11355] CarePlan category value set is out of date or wrong - 2016-09 core #513  (Robert McClure)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11357 GF#11357] Re-use the procedure value set instead of wrapping it - 2016-09 core #515  (Robert McClure)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11358 GF#11358] Should not make a new value set ehre - use the Problem value set that also includes Events and SWEC concepts. - 2016-09 core #516  (Robert McClure)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11359 GF#11359] Why only one medication in an activity? And the value set is problematic (but example) - 2016-09 core #517  (Robert McClure)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11354 GF#11354] Substance identified in both AllergyIntolerance.code and reaction.substance is problematic - 2016-09 core #512  (Robert McClure)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11021 GF#11021] Increase cardinality of substance and make certainty relation to substance  not reaction - 2016-09 core #40  (Jay Lyle)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11023 GF#11023] Why isn't AllergyIntolerance.reaction an Observation? - 2016-09 core #42  (Jay Lyle)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11173 GF#11173] CarePlan needs support for reviews - 2016-09 core #327  (Stephen Chu)
 
−
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=11332 GF#11332] Acknowledge Advance Directives as type of Care Plan - 2016-09 core #490  (David Tao)
 
  
 
=== TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3) ===
 
=== TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3) ===
 
* AllergyIntolerance
 
* AllergyIntolerance
−
** Rob Hausam is helping with RIM mappings (clinicalStatus and verificationStatus)
+
** <span style="color:#FF0000"> Rob Hausam </span> is helping with RIM mappings (clinicalStatus and verificationStatus)
−
** Rob Hausam is using data Elaine sent to see if we can curate the SNOMED CT Clinical Findings to a smaller subset.  If not, then we'll update the binding for AllergyIntolerance.reaction.manifestation to use the same valueset-clinical-findings
+
** <span style="color:#FF0000"> Rob Hausam </span> is using data Elaine sent to see if we can curate the SNOMED CT Clinical Findings to a smaller subset.  If not, then we'll update the binding for AllergyIntolerance.reaction.manifestation to use the same valueset-clinical-findings
 
*** Duplicate Valueset Names: manifestation-codes (SNOMED CT Clinical Findings) & clinical-findings (SNOMED CT Clinical Findings)  
 
*** Duplicate Valueset Names: manifestation-codes (SNOMED CT Clinical Findings) & clinical-findings (SNOMED CT Clinical Findings)  
 
*** AllergyIntolerance.reaction.manifestation -- http://build.fhir.org/valueset-manifestation-codes.html  
 
*** AllergyIntolerance.reaction.manifestation -- http://build.fhir.org/valueset-manifestation-codes.html  
Line 212: Line 194:
  
 
* Condition is clean on the QA report!
 
* Condition is clean on the QA report!
−
** QA Checklist:  [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10635 GF#10635] QA 5a: Resource references exist in both directions for Condition and ClinicalImpression (Michelle Miller) -- deferred and asking for MnM exemption
+
** <span style="color:#FF0000"> Discuss </span> QA Checklist:  [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10635 GF#10635] QA 5a: Resource references exist in both directions for Condition and ClinicalImpression (Michelle Miller) -- deferred and asking for MnM exemption -- Lloyd responded saying "make an explicit call-out in the notes section for Condition about the unresolved issue.  That should be sufficient"  Proposed text to add:  "There is an unresolved issue with circular references between Condition and ClinicalImpression, which is due to the low maturity level of ClinicalImpression."
  
−
* Procedure is clean on the QA report!
+
* <span style="color:#008000"> Procedure </span> is clean on the QA report!
  
−
=== MEDIUM Priority -- CareTeam, CarePlan, and Goal -- QA Warnings (desire FMM > 0 means we address all warnings) ===
+
=== HIGH Priority -- CareTeam, CarePlan, and Goal -- QA Warnings (desire FMM > 0 means we address all warnings) ===
  
 
* CarePlan
 
* CarePlan
−
** MnM exemptions requested for element names should be singular (addresses and replaces)
+
** <span style="color:#FF0000"> MnM </span> exemptions requested for element names should be singular (addresses and replaces)
  
 
* Goal
 
* Goal
−
** MnM exemption requested for element names should be singular (addresses)
+
** <span style="color:#FF0000"> MnM </span> exemption requested for element names should be singular (addresses)
−
** PCWG needs to address [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10623 GF#10623]
+
** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10623 GF#10623]
−
*** Goal.description - example binding to a new value set
+
*** <span style="color:#FF0000"> Rob Hausam </span> was going to help with Goal.description - example binding to a new value set
−
*** Goal.target.detail - ask MnM for exemption because target detail is a choice of data types (i.e. Quantity and CodeableConcept could have different value sets) - Observation.value[x] does not show this same QA warning.
+
*** <span style="color:#FF0000"> MnM </span> exemption requested for Goal.target.detail because target detail is a choice of data types (i.e. Quantity and CodeableConcept could have different value sets) - Observation.value[x] does not show this same QA warning.
 +
 
 +
=== MEDIUM Priority -- All other resources (except Linkage and ClinicalImpression) -- QA Warnings (desire FMM > 0 means we address all warnings) ===
 +
 
 +
* <span style="color:#008000"> Flag </span> -- no remaining QA warnings!
 +
 
 +
* <span style="color:#008000"> FamilyMemberHistory </span> -- no remaining QA warnings!
 +
 
 +
* Communication & CommunicationRequest
 +
** Category Need to provide a binding - [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8564 GF#8564]
 +
*** <span style="color:#FF0000"> Rob Hausam </span> will check to see if v3 has existing codes.  If so, use v3.  If not, then add v3 codes: alert, notification, reminder, instruction
 +
 
 +
* ReferralRequest
 +
** <span style="color:#FF0000"> Discuss </span>: Bindings/Value Sets
 +
*** ReferralRequest.type Need to provide a binding
 +
*** ReferralRequest.reason Need to provide a binding
 +
*** pc:ValueSetComparison Duplicate Valueset Names: v2-0284 (v2 Referral Category) & referralcategory (ReferralCategory) (name: [referrals, categories] / [referrals, categories]))
 +
*** pc:ValueSetComparison Duplicate Valueset Names: v2-0283 (v2 Referral Status) & referralstatus (ReferralStatus) (name: [referrals, statuses] / [referrals, statuses]))
 +
** <span style="color:#FF0000"> Discuss </span>: ReferralRequest.description Element has a todo associated with it (This would be a good candidate for a 'markdown' data type.)
 +
** Examples
 +
*** ReferralRequest.context Search Parameter 'ReferralRequest.context' had no found values in any example. Consider reviewing the expression (ReferralRequest.context)
 +
*** ReferralRequest.group-identifier Search Parameter 'ReferralRequest.group-identifier' had no found values in any example. Consider reviewing the expression (ReferralRequest.groupIdentifier)
  
−
=== MEDIUM Priority -- CareTeam, CarePlan, and Goal -- QA Information (desire FMM = 3 means we address all information) ===
+
=== LOW Priority -- CareTeam, CarePlan, and Goal -- QA Information (desire FMM = 3 means we address all information) ===
 
* CareTeam
 
* CareTeam
 
** RIM Mapping
 
** RIM Mapping
Line 245: Line 248:
 
** QA Checklist: [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10621 GF#10621] QA 4a: Consider whether CarePlan.activity.detail.category should be bound to an external code system (Michelle Miller)
 
** QA Checklist: [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10621 GF#10621] QA 4a: Consider whether CarePlan.activity.detail.category should be bound to an external code system (Michelle Miller)
  
−
=== LOW Priority -- All other resources -- QA Warnings (desire FMM > 0 means we address all warnings) ===
+
=== Draft Resources with FMM = 0 -- ClinicalImpression and Linkage ===
−
 
+
* ClinicalImpression -- keep as FMM = 0
−
* ClinicalImpression
 
 
** Stephen Chu will work on examples to cover all elements
 
** Stephen Chu will work on examples to cover all elements
 
*** ClinicalImpression.action Search Parameter 'ClinicalImpression.action' had no found values in any example. Consider reviewing the expression (ClinicalImpression.action)
 
*** ClinicalImpression.action Search Parameter 'ClinicalImpression.action' had no found values in any example. Consider reviewing the expression (ClinicalImpression.action)
Line 253: Line 255:
 
** PCWG:  ClinicalImpression.code Need to provide a binding
 
** PCWG:  ClinicalImpression.code Need to provide a binding
  
−
* Communication & CommunicationRequest
+
* Linkage -- keep as FMM = 0
−
** PCWG:  category Need to provide a binding [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12167 GF#12167] and [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8564 GF#8564]
 
−
*** Check to see if v3 has existing codes.  If so, use v3.  If not, then add v3 codes: alert, notification, reminder, instruction
 
−
** PCWG:  workflow could resolve [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10293 GF#10293]
 
−
*** A resource must have an 'entered in error' status
 
−
*** CommunicationRequest.subject Elements with name 'subject' cannot be a reference to just a patient
 
−
 
 
−
* FamilyMemberHistory
 
−
** PCWG:  FamilyMemberHistory.condition.onset[x] Element has a todo associated with it (Define/find appropriate observation code.)
 
−
 
 
−
* ReferralRequest
 
−
** PCWG: Bindings/Value Sets
 
−
*** ReferralRequest.type Need to provide a binding
 
−
*** ReferralRequest.reason Need to provide a binding
 
−
*** pc:ValueSetComparison Duplicate Valueset Names: v2-0284 (v2 Referral Category) & referralcategory (ReferralCategory) (name: [referrals, categories] / [referrals, categories]))
 
−
*** pc:ValueSetComparison Duplicate Valueset Names: v2-0283 (v2 Referral Status) & referralstatus (ReferralStatus) (name: [referrals, statuses] / [referrals, statuses]))
 
−
** PCWG: ReferralRequest.description Element has a todo associated with it (This would be a good candidate for a 'markdown' data type.)
 
−
** Examples
 
−
*** ReferralRequest.context Search Parameter 'ReferralRequest.context' had no found values in any example. Consider reviewing the expression (ReferralRequest.context)
 
−
*** ReferralRequest.group-identifier Search Parameter 'ReferralRequest.group-identifier' had no found values in any example. Consider reviewing the expression (ReferralRequest.groupIdentifier)
 
−
 
 
−
* Linkage
 
 
** PCWG: Linkage A resource must have an 'entered in error' status
 
** PCWG: Linkage A resource must have an 'entered in error' status
 
** PCWG: Linkage All resources should have an identifier
 
** PCWG: Linkage All resources should have an identifier
 
** PCWG: Linkage.item Element has a todo associated with it (Make this 2..*.)
 
** PCWG: Linkage.item Element has a todo associated with it (Make this 2..*.)
 +
 +
  
 
=== Block Vote (Thurs, Feb 2)===
 
=== Block Vote (Thurs, Feb 2)===

Revision as of 14:34, 31 January 2017



Meeting Information

Patient Care FHIR Resources Conference Call

Location: Conference Call
Phone Number: +1 770-657-9270
Participant Passcode: 943377
WebEx: https://cerner.webex.com/cerner/j.php?MTID=macd64a688fdc3410ab4178adab5820fb

Date: 2017-02-02
Time: 5-6:30pm ET
Facilitator Michelle M Miller Note taker(s) Michelle M Miller
Attendee Name Affiliation


Elaine Ayres NIH/Department of Clinical Research Informatics
Stephen Chu The Australian Digital Health Agency (ADHA)
Evelyn Gallego EMI Advisors LLC
Eric Haas Haas Consulting
Rob Hausam Hausam Consulting LLC
Laura Heermann-Langford Intermountain Healthcare
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
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
Joe Quinn Optum
Simon Sum Academy of Nutrition and Dietetics
Iona Thraen Dept of Veterans Affairs
Serafina Versaggi Dept of Veterans Affairs
Tracey Coleman Allscripts
Amit Popat Epic
Quorum Requirements Met: yes

Agenda

Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes 2017-01-31_Patient_Care_FHIR_Call
    • Motion:
  3. Prior Action Item Follow-up
  4. gForge change request

Supporting Information

STU 3 Timeline

From FHIR_Ballot_Prep

  • Sun. Feb. 5 Ballot reconciliation deadline - All ballot comments must be reconciled, tracker issue report must be clean
  • 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!

Minutes

STU3 Action Items

TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3)

  • AllergyIntolerance
    • Rob Hausam is helping with RIM mappings (clinicalStatus and verificationStatus)
    • Rob Hausam is using data Elaine sent to see if we can curate the SNOMED CT Clinical Findings to a smaller subset. If not, then we'll update the binding for AllergyIntolerance.reaction.manifestation to use the same valueset-clinical-findings
  • Condition is clean on the QA report!
    • Discuss QA Checklist: GF#10635 QA 5a: Resource references exist in both directions for Condition and ClinicalImpression (Michelle Miller) -- deferred and asking for MnM exemption -- Lloyd responded saying "make an explicit call-out in the notes section for Condition about the unresolved issue. That should be sufficient" Proposed text to add: "There is an unresolved issue with circular references between Condition and ClinicalImpression, which is due to the low maturity level of ClinicalImpression."
  • Procedure is clean on the QA report!

HIGH Priority -- CareTeam, CarePlan, and Goal -- QA Warnings (desire FMM > 0 means we address all warnings)

  • CarePlan
    • MnM exemptions requested for element names should be singular (addresses and replaces)
  • Goal
    • MnM exemption requested for element names should be singular (addresses)
    • GF#10623
      • Rob Hausam was going to help with Goal.description - example binding to a new value set
      • MnM exemption requested for Goal.target.detail because target detail is a choice of data types (i.e. Quantity and CodeableConcept could have different value sets) - Observation.value[x] does not show this same QA warning.

MEDIUM Priority -- All other resources (except Linkage and ClinicalImpression) -- QA Warnings (desire FMM > 0 means we address all warnings)

  • Flag -- no remaining QA warnings!
  • FamilyMemberHistory -- no remaining QA warnings!
  • Communication & CommunicationRequest
    • Category Need to provide a binding - GF#8564
      • Rob Hausam will check to see if v3 has existing codes. If so, use v3. If not, then add v3 codes: alert, notification, reminder, instruction
  • ReferralRequest
    • Discuss : Bindings/Value Sets
      • ReferralRequest.type Need to provide a binding
      • ReferralRequest.reason Need to provide a binding
      • pc:ValueSetComparison Duplicate Valueset Names: v2-0284 (v2 Referral Category) & referralcategory (ReferralCategory) (name: [referrals, categories] / [referrals, categories]))
      • pc:ValueSetComparison Duplicate Valueset Names: v2-0283 (v2 Referral Status) & referralstatus (ReferralStatus) (name: [referrals, statuses] / [referrals, statuses]))
    • Discuss : ReferralRequest.description Element has a todo associated with it (This would be a good candidate for a 'markdown' data type.)
    • Examples
      • ReferralRequest.context Search Parameter 'ReferralRequest.context' had no found values in any example. Consider reviewing the expression (ReferralRequest.context)
      • ReferralRequest.group-identifier Search Parameter 'ReferralRequest.group-identifier' had no found values in any example. Consider reviewing the expression (ReferralRequest.groupIdentifier)

LOW Priority -- CareTeam, CarePlan, and Goal -- QA Information (desire FMM = 3 means we address all information)

  • CareTeam
    • RIM Mapping
  • Goal
    • RIM Mapping
    • QA Checklist: GF#10622 QA 4a: Consider whether Goal.category should be bound to codes from an external code system (Michelle Miller)
  • CarePlan
    • RIM Mapping
    • Examples
      • CarePlan/activity/detail/definition Path had no found values in any example. Consider reviewing the path
      • CarePlan/activity/detail/quantity Path had no found values in any example. Consider reviewing the path
      • CarePlan/activity/detail/reasonCode Path had no found values in any example. Consider reviewing the path
      • CarePlan/activity/detail/reasonReference Path had no found values in any example. Consider reviewing the path
      • CarePlan/supportingInfo Path had no found values in any example. Consider reviewing the path
    • QA Checklist: GF#10621 QA 4a: Consider whether CarePlan.activity.detail.category should be bound to an external code system (Michelle Miller)

Draft Resources with FMM = 0 -- ClinicalImpression and Linkage

  • ClinicalImpression -- keep as FMM = 0
    • Stephen Chu will work on examples to cover all elements
      • ClinicalImpression.action Search Parameter 'ClinicalImpression.action' had no found values in any example. Consider reviewing the expression (ClinicalImpression.action)
      • ClinicalImpression.previous Search Parameter 'ClinicalImpression.previous' had no found values in any example. Consider reviewing the expression (ClinicalImpression.previous)
    • PCWG: ClinicalImpression.code Need to provide a binding
  • Linkage -- keep as FMM = 0
    • PCWG: Linkage A resource must have an 'entered in error' status
    • PCWG: Linkage All resources should have an identifier
    • PCWG: Linkage.item Element has a todo associated with it (Make this 2..*.)


Block Vote (Thurs, Feb 2)

Non-ballot comments

  • GF#12585 Add Goal.target.measure invariant (Michelle Miller) Persuasive
  • GF#12645 CarePlan.activity.reference includes ProcessRequest (Dave Carlson) Persuasive
  • GF#12646 Add "careplan-title" extension (Dave Carlson) Persuasive with Mod
  • GF#12668 ClinFHIR: extension-condition-partof - add support for referencing Condition (Michelle Miller) Persuasive
  • GF#12669 Please add note element to careTeam (Emma Jones) Persuasive

Adjourn

Adjourned at .

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items
  1. Agenda review
  2. Approve previous meeting minutes
    • Motion: <moved>/<seconded> Abstain - <#>, Negative - <#>, Approve - <#>
  3. gForge change request

© 2012 Health Level Seven® International. All rights reserved.

Retrieved from "https://wiki.hl7.org/w/index.php?title=2017-02-02_Patient_Care_FHIR_Call&oldid=132948"