Difference between revisions of "2016-04-21 Patient Care FHIR Call"
(5 intermediate revisions by the same user not shown) | |||
Line 223: | Line 223: | ||
=== FHIR Adverse Event discussion with RCRIM === | === FHIR Adverse Event discussion with RCRIM === | ||
− | Elaine shared [[AdverseEvent_FHIR_Resource_Proposal]] | + | Elaine shared [[AdverseEvent_FHIR_Resource_Proposal]] |
+ | |||
+ | FHIR resource must meet FDA requirements for regulatory reporting | ||
+ | |||
+ | V3 ICSR supports both regulatory adverse event reports as well as other types of occurrence reporting based on input of patient safety interests. | ||
+ | |||
+ | FDA noted that the V3 ICSR is an ISO standard. | ||
+ | |||
+ | CBER (FDA), EMA and Japan all using V3 ICSR by 2017 for drugs and biologics. | ||
+ | |||
+ | FDA would like to create a MedWatch form using FHIR. The form would be mapped to FHIR. | ||
+ | |||
+ | In addition the CADSR is mapped to ICSR. | ||
+ | |||
+ | The Structured Data Capture Adverse Event creates population forms using ICSR concepts. These forms were tested in the last IHE Connectathon. | ||
Lisa Nelson shared HL7 v3 DAM (Adverse Reaction) - When AdverseReactionObservation is specific to medication/substance administration, we would need the ability to link a medication administration to an adverse event (how to do so will be determined later) | Lisa Nelson shared HL7 v3 DAM (Adverse Reaction) - When AdverseReactionObservation is specific to medication/substance administration, we would need the ability to link a medication administration to an adverse event (how to do so will be determined later) | ||
− | Will this be a "simple" resource or a more "complex" resource (like CarePlan) that references a lot of other resources? Likely more complex; an aggregation or wrapper of other information/resources | + | Will this be a "simple" resource or a more "complex" resource (like CarePlan) that references a lot of other resources? Likely more complex; an aggregation or wrapper of other information/resources; will require additional analysis. |
− | + | The group will meet next in Montreal, Tuesday Q3. | |
=== Profiling Care Plan === | === Profiling Care Plan === | ||
+ | Background: IHE profiling care plan; dynamic care plan is a longitudinal care plan that may reference other care plans | ||
+ | <br> | ||
+ | CDA has relationships between HealthConcerns, Goals, Interventions | ||
+ | * Goal.addresses conveys the relationship between goal and condition/concern | ||
+ | * CarePlan.activity.detail.goal conveys the relationship between activity.detail and goal | ||
+ | * Since there is no way to convey the relationship between CarePlan.activity.reference and goal, Michelle logged http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9856 asking to move goal to the activity level, with name "related" or "associated" goal | ||
+ | <br> | ||
+ | Reviewed search parameters, which included a few at the activity level. Discussed that http://hl7-fhir.github.io/profiling.html#conf-res supports "Add additional operations or search parameters not in the base specification (using the OperationDefinition resource or the SearchParameter Resource" | ||
=== Prior Action Item Follow-up === | === Prior Action Item Follow-up === | ||
Line 246: | Line 268: | ||
=== Adjourn === | === Adjourn === | ||
− | Adjourned at | + | Adjourned at 6:29PM Eastern |
==Meeting Outcomes== | ==Meeting Outcomes== |
Latest revision as of 22:43, 21 April 2016
Contents
Meeting Information
Patient Care FHIR Resources Conference Call Location: Conference Call |
Date: 2016-04-21 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 | ||
X | Eric Haas | Haas Consulting | |
X | Rob Hausam | Hausam Consulting LLC | |
Laura Heermann-Langford | Intermountain Healthcare | ||
X | Emma Jones | Allscripts | |
Russ Leftwich | InterSystems | ||
Jay Lyle | Ockham Information Services LLC, VA | ||
Sarah Maulden | VA | ||
Jim McClay | Univ of Nebraska Medical Center | ||
X | Russell McDonell | Telstra Health | |
Lloyd McKenzie | Gevity (HL7 Canada) | ||
Larry McKnight | Cerner | ||
X | Michelle M Miller | Cerner | |
X | Lisa Nelson | Life Over Time Solutions | |
X | Viet Nguyen | Systems Made Simple | |
X | M'Lynda Owens | Cognosante | |
Craig Parker | Intermountain Healthcare | ||
Scott Robertson | Kaiser Permanente | ||
X | Simon Sum | Academy of Nutrition and Dietetics | |
Iona Thraen | Dept of Veterans Affairs | ||
X | Anita Walden | Duke | |
X | Brian Peck | Epic | |
Dr Ed Hammond, Ph.D. | Duke | ||
Helton, Edward | (NIH/NCI) | ||
Jose Costa Teixeira | |||
Julie James | Bluewaveinformatics.co.uk | ||
Mead Walker | comcast.net | ||
Minaei, Behnaz | (FDA/CDRH) | ||
Reeves, Dianne | (NIH/NCI) | ||
X | Rik Smithies | ||
X | Rocca, Mitra | (FDA/CDER) | |
Terrillion, Susan | (AHRQ/CQuIPS) | ||
X | Raquel Bartz | Duke | |
X | Rashedul Hasan | ||
Quorum Requirements Met: yes |
Agenda
Agenda Topics
- Agenda review
- FHIR Adverse Event discussion with RCRIM
- Profiling Care Plan
- Prior Action Item Follow-up
- gForge change request
- QA Guidelines
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
FHIR Adverse Event discussion with RCRIM
Elaine shared AdverseEvent_FHIR_Resource_Proposal
FHIR resource must meet FDA requirements for regulatory reporting
V3 ICSR supports both regulatory adverse event reports as well as other types of occurrence reporting based on input of patient safety interests.
FDA noted that the V3 ICSR is an ISO standard.
CBER (FDA), EMA and Japan all using V3 ICSR by 2017 for drugs and biologics.
FDA would like to create a MedWatch form using FHIR. The form would be mapped to FHIR.
In addition the CADSR is mapped to ICSR.
The Structured Data Capture Adverse Event creates population forms using ICSR concepts. These forms were tested in the last IHE Connectathon.
Lisa Nelson shared HL7 v3 DAM (Adverse Reaction) - When AdverseReactionObservation is specific to medication/substance administration, we would need the ability to link a medication administration to an adverse event (how to do so will be determined later)
Will this be a "simple" resource or a more "complex" resource (like CarePlan) that references a lot of other resources? Likely more complex; an aggregation or wrapper of other information/resources; will require additional analysis.
The group will meet next in Montreal, Tuesday Q3.
Profiling Care Plan
Background: IHE profiling care plan; dynamic care plan is a longitudinal care plan that may reference other care plans
CDA has relationships between HealthConcerns, Goals, Interventions
- Goal.addresses conveys the relationship between goal and condition/concern
- CarePlan.activity.detail.goal conveys the relationship between activity.detail and goal
- Since there is no way to convey the relationship between CarePlan.activity.reference and goal, Michelle logged http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=9856 asking to move goal to the activity level, with name "related" or "associated" goal
Reviewed search parameters, which included a few at the activity level. Discussed that http://hl7-fhir.github.io/profiling.html#conf-res supports "Add additional operations or search parameters not in the base specification (using the OperationDefinition resource or the SearchParameter Resource"
Prior Action Item Follow-up
Michelle flipped a couple gForge statuses back to Triaged where input was provided (specifically, those listed below under gForge Change Requests).
gForge Change Requests
Will discuss next week, ran out of time to discuss on April 21
QA Guidelines
Will discuss next week, ran out of time to discuss on April 21
Adjourn
Adjourned at 6:29PM Eastern
Meeting Outcomes
Actions
|
Next Meeting/Preliminary Agenda Items
|
© 2012 Health Level Seven® International. All rights reserved.