Payer/Provider Information Exchange Track (including Cdex) Connectathon Kick-Off August 30, 2019 Christol Green – Anthem Inc. Durwin Day – Health Care Service Corporation Disclaimer

Registration and Travel Preparing to participate Tracking Issues Agenda Purpose & Goals Registration and Travel Preparing to participate Tracking Issues Touchstone Testing Use Cases Disclaimer

Join a community of FHIR users Why Connectathons? Join a community of FHIR users Develop and test your system and use of the standard Increase the visibility of resources, profiles and implementation guides. In-Depth discussion of a use case Demonstrate what’s possible Refine the FHIR Specification Testing as part of a connectathon is a pre-requisite for resources and implementation guides progressing up the FHIR Maturity Model. Disclaimer

Atlanta Atlanta Marriott Marquis, Atlanta, GA Registration Saturday, September 14 and Sunday September 15 Atlanta Marriott Marquis, Atlanta, GA Registration https://www.hl7.org/events/working_group_meeting/2019/09/ Track Information https://confluence.hl7.org/display/FHIR/Connectathons https://confluence.hl7.org/pages/viewpage.action?pageId=55940211 Review the CDex IG http://hl7.org/implement/standards/fhir/us/davinci-cdex/2019Jun/index.html Register with the Connectathon Tracking Application Pre - Connectathon Survey (TBD) Track Orientation Calls Disclaimer

Know where the Connectathon is How to get the most out of Connectathon Know where the Connectathon is - Find the room when you arrive at the hotel the day before Set your goals - What do you want to accomplish? Do you have a plan for getting there? Connect with your track Useful Skills System Readiness Disclaimer

Connect with your Track Track Pages on Confluence Connect to your track lead on Zulip (chat.fhir.org) Communicate issues so others will know what you know. Disclaimer

Useful Skills Familiarize yourself with base technologies ReST-based APIs and conventions – e.g. GET vs. POST vs. PUT, HTTP headers Inspect and understand the HTTP protocol with tooling – i.e. Postman, Browser debugger, Server-side debugger General Healthcare System Clinical concepts Administrative and payer functions Disclaimer

Usefull Skills Cont. FHIR interactions: FHIR-for-developers or FHIR-for-architects level training Specifically understand the profiles, resources within the relevant IG JWTs and access tokens Experience with a FHIR client and server libraries You can find a list of these at https://confluence.hl7.org/display/FHIR/Test+Servers CDS-Hooks  Ability to build/configure/test/monitor APIs e.g. via java, node.js, AWS Lambdas and gateway JSON is a must Basic database management skills SMART  Web UI development – e.g. Angular or React OAuth Disclaimer

Preparing your Environment Environment Accessibility Open – over the internet Firewall should allow inbound and outbound http(s) Open Sandbox environment is ideal Access for doc shares like Google Docs, Zulip, and other internet-based tools Configuration changes are often required on site Try to ensure manageability without off site dev-ops support Test with simulators ahead of time SMART-on-FHIR Implement and test with multiple sandboxes – HSPC, Epic App-Orchard, Cerner Pre-test with the healthcare instances, if possible, since provisioning (of client-ids and OAuth handshake) support multiple client-ids For EPIC, support and test Internet Explorer (embedded browser used by Hyperspace) Systems readiness: Do NOT expect that the system will not need changes during the connect-a-thon. There will always be nuances of interpretation, different codesets, endpoints, payloads, etc., which will require that code is changed and redeployed Thus, make sure that your developers have appropriate access to the environment and can perform the changes without relying on DevOps support. This is particularly important for HL7 connect-a-thons that happen on the weekend Environment needs to be open/accessible over the internet If running server systems on a laptop, the client firewall needs to be configurable to allow inbound http(s). This is NOT typically the case for secure/HIPAA-compliant systems. If running server in a data center, firewall needs to be configurable to allow inbound and outbound http(s). For the connect-a-thon, an open sandbox environment is ideal. Recommend AWS or Google Cloud, for flexibility Test with simulators ahead of the connect-a-thon – this reduces changes that may be required “on the day” Make sure you have a device that communicate with zulip Make sure you have a device that can access open shares, such as google docs (many corporate devices will block access) SMART-on-FHIR in particular: Implement and test with multiple sandboxes – HSPC, Epic App-Orchard, Cerner Pre-test with the healthcare instances, if possible, since provisioning (of client-ids and OAuth handshake) can take a while to get compatibly configured and working Make sure you can support multiple client-ids, since you cannot force each EHR to use the same one For EPIC, make sure to support and test Internet Explorer (the embedded browser used by Hyperspace) Disclaimer

Zulip – https://chat.fhir.org/ Tracking Issues Zulip – https://chat.fhir.org/ Disclaimer

Gforge - https://gforge.hl7.org Tracking Issues Gforge - https://gforge.hl7.org Be sure to sign up for a Gforge account ahead of time Disclaimer

Conformance Testing Value Set Defines a set of coded values (see "Using Codes" for more details) StructureDefinition Makes rules about how a resource (or type) and its data elements are used in a particular context, including defining how extensions are used. A structure definition references value sets for the coded elements in a resource CapabilityStatement A statement of the kinds of resources and operations provided and/or consumed by an application. The Capability Statement references profiles to describe specific use of resources by the application Implementation Guide A single coherent collection of capability statements, profiles, extensions, value sets, and documentation describing a set of interoperable applications To provide details about specific usage of the frameworks and resource contents, FHIR provides a conformance layer that implementers, national/regional programs, and other profiling organizations such as IHE, can use to provide a computable statement about how the resources and their exchange paradigms are used to solve particular use cases. The conformance layer itself is implemented using these key resources. Conformance with this specification does not provide any guarantee of patient or data safety. However, choosing to not conform to this specification carries additional risk in two ways: FHIR has been subject to a level of review and vetting unlikely to be received by any non-conformant variation; variations may result in introduction of undetected risks FHIR-like solutions (based on FHIR, but not conformant) may set expectations by trading partners which are not met due to the non-conformance of the system and these un-met expectations may also result in risk Disclaimer

Touchstone Validation Testing www.Touchstone.com Disclaimer

Use Case Introductions in Confluence https://confluence.hl7.org/display/FHIR/2019- 09+Tracks+for+Connectathon+22 Disclaimer

Saturday Connectathon Get there early! The Connectathon officially starts at 9am ET, but all the good seats are typically gone by 8:30am. Find your track table and sit there if possible. If no room, find an open table but know where your track lead is sitting. Setup WIFI passwords will be available on arrival. Track leads will setup chat groups (Zulip) Disclaimer

Tips, scenario/track changes, etc. Move around Follow the group chat https://chat.fhir.org Tips, scenario/track changes, etc. Move around It’s ok to walk around, ask questions of FHIR leads Participate in other Tracks Be patient and flexible Technical difficulties, limited seating, changes to track materials, etc. Work late The Saturday portion “officially” ends at 5pm. Nobody pays attention to that. You can participate or observe as long as you like. Disclaimer

Did you accomplish your goals? Sunday Connectathon Did you accomplish your goals? Use the ongoing “Virtual Connectathon” to finish. Work with your track lead on report-outs What went well, what did not, discoveries, etc. Follow ups FHIR updates New colleagues, connections, etc. Plan for the rest of the week Disclaimer

Contact Information Christol Green Christol.green@anthem.com Durwin Day Dayd@BCBSIL.com Disclaimer