This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2017-02-02 Patient Care FHIR Call"
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) | ||
| + | |||
| + | === Block Vote (Thurs, Feb 2)=== | ||
| + | Non-ballot comments | ||
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12585 GF#12585] Add Goal.target.measure invariant (Michelle Miller) Persuasive | ||
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12645 GF#12645] CarePlan.activity.reference includes ProcessRequest (Dave Carlson) Persuasive | ||
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12646 GF#12646] Add "careplan-title" extension (Dave Carlson) Persuasive with Mod | ||
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12668 GF#12668] ClinFHIR: extension-condition-partof - add support for referencing Condition (Michelle Miller) Persuasive | ||
| + | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12669 GF#12669] Please add note element to careTeam (Emma Jones) Persuasive | ||
=== TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3) === | === TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3) === | ||
| Line 193: | Line 201: | ||
*** DiagnosticReport.codedDiagnosis (and profiles) -- http://build.fhir.org/valueset-clinical-findings.html | *** DiagnosticReport.codedDiagnosis (and profiles) -- http://build.fhir.org/valueset-clinical-findings.html | ||
| − | + | * <span style="color:#008000"> Condition </span> is clean on the QA report! | |
| − | |||
* <span style="color:#008000"> Procedure </span> is clean on the QA report! | * <span style="color:#008000"> Procedure </span> is clean on the QA report! | ||
=== HIGH 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) === | ||
| + | |||
| + | * <span style="color:#008000">CareTeam</span> - no QA warnings! | ||
* CarePlan | * CarePlan | ||
| Line 211: | Line 220: | ||
=== MEDIUM Priority -- All other resources (except Linkage and ClinicalImpression) -- QA Warnings (desire FMM > 0 means we address all warnings) === | === 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 | + | * <span style="color:#008000"> Flag </span> -- no QA warnings! |
| − | * <span style="color:#008000"> FamilyMemberHistory </span> -- no | + | * <span style="color:#008000"> FamilyMemberHistory </span> -- no QA warnings! |
| + | ** <span style="color:#FF0000"> Rob Hausam / Stephen Chu </span> will check to see if there is a SNOMED 445518008 or LOINC code to use | ||
* Communication & CommunicationRequest | * Communication & CommunicationRequest | ||
| + | ** Update from Lloyd: Request status is always set by the initiator. It doesn't reflect fulffilment status at all - and we won't change it to include that. An order is active regardless of whether a given filler refuses to act on it. In theory, you can always look for another filler. And if you can't find another filler at the moment, you can leave the request active in the hopes a new one might come along | ||
** Category Need to provide a binding - [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8564 GF#8564] | ** 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 | *** <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 | * ReferralRequest | ||
| − | ** | + | ** [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12750 GF#12750] -- resolved |
*** ReferralRequest.type Need to provide a binding | *** ReferralRequest.type Need to provide a binding | ||
*** ReferralRequest.reason Need to provide a binding | *** ReferralRequest.reason Need to provide a binding | ||
| + | ** <span style="color:#FF0000"> Discuss </span>: Bindings/Value Sets | ||
*** pc:ValueSetComparison Duplicate Valueset Names: v2-0284 (v2 Referral Category) & referralcategory (ReferralCategory) (name: [referrals, categories] / [referrals, categories])) | *** 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])) | *** 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.) | ** <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 | ** Examples | ||
| − | *** ReferralRequest.context Search Parameter 'ReferralRequest.context' had no found values in any example. Consider reviewing the expression (ReferralRequest.context) | + | *** <span style="color:#FF0000"> Stephen Chu </span> 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) | + | *** <span style="color:#FF0000"> Stephen Chu </span> 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) === | === LOW Priority -- CareTeam, CarePlan, and Goal -- QA Information (desire FMM = 3 means we address all information) === | ||
| Line 260: | Line 272: | ||
** 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..*.) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Adjourn === | === Adjourn === | ||
Revision as of 03:00, 1 February 2017
Contents
- 1 Meeting Information
- 2 Agenda
- 3 Supporting Information
- 4 Minutes
- 4.1 STU3 Action Items
- 4.2 Block Vote (Thurs, Feb 2)
- 4.3 TOP Priority -- AllergyIntolerance, Condition, and Procedure -- QA Warnings/Information (desire FMM = 3)
- 4.4 HIGH Priority -- CareTeam, CarePlan, and Goal -- QA Warnings (desire FMM > 0 means we address all warnings)
- 4.5 MEDIUM Priority -- All other resources (except Linkage and ClinicalImpression) -- QA Warnings (desire FMM > 0 means we address all warnings)
- 4.6 LOW Priority -- CareTeam, CarePlan, and Goal -- QA Information (desire FMM = 3 means we address all information)
- 4.7 Draft Resources with FMM = 0 -- ClinicalImpression and Linkage
- 4.8 Adjourn
- 5 Meeting Outcomes
Meeting Information
| Patient Care FHIR Resources Conference Call Location: Conference Call |
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
- Agenda review
- Approve previous meeting minutes 2017-01-31_Patient_Care_FHIR_Call
- Motion:
- Prior Action Item Follow-up
- 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
- 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
- Review workflow gap analysis per GF#10293
- 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)
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
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
- 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
- DiagnosticReport.codedDiagnosis (and profiles) -- http://build.fhir.org/valueset-clinical-findings.html
- Condition is clean on the QA report!
- Procedure is clean on the QA report!
HIGH Priority -- CareTeam, CarePlan, and Goal -- QA Warnings (desire FMM > 0 means we address all warnings)
- CareTeam - no QA 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 QA warnings!
- FamilyMemberHistory -- no QA warnings!
- Rob Hausam / Stephen Chu will check to see if there is a SNOMED 445518008 or LOINC code to use
- Communication & CommunicationRequest
- Update from Lloyd: Request status is always set by the initiator. It doesn't reflect fulffilment status at all - and we won't change it to include that. An order is active regardless of whether a given filler refuses to act on it. In theory, you can always look for another filler. And if you can't find another filler at the moment, you can leave the request active in the hopes a new one might come along
- 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
- GF#12750 -- resolved
- ReferralRequest.type Need to provide a binding
- ReferralRequest.reason Need to provide a binding
- Discuss : Bindings/Value Sets
- 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
- Stephen Chu ReferralRequest.context Search Parameter 'ReferralRequest.context' had no found values in any example. Consider reviewing the expression (ReferralRequest.context)
- Stephen Chu ReferralRequest.group-identifier Search Parameter 'ReferralRequest.group-identifier' had no found values in any example. Consider reviewing the expression (ReferralRequest.groupIdentifier)
- GF#12750 -- resolved
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
- Stephen Chu will work on examples to cover all elements
- 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..*.)
Adjourn
Adjourned at .
Meeting Outcomes
| Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.
