Dharmesh Patel Google Cloud Healthcare & Life Sciences Google Cloud .

Building InteroperableHealthcare Apps withGoogle Cloud FHIR APIsDharmesh PatelGoogle Cloud Healthcare & Life Sciences

Agenda1Healthcare Interoperability & FHIR2Google’s Cloud Healthcare FHIR API3SMART on FHIR

HealthcareInteroperability& FHIR01

The Interoperability Challenge in Healthcare

FHIR as the Data Model and API Spec for InteroperabilityFHIR – Fast Healthcare Interoperability Resources (FHIR, pronounced"fire") is a next generation healthcare data standard created by HL7 todescribe data formats and elements (known as "resources") andapplication programming interfaces (APIs) for exchanging healthcaredata (clinical, diagnostic, medications, workflows, financial, etc) F – Fast (to design & to implement) H – Healthcare I – Interoperability R – ResourcesFHIR as a data modelFHIR as an API specification

Patient Schema in FHIRFHIR Id & MetadataHuman Readable SummaryExtension with reference toits definitionStandard Data Content: Patient IdentityNameGenderDate of BirthProvider

FHIR for Healthcare App Developers Leverage the standard data model instead of building your own custom schemas as you go Use standard FHIR APIs for data access, search,and common operations Create, Read, Update, Delete History, Search, Validate, Patient record & Transaction Easily consume data from other systems Electronic Health Record (EHR) Systems Health Plans Other healthcare apps

04Now, let’s see GoogleFHIR APIs in Action.Cloud HealthcareFHIR API

Cloud Healthcare API - Overview Serverless/managed service for storing and managing healthcaredata privately and securely in the CloudSupports compliance with leading healthcare focused regulatoryframeworks such as HIPAA, HITRUST and GDPR.Data Standards:-HL7 FHIR Resources and REST APIsHL7v2 Messages and REST APIsDICOM Instances and REST APIsIntegrated Capabilities:Cloud Healthcare API-Consent ManagementHealthcare De-Identification

Interactions with FHIR mportExportAStreamingBulkBulkFHIR StoreDe IdentifyNotifyFHIRConfigPub/Sub

Storing and Accessing FHIR ud HealthcareFHIR APIApp

Organization: Project - Location - Dataset - FHIR StoreProjectCloud Healthcare APILocationDatasetStore (FHIR Datastore)

Accessing FHIR resources using RESThttps://healthcare.googleapis.com/ v /projects/ P /locations/ L /datasets/ D / type Stores/ S V Healthcare API version P Project identifier L Location identifier D Dataset identifier type Data type slug S Store identifierhl7v2, dicom,

A-1. Create a Dataset

A-2. Create a FHIR DataStoreCan also edit, delete, list stores from UI or API method calls

B-1. Bulk Import

C-1. Create a FHIR ResourceApps & servicesCloud HealthcareFHIR API

C-2. Accessing FHIR data: Get PatientApps & servicesCloud HealthcareFHIR API

C-3. Updating FHIR data: PUT PatientApps & servicesCloud HealthcareFHIR API

C-4. Updating FHIR data: PATCH PatientApps & servicesCloud HealthcareFHIR API

C-5. Accessing FHIR data: Search PatientApps & servicesCloud HealthcareFHIR API

C-6. Accessing FHIR data: Delete PatientApps & servicesCloud HealthcareFHIR API

Getting Started with FHIR APIs1.Introduction to the Cloud Healthcare ating to the Cloud Healthcare os/authentication3.Using Cloud Healthcare FHIR tos/fhir

03Introduction toSMART

SMARTSubstitutable Medical Applications and Reusable Technologies Open standards to integrate third-party Apps withEHRs/Patient Portal OpenID Connect and OAuth2 based Reusable Apps Write once run with any EHRs!Run in different contexts (EHRs and Patient Portals) Secure and seamless access to EHR data in AppsConfidential & Proprietary

SMART standardizes healthcare applicationsSubstitutable Medical Applications and Reusable temsUX IntegrationSingle Sign OnAuthorizationClinical Data and ContextEHRsPatient PortalsData WarehousesConfidential & Proprietary

SMART Standalone launchUser App1a. Data access requested (scopes)1. Launch anApp2a. Access token for data access, user identity, context (currentpatient, encounter), UI related informationHealthcareAPIs / EHR2.AuthorizeAccess3a. FHIR API request with OAuth2 Access token3. DisplayDataFHIRServer3b. FHIR resourcesConfidential & Proprietary

SMART EHR launchEHR AppEHR1a. Launch information (server URL, token)1b. Data access requested (scopes)2a. Access token for data access, user identity, context (currentpatient, encounter), UI related information3. DisplayData3a. FHIR API request with OAuth2 Access token1. Launch anApp from theregisteredApps2. AuthorizeAccessFHIR Server3b. FHIR resourcesConfidential & Proprietary

SMART Backend Services AuthorizationBackendService1a. Data access requested (JWT Assertion)2a. Access token for data access with authorize system scopesHealthcareAPIs / EHR2.AuthorizeAccess3a. FHIR API request with OAuth2 Access token3. DisplayDataFHIRServer3b. FHIR resourcesConfidential & Proprietary

SMART Authorization Scopes Scope conveys what access an app needspatient/Immunization.readAccess typeFHIR ResourcePermissionApp can read Immunizationinformation of a patient inthe contextExamples: patient/Patient.read - App can access demographics information of a patient in the contextpatient/*.read - App can read all resources of a patient in the contextuser/Patient.write - App can write (create/update/delete) all Patient resources accessible to useruser/*.read - App can read all resources of all patients accessible to usersystem/Patient.write - App can write (create/update/delete) all Patient resourcessystem/*.read - App can read all resources of all patientsConfidential & Proprietary

SMART App Galleryy

SMART Sandbox and App Launcher

Thank you

Google Cloud FHIR APIs Dharmesh Patel Google Cloud Healthcare & Life Sciences. Agenda Healthcare Interoperability & FHIR SMART on FHIR 1 2 3 Google's Cloud Healthcare FHIR API. Healthcare 01 Interoperability & FHIR. The Interoperability Challenge in Healthcare. FHIR as the Data Model and API Spec for Interoperability