Difference between revisions of "2016-02-11 Patient Care FHIR Call"
(Created page with "{{subst::Patient_Care_FHIR_Call_Template}}") |
|||
(30 intermediate revisions by the same user not shown) | |||
Line 23: | Line 23: | ||
'''Live Meeting:''' <nowiki>https://www147.livemeeting.com/cc/_XML/cerner/join?id=8FNF2S&role=attend&pw=m9Kd%7Cx9</nowiki> | '''Live Meeting:''' <nowiki>https://www147.livemeeting.com/cc/_XML/cerner/join?id=8FNF2S&role=attend&pw=m9Kd%7Cx9</nowiki> | ||
<!-- ******** CHANGE Date and Time ON NEXT LINE **********************--> | <!-- ******** CHANGE Date and Time ON NEXT LINE **********************--> | ||
− | | width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''Date: 2016- | + | | width="50%" colspan="2" align="left" style="background:#f0f0f0;"|'''Date: 2016-02-11'''<br/> '''Time: 5-6:30pm ET''' |
|- | |- | ||
<!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | <!-- ******** CHANGE chair and scribe ON NEXT LINES *******************--> | ||
Line 51: | Line 51: | ||
|- | |- | ||
<!-- ********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 60: | Line 60: | ||
|colspan="2"| Haas Consulting | |colspan="2"| Haas Consulting | ||
|- | |- | ||
− | | || Rob Hausam | + | |X || Rob Hausam |
|colspan="2"| Hausam Consulting LLC | |colspan="2"| Hausam Consulting LLC | ||
|- | |- | ||
Line 69: | Line 69: | ||
|colspan="2"| Allscripts | |colspan="2"| Allscripts | ||
|- | |- | ||
− | | || Russ Leftwich | + | | X|| Russ Leftwich |
|colspan="2"| InterSystems | |colspan="2"| InterSystems | ||
|- | |- | ||
− | | || Jay Lyle | + | |X || Jay Lyle |
|colspan="2"| Ockham Information Services LLC, VA | |colspan="2"| Ockham Information Services LLC, VA | ||
|- | |- | ||
Line 81: | Line 81: | ||
|colspan="2"| Univ of Nebraska Medical Center | |colspan="2"| Univ of Nebraska Medical Center | ||
|- | |- | ||
− | | || Russell McDonell | + | | X || Russell McDonell |
|colspan="2"| Telstra Health | |colspan="2"| Telstra Health | ||
|- | |- | ||
− | | || Lloyd McKenzie | + | | X || Lloyd McKenzie |
|colspan="2"| Gevity (HL7 Canada) | |colspan="2"| Gevity (HL7 Canada) | ||
|- | |- | ||
− | | || Larry McKnight | + | |X || Larry McKnight |
|colspan="2"| Cerner | |colspan="2"| Cerner | ||
|- | |- | ||
− | | | + | | X || Michelle M Miller |
|colspan="2"| Cerner | |colspan="2"| Cerner | ||
|- | |- | ||
Line 105: | Line 105: | ||
|colspan="2"| Kaiser Permanente | |colspan="2"| Kaiser Permanente | ||
|- | |- | ||
− | | || Simon Sum | + | |X || Simon Sum |
|colspan="2"| Academy of Nutrition and Dietetics | |colspan="2"| Academy of Nutrition and Dietetics | ||
|- | |- | ||
| || Iona Thraen | | || Iona Thraen | ||
|colspan="2"| Dept of Veterans Affairs | |colspan="2"| Dept of Veterans Affairs | ||
+ | |- | ||
+ | | X || M'Lynda Owens | ||
+ | |colspan="2"| | ||
|- | |- | ||
|colspan="4" style="background:#f0f0f0;"| | |colspan="4" style="background:#f0f0f0;"| | ||
Line 133: | Line 136: | ||
<!-- ***** Delete instructions and fill in agenda items ON NEXT LINES ****--> | <!-- ***** Delete instructions and fill in agenda items ON NEXT LINES ****--> | ||
#Agenda review | #Agenda review | ||
− | #Approve previous meeting minutes | + | #Approve previous meeting minutes: [[2016-02-04_Patient_Care_FHIR_Call]] |
− | #*'''Motion:''' | + | #*'''Motion:''' Russell/Jay Abstain - 0, Negative - 0, Approve - 4 |
#Prior Action Item Follow-up | #Prior Action Item Follow-up | ||
# gForge change request | # gForge change request | ||
Line 174: | Line 177: | ||
=== Prior Action Item Follow-up === | === Prior Action Item Follow-up === | ||
+ | |||
+ | ====Note vs ClinicalImpression Boundaries==== | ||
+ | A ‘Note’ is about a subject (typically a patient)<br> | ||
+ | A ‘Note’ may have one or more ‘Clinical Impressions’ which are typically part of a section (named "Assessment/Plan") OR sometimes this is part of a dictation (where the entire document is stored as a PDF or single block of text)<br> | ||
+ | Notes, on the other hand, may contain many things that are NOT clinical Impressions. Notes may contain many things that are NOT clinical impressions at all.<br> | ||
+ | Can any content be included in the note (e.g. allergies, family history)? Anything is possible in a note. | ||
+ | |||
+ | If the H&P is signed, then an annotation could be added. | ||
+ | |||
+ | If capture allergy, diagnosis, procedure, family history, then one possibility in system to capture narrative only (still lives in same place, such that you could retrieve it with other structured allergies, etc). More common to capture raw text into a single bucket with a mixture of allergies, diagnoses, procedures, family history etc. | ||
+ | |||
+ | '''Different ways to capture data in FHIR:''' <br> | ||
+ | # Domain resource (e.g. allergy, condition, procedure, etc) -- discrete form or narrative form or combination of both | ||
+ | # Questionnaire contains structured data | ||
+ | |||
+ | Are notes another way to capture undifferentiated data? Narrative, tied to subject, context/encounter, author, time | ||
+ | |||
+ | Introduce new resource for capturing raw form text<br> | ||
+ | When we know what the content is, then use specific domain resource narrative | ||
+ | |||
+ | Documents in FHIR require content to live in other resources, which get packaged into a Bundle and Composition (who created, when, for what purpose). Collection of stuff gets passed around with rules about how to render. Narrative associated to Composition (who wrote it, title, date, type of document). In some circumstances, use Composition to wrap PDF or equivalent (whole text of document). The narrative ends up being the PDF. Most of the time, though, the content of the document comes from the various resources that each section points to (e.g. list) and narrative of that will be the blob for that section. When query the Bundle, can use parameters of Composition. | ||
+ | * What element is used for text body when the text is all in one big blob? Composition narrative (text or HTML -- or reference to contained binary) | ||
+ | * Why not have a single section with section.text? The text is the entire document....and might represent more than a single section, so don't use section to represent the entire note. | ||
+ | * Still use Bundle that contains Patient and Composition. | ||
+ | |||
+ | H&P is more document-like because discrete resources do exist. | ||
+ | |||
+ | Nursing notes at end of shift (e.g. patient had nausea, gave meds) -- is not a document. | ||
+ | |||
+ | '''Conclusion:''' | ||
+ | # Look into a new clinical note resource, which represents a big undifferentiated textual blob with narrative, tied to subject, context/encounter, author, time (maybe it is Basic, but will evaluate) -- often from dictation or a text editor | ||
+ | # Need a way to represent processes, like H&P or SOAP, without needing to invoke Document paradigm (to make it possible to share SOAP without having to define sections) -- next step: if we didn't do documents, but wanted discrete information, what does that resource look like? Larry and Rob; might have references to existing resources and/or might have content specific to the new resource | ||
+ | # If a Document exists, then can continue with Document instead of parsing into discrete data | ||
=== gForge Change Requests === | === gForge Change Requests === | ||
+ | N/A - ran out of time | ||
=== Adjourn === | === Adjourn === | ||
− | Adjourned at | + | Adjourned at 06:57 PM Eastern. |
==Meeting Outcomes== | ==Meeting Outcomes== | ||
Line 195: | Line 232: | ||
| width="100%" align="left" style="background:#f0f0f0;"|'''Actions''' '' | | width="100%" align="left" style="background:#f0f0f0;"|'''Actions''' '' | ||
− | * | + | * Russell is withdrawing his prior gForge requesting a new Clinical Note resource |
+ | * Larry, Rob, and Michelle will draft elements of a new resource to represent structured notes (such as H&P, SOAP notes, etc) | ||
|- | |- | ||
<!---======================================================================= | <!---======================================================================= |
Latest revision as of 23:56, 11 February 2016
Contents
Meeting Information
Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2016-02-11 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 | |
Stephen Chu | |||
Eric Haas | Haas Consulting | ||
X | Rob Hausam | Hausam Consulting LLC | |
Laura Heermann-Langford | Intermountain Healthcare | ||
Emma Jones | Allscripts | ||
X | Russ Leftwich | InterSystems | |
X | Jay Lyle | Ockham Information Services LLC, VA | |
Sarah Maulden | VA | ||
Jim McClay | Univ of Nebraska Medical Center | ||
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 | ||
Scott Robertson | Kaiser Permanente | ||
X | Simon Sum | Academy of Nutrition and Dietetics | |
Iona Thraen | Dept of Veterans Affairs | ||
X | M'Lynda Owens | ||
Quorum Requirements Met: yes |
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes: 2016-02-04_Patient_Care_FHIR_Call
- Motion: Russell/Jay Abstain - 0, Negative - 0, Approve - 4
- Prior Action Item Follow-up
- gForge change request
Supporting Information
FHIR Resources owned by Patient Care
Maturity levels [1]
- Questionnaire (2) -- Lloyd will QA to get to 3
- Questionnaire Response (2) -- Lloyd will QA to get to 3
- Condition (2)
- AllergyIntolerance (1) -- Rob
- Procedure (1)
Connectathon candidates
- CarePlan (1)
- Goal (1)
- Referral Request (1)
- FamilyMemberHistory (1)
Lower priority resources
- Procedure Request (1)
- Flag (1)
- ClinicalImpression (0) -- goal to move to level 1 by next release
- Communication (1)
- CommunicationRequest (1)
Note: Contraindication and Risk Assessment are owned by CDS, not Patient Care
Minutes
Prior Action Item Follow-up
Note vs ClinicalImpression Boundaries
A ‘Note’ is about a subject (typically a patient)
A ‘Note’ may have one or more ‘Clinical Impressions’ which are typically part of a section (named "Assessment/Plan") OR sometimes this is part of a dictation (where the entire document is stored as a PDF or single block of text)
Notes, on the other hand, may contain many things that are NOT clinical Impressions. Notes may contain many things that are NOT clinical impressions at all.
Can any content be included in the note (e.g. allergies, family history)? Anything is possible in a note.
If the H&P is signed, then an annotation could be added.
If capture allergy, diagnosis, procedure, family history, then one possibility in system to capture narrative only (still lives in same place, such that you could retrieve it with other structured allergies, etc). More common to capture raw text into a single bucket with a mixture of allergies, diagnoses, procedures, family history etc.
Different ways to capture data in FHIR:
- Domain resource (e.g. allergy, condition, procedure, etc) -- discrete form or narrative form or combination of both
- Questionnaire contains structured data
Are notes another way to capture undifferentiated data? Narrative, tied to subject, context/encounter, author, time
Introduce new resource for capturing raw form text
When we know what the content is, then use specific domain resource narrative
Documents in FHIR require content to live in other resources, which get packaged into a Bundle and Composition (who created, when, for what purpose). Collection of stuff gets passed around with rules about how to render. Narrative associated to Composition (who wrote it, title, date, type of document). In some circumstances, use Composition to wrap PDF or equivalent (whole text of document). The narrative ends up being the PDF. Most of the time, though, the content of the document comes from the various resources that each section points to (e.g. list) and narrative of that will be the blob for that section. When query the Bundle, can use parameters of Composition.
- What element is used for text body when the text is all in one big blob? Composition narrative (text or HTML -- or reference to contained binary)
- Why not have a single section with section.text? The text is the entire document....and might represent more than a single section, so don't use section to represent the entire note.
- Still use Bundle that contains Patient and Composition.
H&P is more document-like because discrete resources do exist.
Nursing notes at end of shift (e.g. patient had nausea, gave meds) -- is not a document.
Conclusion:
- Look into a new clinical note resource, which represents a big undifferentiated textual blob with narrative, tied to subject, context/encounter, author, time (maybe it is Basic, but will evaluate) -- often from dictation or a text editor
- Need a way to represent processes, like H&P or SOAP, without needing to invoke Document paradigm (to make it possible to share SOAP without having to define sections) -- next step: if we didn't do documents, but wanted discrete information, what does that resource look like? Larry and Rob; might have references to existing resources and/or might have content specific to the new resource
- If a Document exists, then can continue with Document instead of parsing into discrete data
gForge Change Requests
N/A - ran out of time
Adjourn
Adjourned at 06:57 PM Eastern.
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.