Integrating with the epic platform fhir dev days 17
- 1. FHIR® is the registered trademark of HL7 and is used with the permission of HL7. The Flame Design mark is the registered trademark of HL7 and is used with the permission of HL7. Amsterdam, 15-17 November | @fhir_furore | #fhirdevdays17 | www.fhirdevdays.com Zach Vaughan Integrating with the Epic Platform
- 7. How we interoperate Download public specs Playing with FHIR
- 12. YOU NOW OPE N TO http://apporchard.epic.com
- 13. Create and manage your apps
- 15. Access data entered by users or gathered by interfaces to other systems
- 17. November 9 – 10, 2017 | Verona, WI
- 18. 2-Day Training February 2018
- 19. FHIR
- 20. Patient Practitioner Condition Observation (Vitals) Observation (Smoking Hx) Observation (Lab Results) Immunization Diagnostic Report Device (Implants) Family Member History Allergy Intolerance Medication Order Medication Statement Medication Document Reference Care Plan Goal Procedure Read ^ Available Today
- 21. FHIR 2018 Location Medication Request (Inpatient) Diagnostic Report (Imaging) Encounter Appointment Observation (Vitals) Appointment Patient Allergy Intolerance Read ^ Writev
- 23. File data back to the chart
- 24. New ways to interact Consume external data Initiate FHIR Requests More content Appointment resource Operations ($find, $book) Industry engagement Argonauts FHIR 2018 – Scheduling
- 27. •EHR Launch of SMART on FHIR Apps •Pass User and Patient Context •Embed them natively in a browser •From MyChart web and mobile •From Hyperspace, web and mobile
- 31. •Backend Services •No user •OAuth 2 client credentials flow •System-to-system data exchange FHIRon
- 33. • Launch from Hyperspace, Web and Mobile, … (2015+) • Patient Login (2015+) • User Login (2018, retrofitted to 2017) • Backend Services (2018, considering retrofit) • Introspection endpoint (2018) Epic’s support for OAuth2 FHIRon
- 34. UNIVERSITY OF UTAH H O S P I T A L S & C L I N I C S Bilirubin management via SMART on FHIR and HSPC platform integration Phil Warner, Mike Donnelly
- 35. The problem with SMART apps Bilirubin Chart Newborns < 120 hours old Bilirubin results that are either: Not documented Outside of the accepted range The user needs to know the app is available The user needs to know the app is relevant The user has to find the app and launch it
- 37. The EHR invokes a CDS service via a patient-view hook, resulting in a SMART app link card that the clinician uses to launch the SMART app. Validate and implement the CDS Hooks security model
- 39. EHR FHIR ServerApp 1 Create Subscription resource 2 Clinical or workflow event fires in EHR 3 Post change to subscribing clients 4 FHIR Subscriptions
- 40. Event Processing End User Actions Batch Processes Interfaces Services & APIs Event Generators Rules Engine Events Event Channel Events Epic Operational Database Take Actions Downstream Systems Other Apps External Intelligence Epic’s Event Driven Architecture
- 41. UserSession Resource • Creating a new FHIR resource for context synchronization. • UserSession represents the current user’s context: • Workstation • Patient • Study • User • Application subscribe to changes to UserSession for a given user, workstation or patient, etc
- 42. FHIRcast EHR FHIR ServerApp 1 Subscribe to UserSession 2 Patient chart opened in EHR 3 Notify subscribed client of chart-open event. 5 Delete subscription 4 Open patient
- 45. Get Involved! •http://fhircast.org • January 2018 Connectathon (New Orleans) track • http://wiki.hl7.org/index.php?title=201801_FHIR_Subscriptions • May 2018 Connectathon (Germany)
- 46. Dank u wel! •For more information, please check us out! •www.epic.com •https://open.epic.com •https://apporchard.epic.com •http://fhircast.org •Questions? •zvaughan@epic.com