We continue our OpenMRS University series with a presentation by Piotr from UW . This session will be focused on the OpenMRS FHIR module and what the future could look like with a FHIR module for OpenMRS
Join us Next week for a 1 hour session on OpenMRS-FHIR Webinar
Cynthia Antwi is inviting you to a scheduled Zoom meeting.
Topic: FHIR Webinar Series 2 : OpenMRS & FHIR
Time: Sep 11, 2019 02:00 PM Universal Time UTC
Join Zoom Meeting
One tap mobile
+19292056099,552460171# US (New York)
+16699006833,552460171# US (San Jose)
Dial by your location
+1 929 205 6099 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 552 460 171
Find your local number: https://zoom.us/u/aPUyp3vQg
Here’s an outline for tomorrow’s webinar, which will be much less lecture-heavy. We’ll work together to document some of the needs, questions, ideas, and concerns regarding FHIR and OpenMRS. This outline will be updated both during and after the webinar to provide a coherent record of what we talked about.
Get an introduction to the OpenMRS FHIR Module and the OpenMRS Rest API
Review possible future directions for FHIR and OpenMRS
Participate in compiling lists of ideas for each of these categories:
- Previous FHIR-related efforts in the OpenMRS community
- Current health data, web apis, and interoperability needs.
- Questions, Potential Issues, Forcasted Barriers, and any other comments or concerns from community members regarding OpenMRS and FHIR
Introduction
Review of Webinar 1
The previous webinar can be found on the github page
We had a few issues with recording the video, and unfortunately have no video of the tutorial section. However, I finally spliced the audio recording and the video together and uploaded it to YouTube. If you’d like to watch it, check it out here:
Also, if you’d like to get some other perspectives on FHIR, check out these two videos from a tutorial Viet Nguyen gave at last year’s UW FHIR Workshop:
We unfortunately had some difficulties with the recording of today’s session and its not available. @pmanko and I are working on a workaround and will update everyone what the next steps will be shortly.