This wiki has undergone a migration to Confluence found Here

Clinician on FHIR - May 2017 Madrid, Spain

From HL7Wiki
Jump to navigation Jump to search

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


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


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.

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:
- []
- 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

  • To be determined

Track 3 Medications

  • 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