This wiki has undergone a migration to Confluence found Here

Difference between revisions of "2018-01-25 Patient Care FHIR Call"

From HL7Wiki
Jump to navigation Jump to search
Line 166: Line 166:
 
<!-- **** Delete instructions  and fill in minutes ON NEXT LINES  ******-->
 
<!-- **** Delete instructions  and fill in minutes ON NEXT LINES  ******-->
  
=== Prior Action Item Follow-up ===
+
=== WGM Agenda ===
 +
[[January_2018_WGM_New_Orleans;_Jan_27_to_Feb_8]]
 +
 
 +
=== High Priority Resources (AlleryIntolerance, Condition, Procedure) ===
 +
 
 +
* FHIR Admin [[FHIR_Ballot_Prep]]
 +
** QA guidelines have changed:  [[FHIR_Conformance_QA_Criteria]]
 +
** No PC resources are currently targeted for normative, but we can still evaluate
 +
*** '''AllergyIntolerance''' - questions about reaction/AdverseEvent - is this just writing down boundaries?
 +
*** '''Condition''' - questions about health concern/linking - need Connectathon planned around concern management, need use cases (from domain analysis) and scenarios to test and recruit implementers to participate
 +
*** '''Procedure''' - questions about splitting Procedure (performed) vs ProcedureStatement (history/ patient stated) - need to draft resources as a starting point and sync with Russ on whether we need a more generic patient activity statement resource
 +
****Procedure statement is a good idea. Need to broaden the concepts to other activities. Idea is to have activity statement and then profile it specific to procedure. A patient statement about their exercise or nutritional intake or their ADLs, these are different
 +
****Who are the actors that would use this - patient statement and carer statement but can be an activity statement that a provider can use as secondary information. Scope includes provider use as well.
 +
****PMH - where it should be possible do distinguish surgical or diagnostic procedure from when the patient reported the procedure. Post surgery, the surgeon will make an interventional procedure report. This is different. FHIR has a procedure report. OO part would be the diagnostic report (report of findings) and the report that is interventional - these are two different reports. How does FHIR separate the two. And how does FHIR handle the real world where these are combined? Ultrasound guided biopsy would be a diagnostic report with findings (description of the procedure and description of findings).
 +
****There is an extension that adds the types of terms that you would see on the procedure.
 +
****Might be a more general solution but it's not settled.
 +
****Standard operative report has a description of the procedure and a section that deals with findings. 
 +
 
 +
=== gForge Change Requests (Backlog) ===
 +
Workflow
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14446 GF#14446] PatientCare resources do not have a clean Workflow report
 +
 
 +
CarePlan
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13903 GF#13903] CarePlan should allow tracking of past activities (i.e. past interventions) (Rick Geimer)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10028 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
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13140 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
 +
* [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)
 +
** 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
 +
 
 +
AdverseEvent / BR&R -- Thurs Q3
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13302 GF#13302] Vocabulary issues with AdverseEvent
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13698 GF#13698] AdverseEvent.suspectedEntity.instance should allow CodeableConcept
 +
* [https://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
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13892 GF#13892] Need guidance on overlap of AdverseEvent.event.text and AdverseEvent.description (Lloyd McKenzie)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13893 GF#13893] Correction to AdverseEvent.subject definition (Lloyd McKenzie)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13894 GF#13894] AdverseEvent.eventParticipant needs work (Lloyd McKenzie)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14238 GF#14238] AdverseEvent.suspectEntity.instance should be expanded to include the Immunization resource (Craig Newman) - also related to [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14152 GF#14152]
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14458 GF#14458] AdverseEvent should have a context reference
 +
 
 +
CareTeam / LHS -- Thurs Q4
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14334 GF#14334] allow careteam.participant,member to reference a Practitioner role (David Hay) -- discuss at WGM after we get implementer feedback
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12509 GF#12509] CareTeam participant (Michelle Miller)
 +
 
 +
OO -- Wed Q3
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12673 GF#12673] How to handle HCT/TP
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12993 GF#12993] Please Create a NonMedicationAdministration object or an Administration object
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13047 GF#13047] Add DosageInstructions to Procedure
 +
 
 +
SD -- Mon Q2
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12676 GF#12676] Guidance request for GP SOAP in FHIR (Alexander Henket) -
 +
** https://chat.fhir.org/#narrow/stream/implementers/topic/ClinicalImpression
 +
** [http://www.hl7.org/documentcenter/public_temp_5FDD4E7F-1C23-BA17-0C08E37E733EAB03/wg/structure/minutes/Minutes%202017%2012%2014.rtf Dec 14 SD Minutes]
 +
 
 +
Procedure -- Wed Q1
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=12633 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)
 +
 
 +
ClinicalImpression
 +
* [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)
 +
** 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"
  
=== gForge Change Requests ===
 
  
 
=== Adjourn ===
 
=== Adjourn ===

Revision as of 14:07, 25 January 2018



Meeting Information

Patient Care FHIR Resources Conference Call

Location: Conference Call
Phone Number: +1 563-999-2090
Participant Passcode: 792564
WebEx: https://join.freeconferencecall.com/patientcare

Date: 2018-01-25
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
Dave Carlson VA
Stephen Chu The Australian Digital Health Agency (ADHA)
Evelyn Gallego EMI Advisors LLC
Eric Haas Health eData Inc
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
Mike Padula The Children's Hospital of Philadelphia
Craig Parker Intermountain Healthcare
Joe Quinn Optum
Katie Wheatley UK NHS Digital
Quorum Requirements Met: yes

Agenda

Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes 2018-01-18_Patient_Care_FHIR_Call
    • Motion: <moved>/<seconded>
  3. Prior Action Item Follow-up
  4. gForge change request

Supporting Information

Minutes

WGM Agenda

January_2018_WGM_New_Orleans;_Jan_27_to_Feb_8

High Priority Resources (AlleryIntolerance, Condition, Procedure)

  • FHIR Admin FHIR_Ballot_Prep
    • QA guidelines have changed: FHIR_Conformance_QA_Criteria
    • No PC resources are currently targeted for normative, but we can still evaluate
      • AllergyIntolerance - questions about reaction/AdverseEvent - is this just writing down boundaries?
      • Condition - questions about health concern/linking - need Connectathon planned around concern management, need use cases (from domain analysis) and scenarios to test and recruit implementers to participate
      • Procedure - questions about splitting Procedure (performed) vs ProcedureStatement (history/ patient stated) - need to draft resources as a starting point and sync with Russ on whether we need a more generic patient activity statement resource
        • Procedure statement is a good idea. Need to broaden the concepts to other activities. Idea is to have activity statement and then profile it specific to procedure. A patient statement about their exercise or nutritional intake or their ADLs, these are different
        • Who are the actors that would use this - patient statement and carer statement but can be an activity statement that a provider can use as secondary information. Scope includes provider use as well.
        • PMH - where it should be possible do distinguish surgical or diagnostic procedure from when the patient reported the procedure. Post surgery, the surgeon will make an interventional procedure report. This is different. FHIR has a procedure report. OO part would be the diagnostic report (report of findings) and the report that is interventional - these are two different reports. How does FHIR separate the two. And how does FHIR handle the real world where these are combined? Ultrasound guided biopsy would be a diagnostic report with findings (description of the procedure and description of findings).
        • There is an extension that adds the types of terms that you would see on the procedure.
        • Might be a more general solution but it's not settled.
        • Standard operative report has a description of the procedure and a section that deals with findings.

gForge Change Requests (Backlog)

Workflow

  • GF#14446 PatientCare resources do not have a clean Workflow report

CarePlan

  • GF#13903 CarePlan should allow tracking of past activities (i.e. past interventions) (Rick Geimer)
  • 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)
  • 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

AdverseEvent / BR&R -- Thurs Q3

  • GF#13302 Vocabulary issues with AdverseEvent
  • GF#13698 AdverseEvent.suspectedEntity.instance should allow CodeableConcept
  • GF#11021 Increase cardinality of substance and make certainty relation to substance, not reaction - 2016-09 core #40
  • GF#13892 Need guidance on overlap of AdverseEvent.event.text and AdverseEvent.description (Lloyd McKenzie)
  • GF#13893 Correction to AdverseEvent.subject definition (Lloyd McKenzie)
  • GF#13894 AdverseEvent.eventParticipant needs work (Lloyd McKenzie)
  • GF#14238 AdverseEvent.suspectEntity.instance should be expanded to include the Immunization resource (Craig Newman) - also related to GF#14152
  • GF#14458 AdverseEvent should have a context reference

CareTeam / LHS -- Thurs Q4

  • GF#14334 allow careteam.participant,member to reference a Practitioner role (David Hay) -- discuss at WGM after we get implementer feedback
  • GF#12509 CareTeam participant (Michelle Miller)

OO -- Wed Q3

  • GF#12673 How to handle HCT/TP
  • GF#12993 Please Create a NonMedicationAdministration object or an Administration object
  • GF#13047 Add DosageInstructions to Procedure

SD -- Mon Q2

Procedure -- Wed Q1

ClinicalImpression

  • 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"


Adjourn

Adjourned at <hh:mm am/pm> <timezone>.

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.