This wiki has undergone a migration to Confluence found Here
Difference between revisions of "2017-08-03 Patient Care FHIR Call"
Jump to navigation
Jump to search
| (10 intermediate revisions by the same user not shown) | |||
| Line 183: | Line 183: | ||
=== AdverseEvent Transition === | === AdverseEvent Transition === | ||
| − | * | + | * Elaine's [[Media: 2017_FHIR_AE_Patient_Care_WG_2017_8_3.pptx| presentation]] |
| − | |||
* BR&R has v3 message for adverse event - focus on regulatory reporting | * BR&R has v3 message for adverse event - focus on regulatory reporting | ||
* Majority of the real contribution was from Patient Care (e.g. Elaine) | * Majority of the real contribution was from Patient Care (e.g. Elaine) | ||
| Line 203: | Line 202: | ||
** Stephen wants more time to remember his intent (and may end up withdrawing it) | ** Stephen wants more time to remember his intent (and may end up withdrawing it) | ||
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13302 GF#13302] Vocabulary issues with AdverseEvent | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13302 GF#13302] Vocabulary issues with AdverseEvent | ||
| − | * | + | ** actuality - value set no longer contains abbreviations |
| + | ** category - Elaine to look at MeDRA and SNOMED CT for value sets | ||
| + | ** seriousness - Elaine will log a tracker to sort out severity vs seriousness | ||
| + | ** severity - make codes lower case and/or think about whether to use v3 - some inconsistency across resources whether required binding to FHIR-defined value set versus preferred binding to SNOMED CT value set (e.g. Condition.severity) | ||
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13698 GF#13698] AdverseEvent.suspectedEntity.instance should allow CodeableConcept | * [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13698 GF#13698] AdverseEvent.suspectedEntity.instance should allow CodeableConcept | ||
| + | ** AdverseEvent.suspectEntity.instance should support a choice of types CodeableConcept | Reference, but need to decide on the value set | ||
| + | * [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) | ||
=== gForge Change Requests Backlog === | === gForge Change Requests Backlog === | ||
| Line 243: | Line 247: | ||
=== Adjourn === | === Adjourn === | ||
| − | Adjourned at | + | Adjourned at 6:35PM Eastern |
==Meeting Outcomes== | ==Meeting Outcomes== | ||
Latest revision as of 22:40, 3 August 2017
Contents
Meeting Information
| Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2017-08-03 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 | |
| Dave Carlson | VA | ||
| 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 | ||
| X | 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 | ||
| Mike Padula | The Children's Hospital of Philadelphia | ||
| 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 | ||
| X | Mary Ann Slack | FDA | |
| X | Mitra Rocca | FDA | |
| X | Floyd Eisenberg | ||
| X | Scott Gordon | ||
| Quorum Requirements Met: yes | |||
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes 2017-07-27_Patient_Care_FHIR_Call
- Motion: Stephen/Elaine
- AdverseEvent transition from BR&R to Patient Care
- gForge change request
Supporting Information
- 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
- Maintain QA checklist
Minutes
AdverseEvent Transition
- Elaine's presentation
- BR&R has v3 message for adverse event - focus on regulatory reporting
- Majority of the real contribution was from Patient Care (e.g. Elaine)
- Elaine asked how will AdverseEvent interact with ResearchSubject and ResearchStudy?
- 201709_Clinical_Research Connectathon planned
- Mary Ann asked if we can represent reporter? The resource has a recorder, but may need to discuss reporter further.
- Stephen asked to confirm scope. The scope of the AdverseEvent resource *is* intentionally broader than clinical research to cover any event reporting
- Elaine compiled all past documentation, meeting minutes, etc: FHIR_Adverse_Event_Resource
- Recapped GF#13308 and GF#13309, which have been applied
- Rob H has been assigned GF#13312 regarding the AdverseEvent.event value set
- Michelle will reach out to Rik to see if he can attend Thurs Q3 meeting with BR&R and PC to discuss AdverseEvent
gForge Change Requests Discussed
Prioritization of backlog was discussed on July 20, 2017
Joint discussion with BRR (AdverseEvent)
- GF#11021 AdverseEvent - need patient medical history for cases in which subject is not patient
- Stephen wants more time to remember his intent (and may end up withdrawing it)
- GF#13302 Vocabulary issues with AdverseEvent
- actuality - value set no longer contains abbreviations
- category - Elaine to look at MeDRA and SNOMED CT for value sets
- seriousness - Elaine will log a tracker to sort out severity vs seriousness
- severity - make codes lower case and/or think about whether to use v3 - some inconsistency across resources whether required binding to FHIR-defined value set versus preferred binding to SNOMED CT value set (e.g. Condition.severity)
- GF#13698 AdverseEvent.suspectedEntity.instance should allow CodeableConcept
- AdverseEvent.suspectEntity.instance should support a choice of types CodeableConcept | Reference, but need to decide on the value set
- GF#11021 Increase cardinality of substance and make certainty relation to substance not reaction - 2016-09 core #40 (Jay Lyle)
gForge Change Requests Backlog
Aug 10 + WGM: Joint discussion with Pharmacy, OO
- GF#12673 How to handle HCT/TP
- GF#12993 Please Create a NonMedicationAdministration object or an Administration object
- GF#13047 Add DosageInstructions to Procedure
- GF#12676 Guidance request for GP SOAP in FHIR (Alexander Henket) -
- https://chat.fhir.org/#narrow/stream/implementers/topic/ClinicalImpression
- PC, SD - possibly Thurs Q2
- Patient Care WGM agenda: PC_Sept_2017_WGM
Backlog Rady to Discuss
- GF#12163 Update payload URL to lead to a real file (Guillaume Rossignol)
Medium Backlog
- GF#12509 CareTeam participant (Michelle Miller)
- Feedback from LHS, and LHS continues to meet and discuss
- CareTeam.participant.role (existing) 0..* - need to update definition of role (since it mentions responsibility) Example: PCP - close to finalizing the value set
- CareTeam.participant.function 0..* (new) - Example: PT, Wound Care - close to finalizing the value set
- CareTeam.participant.specialty is no longer needed -- instead, get from Practitioner
- GF#12633 Split Procedure into Procedure and ProcedureStatement (Lloyd McKenzie)
- Zulip chat asking for implementer feedback: https://chat.fhir.org/#narrow/stream/implementers/topic/Procedure.20vs.20ProcedureStatement
- Dave commented that there is relevance for ProcedureStatement in context of CarePlan activities (Activity Statements where the activity is a procedure)
- GF#10028 Careplan: Provide ability to specify patient and/or provider preferences (Emma Jones)
- meet need with a profile for preference on the observation resource. Requirements are a preference category (nutrition, medication, care), the preference priority (high/medium/delayed from C-CDA) and with elements of expressor and recorder.
- This profile would not be developed for this release cycle
- GF#13140 logical definition of care-plan-category value set may require realignment with SCT changes (Matthew Cordell)
- pending SNOMED proposal: https://confluence.ihtsdotools.org/display/cmag/Care+plans
- Rob said he would follow up on the status of the SNOMED proposal
Low Backlog
- GF#10635 QA 5a: Resource references exist in both directions for Condition and ClinicalImpression (Michelle Miller)
- ClinicalImpression is not mature enough to resolve this issue. Ask MnM for an exemption on the QA checklist (re: Condition having a circular reference with ClinicalImpression)
- Add note: "A known issue exists with circular references between Condition and ClinicalImpression, which is due to the low maturity level of ClinicalImpression. The Patient Care work group intends to address this issue when ClinicalImpression is considered substantially complete and ready for implementation"
- GF#11173 CarePlan needs support for reviews - 2016-09 core #327 (Stephen Chu)
- Tracking of reviews and plans for reviews is something that applies to many resources, not just CarePlan (e.g. protocols, standing orders, long term care admissions, etc.). This is something probably best handled by "Task" but will require a fair bit of analysis and discussion with other work groups to agree on approach. Defer to R4. Consider transfer to OO who owns Task
Adjourn
Adjourned at 6:35PM Eastern
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.
