This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Clinician on FHIR - May 2017 Madrid, Spain"

From HL7Wiki
Jump to navigation Jump to search
Line 47: Line 47:
 
* [[March 7 - Refine plans for Care Plan Track]]  
 
* [[March 7 - Refine plans for Care Plan Track]]  
 
* March 14 - David Hay - Walk through the new interface, tool Q&A
 
* March 14 - David Hay - Walk through the new interface, tool Q&A
* March 21 - Refine plans for Medications (Rob H. out)
+
* March 21 - OPEN (Rob H. out)
 
* March 28 - Refine plans for Diagnostics and ordering (Laura out)
 
* March 28 - Refine plans for Diagnostics and ordering (Laura out)
* April 4 - OPEN
+
* April 4 - Refine plans for Medications - need to confirm with Melva and John Hatum
 
* April 11 - Adverse Event (do not move this one - Russ available)
 
* April 11 - Adverse Event (do not move this one - Russ available)
 
* April 18 - Clinical Maturity Model  (ClinFHIR tool freeze)
 
* April 18 - Clinical Maturity Model  (ClinFHIR tool freeze)

Revision as of 21:12, 21 March 2017

Back to: Patient Care
Return to: FHIR Clinical Resources - PCWG
Return to: Clinicians on FHIR
Return to: Clinician on FHIR 2017

Introduction

The May 2017 Clinician-on-FHIR event will be hosted on Friday May 12, 2017.


Weekly preparatory conference calls are being hosted on Tuesdays at 5:00 - 6:00 pm US Eastern.

First Clinician-on-FHIR call starts: Tuesday January 24, 2017

Conference call details: please see HL7 email broadcast


Planning

Master Plan for Baltimore Clinicians on FHIR - May 2017 - placeholder


Tracks to be addressed and leadership

- Details to be included


Planning Notes

  • Wiki Page - To be included


Goal = create at least one (or more if possible) meaningful example(s) (actual JSON resource instance) for each FHIR resource otherwise the limitation of the FHIR resource is identified.


Planning Calendar and Meeting Minutes

  • March 7 - Refine plans for Care Plan Track
  • March 14 - David Hay - Walk through the new interface, tool Q&A
  • March 21 - OPEN (Rob H. out)
  • March 28 - Refine plans for Diagnostics and ordering (Laura out)
  • April 4 - Refine plans for Medications - need to confirm with Melva and John Hatum
  • April 11 - Adverse Event (do not move this one - Russ available)
  • April 18 - Clinical Maturity Model (ClinFHIR tool freeze)
  • April 25 - OPEN (Russ out, Emma out)
  • May 2 - Last Minute prep and orientation


Tooling and Supporting Information

  • Tool
- Participants registered for the Clinician-on-FHIR event are strongly recommended to familiarise themselves with the clinFHIR tool
- A new user interface has been created to support creation of clinical story built from a set of FHIR resources based on the clinical scenario described in the Tracks section below
- Logon to the clinFHIR site:
- [clinFHIR.com/]
- Connect to the FHIR servers by selecting the appropriate Data Server (e.g. Public HAPI DSTU3), Conformance Server and Terminology Server
- click on the "Tool" icon on the top right hand corner of the clinFHIR page and select "simple builder" option
(Note - "simple builder" will soon be changed to "scenario builder")


  • Supporting Information
- To be included



Clinician-on-FHIR Tracks


Track 1 Diagnostic Ordering and Reporting

  • Track Lead: Rob Hausam
  • Clinical Scenario



Track 2 Care Plan and Care Team

Leads: Emma Jones, Laura Heermann


  • Care Plan - inclusion of the components. These are the components of the care plan, how are they included into the FHIR Care Plan resource?
  • Care Team - MD, RN, dietician, PT, referral to skin/wound nurse,
    • Refer to the technical connectathon use case spread sheet - how do you assign the common functionality of the team members to them - who is the team lead, coverage for others, who is reviewing only, who can edit, accept, review, decline, delete, reconcile, history of team members? (new PCP), etc.
    • Spreadsheet prepared by Stephen for the ONC call. Touches on care team type.
  • Instructions - Discharge, wound care, medication, diet
  • Medications - insulin...
  • Procedures - dressing change, foot care,
  • XX
  • XX
  • Select Patient
  • Select Care Plan
  • Select Care Team (multiple care team members)
    • Add MD
    • Add RN
    • Add Nutritionist
    • Add Consulting podiatrist
    • Add Pharmacist
    • Add RN Educator
    • Patient in the team
    • Caregiver (lay) on the team

For each of these:

  • Name
  • Role(s) - multiple needed per person (PCP, Covering MD, Wound RN, Team Lead) (need a Gforge item for Role to be 0...*
  • Specialty
  • Status on the team (active, past...)
  • Participation privileges - create, accept, decline, update, review...

Additional: instructions, need the goals for instruction?


CarePlan - Use Case Spreadsheet

  • This is the spreadsheet containing a Type 2 Diabetes use case for Care Plan and Care Team. The contents were used in the January 2017 San Antonio Technical Connectathon and Clinician-on-FHIR Care Plan track.
Type 2 DM - Use case and test data for Care Plan and Care Team


Goal for November: to have one cohesive storyboard - look at the one from the last technical connectathon. It needs to have a nursing spin put on it. With a nursing focus of content included. Such as nurse reinforcing diabetic teaching, injection instruction, etc.



Track 3 Medications

Track leads: Melva Peters/ John Hatum

  • To be determined


Track 4 Adverse Event Resource

Track Lead: Russ Leftwich with help on use cases from Elaine, Margaret and Lindsey

  • specifically test the ability of the resource to fully represent an allergic reaction.
  • Specifically test a range of use cases that would fall under this and see if it works or not..
    • such as:
      • Drug drug interaction
      • non immunologic reaction that is undiagnosed at the onset (a physiologic change that is sudden and unexpected - an intolernance... such as severe abdominal pain an vomiting)
      • Medication error
      • procedure error
      • patient fall
      • Needle stick


Track 5 UK Follow up...

Russ L to reach out to Philip Scott - to explore interest.


.....