Difference between revisions of "2015-11-05 Patient Care FHIR Call"
(→SDC) |
(→SDC) |
||
| Line 185: | Line 185: | ||
<attach presentation> | <attach presentation> | ||
| − | SDC is socializing profile to raise visibility prior to | + | SDC is socializing the SDC FHIR profile to raise visibility prior to upcoming (January) connectathon. |
It is possible to query for all questionnaires. | It is possible to query for all questionnaires. | ||
| Line 191: | Line 191: | ||
There is a DataElement resource in FHIR, so data element registry could be (and is within SDC profile) a FHIR server that allows both maintenance of data elements as well as ability to query them. When form designer is authoring forms, load data elements that exist and reference in forms. | There is a DataElement resource in FHIR, so data element registry could be (and is within SDC profile) a FHIR server that allows both maintenance of data elements as well as ability to query them. When form designer is authoring forms, load data elements that exist and reference in forms. | ||
| − | DataElement is currently defined to allow complex data elements (data elements with multiple components), so you can talk about multiple data elements tied together in context of a larger data element. | + | DataElement is currently defined to allow complex data elements (data elements with multiple components), so you can talk about multiple data elements tied together in context of a larger data element. For simple data types there will only be one repetition of DataElement.element. For complex data types, multiple repetitions of DataElement.element will be present defining a nested structure using the "path" element |
| + | |||
| + | Some data elements, such as laterality (left), don't stand alone. | ||
=== Prior Action Item Follow-Up === | === Prior Action Item Follow-Up === | ||
Revision as of 22:29, 5 November 2015
Contents
Meeting Information
| Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2015-11-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 | |
| X | Stephen Chu | ||
| Eric Haas | Haas Consulting | ||
| Rob Hausam | Hausam Consulting LLC | ||
| Laura Heermann-Langford | Intermountain Healthcare | ||
| X | Emma Jones | Allscripts | |
| X | Russ Leftwich | InterSystems | |
| X | Jay Lyle | Ockham Information Services LLC, 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 | ||
| X | Simon Sum | Academy of Nutrition and Dietetics | |
| Iona Thraen | Dept of Veterans Affairs | ||
| X | Farrah Darbouze | ||
| X | Perri Smith | ||
| X | Vijay Shah | ||
| X | Jenny Brush | ||
| X | Lauren Caruso | ||
| Quorum Requirements Met: yes | |||
Agenda
Agenda Topics
- Agenda review
- Approve previous meeting minutes: 2015-10-29_Patient_Care_FHIR_Call
- Motion: Stephen/Elaine Abstain - 5, Negative - 0, Approve - 9
- SDC
- Prior Action Item Follow-Up
- gForge change request
Supporting Information
DSTU 2.1 Timeline
FHIR Resources owned by Patient Care
- AllergyIntolerance (1) -- frozen
- Procedure (1) -- frozen
- Questionnaire (1)-- potential normative candidate
- Questionnaire Answer (1)-- potential normative candidate
- Condition (1) -- possible normative only if it doesn't have substantive changes after working through health concern, negation, and alignment with OpenEHR
- CarePlan (1) -- probably not enough wide spread implementation to be considered normative, but Lloyd will check with community to see if there are any planned implementations coming up in the next 18 months
- Goal (1) -- probably not enough wide spread implementation to be considered normative
- Referral Request (1)-- probably not enough wide spread implementation to be considered normative
- FamilyMemberHistory (2) genomics / Jonathan Holt – Vanderbilt - interested in contributing to this resource -- possible normative, but may not have wide spread implementation to be considered normative
- 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
SDC
<attach presentation>
SDC is socializing the SDC FHIR profile to raise visibility prior to upcoming (January) connectathon.
It is possible to query for all questionnaires.
There is a DataElement resource in FHIR, so data element registry could be (and is within SDC profile) a FHIR server that allows both maintenance of data elements as well as ability to query them. When form designer is authoring forms, load data elements that exist and reference in forms.
DataElement is currently defined to allow complex data elements (data elements with multiple components), so you can talk about multiple data elements tied together in context of a larger data element. For simple data types there will only be one repetition of DataElement.element. For complex data types, multiple repetitions of DataElement.element will be present defining a nested structure using the "path" element
Some data elements, such as laterality (left), don't stand alone.
Prior Action Item Follow-Up
Adverse Event
Elaine has a draft resource proposal for AdverseEvent inspired by the ISO 27953 standard for Adverse Event
DSTU2.1 Implementer Feedback
Lloyd will solicit feedback from implementer community on which resources should be prioritized and who has plans to implement care plan
MnM Annotation/Notes
Lloyd will talk to MnM about the possibility of renaming notes to annotation
Negation
Stephen and Rob will build out the negation proposal/wiki
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.
