Difference between revisions of "2015-10-22 Patient Care FHIR Call"
Line 193: | Line 193: | ||
Lloyd said that there is no expectation that data types and element names match, ContactPoint / telecom is an example <br/> | Lloyd said that there is no expectation that data types and element names match, ContactPoint / telecom is an example <br/> | ||
As related to http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7622, is it worth it to change the recommended name from note (0..*) to annotation (0..*)? | As related to http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7622, is it worth it to change the recommended name from note (0..*) to annotation (0..*)? | ||
+ | |||
+ | Larry feels that having procedure.note could be ambiguous (annotation vs clinical note). | ||
=== Negation === | === Negation === |
Revision as of 21:37, 22 October 2015
Contents
Meeting Information
Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2015-10-22 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 | ||
X | Stephen Chu | Queensland Health | |
Eric Haas | Haas Consulting | ||
X | Rob Hausam | Hausam Consulting LLC | |
Laura Heermann-Langford | Intermountain Healthcare | ||
Emma Jones | Allscripts | ||
X | Russ Leftwich | InterSystems | |
X | Russell McDonell | Telstra Health | |
X | Lloyd McKenzie | Gevity (HL7 Canada) | |
X | Larry McKnight | Cerner | |
X | Michelle M Miller | Cerner | |
Lisa Nelson | Life Over Time Solutions | ||
Viet Nguyen | Systems Made Simple | ||
Craig Parker | Intermountain Healthcare | ||
X | Iona Thraen | Dept of Veterans Affairs | |
X | Jay Lyle | VA | |
X | Simon Sum | Academy of Nutrition and Dietetics | |
Quorum Requirements Met: yes |
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes 2015-10-15_Patient_Care_FHIR_Call
- Motion: Russ/Lloyd Abstain - 1, Negative - 0, Approve - 8
- Follow-up on Prior Action Items
- Lloyd is logging a change request for condition/observation boundary clarification
- Collaborate on definitions of note, annotation, and comment to provide feedback to MnM
- Negation
- OpenEHR collaboration
- DSTU 2.1 prioritization
- gForge change request
Supporting Information
DSTU 2.1 Timeline
FHIR Resources owned by Patient Care
- AllergyIntolerance (1) -- frozen
- Condition (1)
- Procedure (1) -- frozen
- CarePlan (1)
- Goal (1)
- Referral Request (1)
- Questionnaire (1)
- Questionnaire Answer (1)
- FamilyMemberHistory (2) genomics / Jonathan Holt – Vanderbilt - interested in contributing to this resource.
- Procedure Request (2)
- Flag (2)
- ClinicalImpression (3)
- Communication (3)
- CommunicationRequest (3)
Note: Contraindication and Risk Assessment are owned by CDS, not Patient Care
Note: Substantive changes to frozen resources in DSTU2.1 are prohibited unless FMG explicitly approves the substantive change
Minutes
Prior Action Items
Condition/observation boundary
Lloyd logged a change request for condition/observation boundary clarification
http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=8872
MnM feedback on notes/annotation/comments
2015-10-15_Patient_Care_FHIR_Call#Definitions
- Notes are....
- also known as clinical note or document; could be unstructured or structured; could require review and authentication; likely has a subject or type of note assigned to enable retrieval of note; could follow the SOAP format
- Comments are....
- unstructured, free form text that applies to the entire entity (e.g. condition, allergy, medication order, etc.). A comment is typically comprised of an author, date/time, and text only. Typically, comments don't have a status or title. Comments don't standalone, so there is typically no title of the comment or need for additional workflow to review or authenticate the comment independent from the overall entity's status.
- comments could be independent
- Annotations are....
- unstructured, free form text that is context specific with a given entity (e.g. annotated condition code display or annotation within a flowsheet or wave form for a specific point in time or time frame)
- could be a comment, but distinguished from comments by being "attached" to document or image
- annotate a point of interest in document or wave form, or "topic of interest" (e.g. medication dose/frequency/brand matters)
- an annotation is a comment on something else
- annotation is "part of" something else
Both comments and annotations are impacting something else versus a note is standalone
Lloyd said that there is no note resource today (and even if a clinical note was added, it would be named clinical note)
Lloyd said that there is no expectation that data types and element names match, ContactPoint / telecom is an example
As related to http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=7622, is it worth it to change the recommended name from note (0..*) to annotation (0..*)?
Larry feels that having procedure.note could be ambiguous (annotation vs clinical note).
Negation
OpenEHR collaboration
DSTU 2.1 Prioritization
- Normative candidates
- For resources that are frozen, doing non-substantive changes to get them ready for quality criteria and moving up maturity levels.
- For draft or new resources, then be informed by what implementers are saying they need/want. Ping implementer community for feedback to help us prioritize
gForge Change Requests
Adjourn
Adjourned at <hh:mm am/pm> <timezone>.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.