This wiki has undergone a migration to Confluence found Here

Difference between revisions of "2017-10-05 Patient Care FHIR Call"

From HL7Wiki
Jump to navigation Jump to search
 
(34 intermediate revisions by the same user not shown)
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"| VA
 
|colspan="2"| VA
 
|-
 
|-
| || Stephen Chu
+
| 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"| Health eData Inc
 
|colspan="2"| Health eData Inc
 
|-
 
|-
| || Rob Hausam
+
|X || Rob Hausam
 
|colspan="2"| Hausam Consulting LLC
 
|colspan="2"| Hausam Consulting LLC
 
|-
 
|-
| || Laura Heermann-Langford
+
|X || Laura Heermann-Langford
 
|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
 
|-
 
|-
| || Michelle M Miller  
+
| X || Michelle M Miller  
 
|colspan="2"| Cerner
 
|colspan="2"| Cerner
 
|-
 
|-
Line 113: Line 113:
 
|colspan="2"| Intermountain Healthcare
 
|colspan="2"| Intermountain Healthcare
 
|-
 
|-
| || Joe Quinn
+
| X|| Joe Quinn
 
|colspan="2"| Optum
 
|colspan="2"| Optum
 
|-
 
|-
Line 124: Line 124:
 
| || Serafina Versaggi
 
| || Serafina Versaggi
 
|colspan="2"| Dept of Veterans Affairs
 
|colspan="2"| Dept of Veterans Affairs
 +
|-
 +
| X || Sharon Soloman
 +
|colspan="2"|
 +
|-
 +
| X || Danielle Friends
 +
|colspan="2"| Epic
 
|-
 
|-
 
|colspan="4" style="background:#f0f0f0;"|
 
|colspan="4" style="background:#f0f0f0;"|
Line 148: Line 154:
 
#Agenda review
 
#Agenda review
 
#Approve previous meeting minutes [[2017-09-28_Patient_Care_FHIR_Call]]
 
#Approve previous meeting minutes [[2017-09-28_Patient_Care_FHIR_Call]]
#*'''Motion:''' <moved>/<seconded>
+
#*'''Motion:''' Stephen/Rob
# High Priority Resources
+
# SNOMED/HL7 relationship
# gForge change request
+
# Nutrition intake FHIR resource
 +
# High priority resources (AllergyIntolerance, Condition, and Procedure) - normative candidates
 +
# gForge change request backlog
  
 
==Supporting Information==
 
==Supporting Information==
Line 171: Line 179:
 
=================================================================--->
 
=================================================================--->
 
<!-- **** Delete instructions  and fill in minutes ON NEXT LINES  ******-->
 
<!-- **** Delete instructions  and fill in minutes ON NEXT LINES  ******-->
 +
=== SNOMED / HL7 relationship ===
 +
Nothing is changing with the SNOMED/HL7 relationship, but we have been struggling to get it fully defined.<br>
 +
In San Diego, there was a decision to stop preparing request to SNOMED for concept free use.  Why wasn't it approved?  Difficulty in process and question about maximum limits (SNOMED has never said there were a max number, they have hinted there might be a max).
 +
SNOMED asked that once HL7 makes request, it would be a single request.
 +
If a country has license, then full use of concepts.  This does apply to exchange of data across boundaries of member and non-member countries.
 +
 +
=== Nutrition intake FHIR resource ===
 +
The nutrition group would like to propose a nutrition intake FHIR resource (OO and PC as co-sponsors).
 +
 +
In ClinFHIR, there is a hierarchy of proposed elements for Nutrition Service.
 +
* food
 +
** estimatedDeliveryTime
 +
** item
 +
** amount
 +
** menu
 +
** intake
 +
** nutrients
 +
* nutritionOrder
 +
* identifier
 +
* subject
 +
* effectiveDateTime
 +
* printedDateTime
 +
* category
 +
 +
Recommend:  Gap analysis against Observation to see where an extension or profile or new resource may be needed
 +
 +
Need to clearly define boundaries between nutritional intake versus I&O (fluid balance).
 +
* Nutritional intake -- documenting the nutritional status/balance
 +
* I&O - fluid and hemodynamic balance of patient (e.g. in ICU)
 +
 +
Use case:
 +
* inpatient -- what was diet prior to admission
 +
* clinic -- diet history to manage diabetes; check whether following goals in care plan
 +
 +
No V2 equivalent.
 +
 +
Questionnaire scope includes "Patient intake form", but consider guidance [http://build.fhir.org/questionnaire.html#qversusr Using Questionnaire versus Resources]
 +
 +
=== High Priority Resources (AlleryIntolerance, Condition, Procedure) ===
 +
 +
{|border="1" cellpadding="2" cellspacing="0"
 +
<!---=======================================================================
 +
|                                                                          |
 +
|  MM    MM  TTTTTT  GGGGG        IIIIII  NN    NN  FFFFFF  OOOOO      |
 +
|  MMM  MMM    TT    GG              II    NNN  NN  FF      OO  OO    |
 +
|  MM MMM MM    TT    GG  GGG        II    NN NN NN  FFFF    OO  OO    |
 +
|  MM  M  MM    TT    GG  GG        II    NN  NNN  FF      OO  OO    |
 +
|  MM    MM    TT    GGGGG        IIIIII  NN    NN  FF      OOOOO      |
 +
|                                                                          |
 +
========================================================================--->
 +
<!-- ********  CHANGE WG Name or Project ON NEXT LINE *******************-->
 +
| width="20%" colspan="1" align="left"|
 +
| width="40%" colspan="1" align="left"|'''AllergyIntolerance'''
 +
| width="40%" colspan="1" align="left"|'''Condition'''
 +
|-
 +
|| asserter
 +
|| '''Short''': Source of the information about the allergy <br>
 +
'''Long''': The source of the information about the allergy that is recorded <br>
 +
'''w5''':  <font color="red">who.source</font><br>
 +
'''v2''': IAM-14 (ReportedBy if patient) / IAM-18 (Statused by Person if practitioner)
 +
|| '''Short''': Person who asserts this condition <br>
 +
'''Long''': Individual who is making the condition statement <br>
 +
'''w5''':  <font color="red">who.author</font> --> CHANGE to who.source<br>
 +
'''v2''': REL-7.1 identifier + REL-7.12 type code
 +
|-
 +
|| assertedDate
 +
|| '''Short''': Date record was believed accurate <br>
 +
'''Long''': The date on which the existance of the AllergyIntolerance was first asserted or acknowledged <br>
 +
'''w5''':  when.recorded <br>
 +
'''v2''': IAM-20 (Statused at Date/Time) --> CHANGE to IAM-13 (Reported Date/Time
 +
|| '''Short''': Date record was believed accurate <br>
 +
'''Long''': The date on which the existance of the Condition was first asserted or acknowledged.  The assertedDate represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified.  The date of the last record modification can be retrieved from the resource metadata <br>
 +
'''w5''': when.recorded <br>
 +
'''v2''': REL-11
 +
 +
|-
 +
|| recorder
 +
|| '''Short''': Who recorded the sensitivity <br>
 +
'''Long''': Individual who recorded the record and takes responsibility for its content <br>
 +
'''w5''': who.author 
 +
|| ADD recorder to Condition
 +
|-
 +
|| recordedDate
 +
|| N/A
 +
|| N/A
 +
|-
 +
 +
|}
 +
 +
 +
 +
AllergyIntolerance
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13997 GF#13997] - QA 4d. value set should include unknown when minOccurs=1 - AllergyIntolerance.verificationStatus - [https://chat.fhir.org/#narrow/stream/implementers/topic/AllergyIntolerance.20verificationStatus Zulip discussion]
 +
** Similar discussion for AllergyIntolerance.clinicalStatus -- focus for next week
 +
** Similar discussion for Condition.clinicalStatus -- focus for next week
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14007 GF#14007] QA 5e. W5 mappings - AllergyIntolerance.asserter = w5 who.source whereas Condition.asserter = w5 who.author
 +
** Similar to questions on how to map AllergyIntolerance.assertedDate = IAM-20 (Statused at Date/Time) or IAM-13 (Reported Date/Time)?
 +
** AllergyIntolerance.assertedDate says "The date on which the existance of the AllergyIntolerance was first asserted or acknowledged" as well as "Date record was believed accurate"
 +
** AllergyIntolerance.asserter says "The source of the information about the allergy that is recorded"
  
=== High Priority Resources ===
+
 
* QA 5e. W5 mappings - AllergyIntolerance.asserter = w5 who.source whereas Condition.asserter = w5 who.author
+
Condition -- focus for next week
 +
* [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13980 GF#13980] condition-related extension cardinality should be 0..* (pre-applied)
 
* QA 4a. Condition.category is CodeableConcept with FHIR-defined value set - related to past [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10091 GF#11091]
 
* QA 4a. Condition.category is CodeableConcept with FHIR-defined value set - related to past [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10091 GF#11091]
* Condition.clinicalStatus - revisit [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13026 GF#13026]
+
* revisit [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13026 GF#13026] Condition.clinicalStatus
 +
* QA 4d. value set should include unknown when minOccurs=1 - Condition.clinicalStatus has invariant that requires it, but it doesn't have unknown
 +
 
 +
Procedure -- backlog
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13974 GF#13974] Purpose of Procedure.reasonCode vs. Procedure.reasonReference (Ioana Singureanu)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13975 GF#13975] Procedure.reasonReference description is incomplete (Ioana Singureanu)
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13976 GF#13976] Procedure.focalDevice description is confusing (Ioana Singureanu)
  
 
=== gForge Change Requests ===
 
=== gForge Change Requests ===
  
CommunicationRequest
+
Communication/CommunicationRequest
 
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13936 GF#13936] CommunicationRequest - intent value set (Ravi Kuchi)  
 
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13936 GF#13936] CommunicationRequest - intent value set (Ravi Kuchi)  
 +
* [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13979 GF#13979] QA 4a:  Communication.topic needs binding to a value set (Michelle Miller)
  
 
CarePlan/Goal backlog   
 
CarePlan/Goal backlog   
Line 227: Line 342:
  
 
=== Adjourn ===
 
=== Adjourn ===
Adjourned at <hh:mm am/pm> <timezone>.
+
Adjourned at 6:32pm Eastern
  
 
==Meeting Outcomes==
 
==Meeting Outcomes==

Latest revision as of 22:34, 5 October 2017



Meeting Information

Patient Care FHIR Resources Conference Call

Location: Conference Call
Phone Number: +1 770-657-9270
Participant Passcode: 943377
WebEx: https://cernermeeting.webex.com/join/michelle.m.miller

Date: 2017-10-05
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 Health eData Inc
X Rob Hausam Hausam Consulting LLC
X 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
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 Sharon Soloman
X Danielle Friends Epic
Quorum Requirements Met: yes

Agenda

Agenda Topics

  1. Agenda review
  2. Approve previous meeting minutes 2017-09-28_Patient_Care_FHIR_Call
    • Motion: Stephen/Rob
  3. SNOMED/HL7 relationship
  4. Nutrition intake FHIR resource
  5. High priority resources (AllergyIntolerance, Condition, and Procedure) - normative candidates
  6. gForge change request backlog

Supporting Information

Minutes

SNOMED / HL7 relationship

Nothing is changing with the SNOMED/HL7 relationship, but we have been struggling to get it fully defined.
In San Diego, there was a decision to stop preparing request to SNOMED for concept free use. Why wasn't it approved? Difficulty in process and question about maximum limits (SNOMED has never said there were a max number, they have hinted there might be a max). SNOMED asked that once HL7 makes request, it would be a single request. If a country has license, then full use of concepts. This does apply to exchange of data across boundaries of member and non-member countries.

Nutrition intake FHIR resource

The nutrition group would like to propose a nutrition intake FHIR resource (OO and PC as co-sponsors).

In ClinFHIR, there is a hierarchy of proposed elements for Nutrition Service.

  • food
    • estimatedDeliveryTime
    • item
    • amount
    • menu
    • intake
    • nutrients
  • nutritionOrder
  • identifier
  • subject
  • effectiveDateTime
  • printedDateTime
  • category

Recommend: Gap analysis against Observation to see where an extension or profile or new resource may be needed

Need to clearly define boundaries between nutritional intake versus I&O (fluid balance).

  • Nutritional intake -- documenting the nutritional status/balance
  • I&O - fluid and hemodynamic balance of patient (e.g. in ICU)

Use case:

  • inpatient -- what was diet prior to admission
  • clinic -- diet history to manage diabetes; check whether following goals in care plan

No V2 equivalent.

Questionnaire scope includes "Patient intake form", but consider guidance Using Questionnaire versus Resources

High Priority Resources (AlleryIntolerance, Condition, Procedure)

AllergyIntolerance Condition
asserter Short: Source of the information about the allergy

Long: The source of the information about the allergy that is recorded
w5: who.source
v2: IAM-14 (ReportedBy if patient) / IAM-18 (Statused by Person if practitioner)

Short: Person who asserts this condition

Long: Individual who is making the condition statement
w5: who.author --> CHANGE to who.source
v2: REL-7.1 identifier + REL-7.12 type code

assertedDate Short: Date record was believed accurate

Long: The date on which the existance of the AllergyIntolerance was first asserted or acknowledged
w5: when.recorded
v2: IAM-20 (Statused at Date/Time) --> CHANGE to IAM-13 (Reported Date/Time

Short: Date record was believed accurate

Long: The date on which the existance of the Condition was first asserted or acknowledged. The assertedDate represents the date when this particular Condition record was created in the EHR, not the date of the most recent update in terms of when severity, abatement, etc. were specified. The date of the last record modification can be retrieved from the resource metadata
w5: when.recorded
v2: REL-11

recorder Short: Who recorded the sensitivity

Long: Individual who recorded the record and takes responsibility for its content
w5: who.author

ADD recorder to Condition
recordedDate N/A N/A


AllergyIntolerance

  • GF#13997 - QA 4d. value set should include unknown when minOccurs=1 - AllergyIntolerance.verificationStatus - Zulip discussion
    • Similar discussion for AllergyIntolerance.clinicalStatus -- focus for next week
    • Similar discussion for Condition.clinicalStatus -- focus for next week
  • GF#14007 QA 5e. W5 mappings - AllergyIntolerance.asserter = w5 who.source whereas Condition.asserter = w5 who.author
    • Similar to questions on how to map AllergyIntolerance.assertedDate = IAM-20 (Statused at Date/Time) or IAM-13 (Reported Date/Time)?
    • AllergyIntolerance.assertedDate says "The date on which the existance of the AllergyIntolerance was first asserted or acknowledged" as well as "Date record was believed accurate"
    • AllergyIntolerance.asserter says "The source of the information about the allergy that is recorded"


Condition -- focus for next week

  • GF#13980 condition-related extension cardinality should be 0..* (pre-applied)
  • QA 4a. Condition.category is CodeableConcept with FHIR-defined value set - related to past GF#11091
  • revisit GF#13026 Condition.clinicalStatus
  • QA 4d. value set should include unknown when minOccurs=1 - Condition.clinicalStatus has invariant that requires it, but it doesn't have unknown

Procedure -- backlog

  • GF#13974 Purpose of Procedure.reasonCode vs. Procedure.reasonReference (Ioana Singureanu)
  • GF#13975 Procedure.reasonReference description is incomplete (Ioana Singureanu)
  • GF#13976 Procedure.focalDevice description is confusing (Ioana Singureanu)

gForge Change Requests

Communication/CommunicationRequest

  • GF#13936 CommunicationRequest - intent value set (Ravi Kuchi)
  • GF#13979 QA 4a: Communication.topic needs binding to a value set (Michelle Miller)

CarePlan/Goal backlog

  • GF#13903 CarePlan should allow tracking of past activities (i.e. past interventions) (Rick Geimer)
  • GF#13904 Consider renaming CarePlan.activity.outcomeCodeableConcept and CarePlan.activity.outcomeReference (Rick Geimer)

BR&R:

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


LHS:

  • GF#12509 CareTeam participant (Michelle Miller)

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

SD:


Medium Backlog

  • GF#12633 Split Procedure into Procedure and ProcedureStatement (Lloyd McKenzie)
  • 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)


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:32pm Eastern

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.