Getting SMART with FHIR Grahame Grieve, Mark Braunstein, Michael - - PowerPoint PPT Presentation

getting smart
SMART_READER_LITE
LIVE PREVIEW

Getting SMART with FHIR Grahame Grieve, Mark Braunstein, Michael - - PowerPoint PPT Presentation

Getting SMART with FHIR Grahame Grieve, Mark Braunstein, Michael Lawley, Brett Esler, Reuben Daniels, Kate Ebrill, Steve Badham, Andrew Patterson, Danielle Bancroft, Brian Postlethwaite August 2019 Australias National Science Agency


slide-1
SLIDE 1

Australia’s National Science Agency

Getting SMART with FHIR

Grahame Grieve, Mark Braunstein, Michael Lawley, Brett Esler, Reuben Daniels, Kate Ebrill, Steve Badham, Andrew Patterson, Danielle Bancroft, Brian Postlethwaite August 2019

slide-2
SLIDE 2

1. FHIR rapidly spreading around the World- Grahame Grieve 2. Fueling FHIR for change in the US- Mark Braunstein 3. Quick FHIR: initiatives across Australia

  • HL7 Au - Brett Esler
  • SafeScript - Danielle Bancroft
  • Federated Provider Directory - Brian Postlethwaite
  • National Children’s Digital Health Collaborative - Steve Badham
  • Queensland Clinical Terminology Service - Reuben Daniels
  • Genomics Alliance’s supported by FHIR - Andrew Patterson
  • Primary Care Data Quality and Practice to Practice Exchange - Kate Ebrill

Agenda

slide-3
SLIDE 3

Mentimeter- getting to know who is in the room

slide-4
SLIDE 4

FHIR: Spreading around the world

Grahame Grieve 13-Aug 2019 Melbourne (IHE/HIC)

slide-5
SLIDE 5

FHIR: The web, for Healthcare

Open Community Open Standard

  • Make it easier to exchange

healthcare information

  • Open Participation - uses

web infrastructure (social media)

  • Lead by HL7 - deeply

connected to world wide health community

  • Describes how to exchange

healthcare information

  • A web API - web standards

where possible

  • Continuity with existing

healthcare standards

  • Public Treasure

(http://hl7.org/fhir)

slide-6
SLIDE 6

FHIR History

Standards History

  • July 2011 - Conception
  • May 2012 - First Milestone
  • Sept 2014 - R1 (Trial Use)
  • Oct 2015 - R2
  • April 2017 - R3 (CC0)
  • Dec 2018 - R4 (1st Normative)
  • Oct 2020? - R5

Implementation History

  • Sept 2012: 1st Connectathon
  • June 2014: Commonwell (1st Prod)
  • Sept 2014: Reorientate
  • Dec 2014: Argonaut
  • May 2016: FHIR Foundation
  • Jan 2018: Apple Healthkit
  • Late 2019?: R4 required in US Regs
slide-7
SLIDE 7

Three Legs of the Standards Process

  • Base Standard
  • Establish Capabilities
  • Common Engineering
  • V2, FHIR, DICOM, LOINC, SNOMED, XDS?
  • Profiling for Communities
  • Common Use Cases, Smaller communities (Wishel Rule)
  • Adapt / Combine
  • IHE, Argonaut / Da Vinci, ADHA / IT-14
  • Driving Solutions into the Market
  • Regulation, Incentive Payments – ONC, ADHA, etc
  • Trade Associations - HIMSS / HISA,
slide-8
SLIDE 8

Overall Progress

slide-9
SLIDE 9
slide-10
SLIDE 10

Where adoption is happening

  • Secondary Data Repositories
  • Patient access to data
  • Big Data
  • Specific Clinical Data Repositories
  • National Health Records / Sharing frameworks
  • Application Extension
  • Argonaut / EHR Plug-ins
  • Decision Support Integration
  • Primary Apps: SaaS (health)
  • Interaction between Payers and Providers (pre-auth, approval, review

processes)

slide-11
SLIDE 11

Adoption: USA / Argonaut

  • Clinical Summary Query (R2 -> R4)
  • Provider Directory
  • Scheduling
  • Clinical Notes
  • Questionnaire
  • Active Health Nodes – provide services to enable a distributed

healthcare system

  • Clinical Summary (R4) required in next regulations
slide-12
SLIDE 12

Adoption: USA / Da Vinci

  • Prior Authorization
  • Coverage Decision
  • Payer Data Acquisition
  • Care Plan / Medicine Formulary Exchange
  • Clinical Data/Documentation/Record Exchange
  • Alerts
slide-13
SLIDE 13

Adoption: USA / Federal

  • Blue Button (2) – Government + Payer reporting of payment

information)

  • Quality Measure (Data Collection / Reporting)
  • National Provider Directory
  • NIH Endorsement
  • Public Health / Death reporting
  • VA Clinical care projects
slide-14
SLIDE 14

Adoption: US Vendors

  • Many personal health projects
  • Apple Healthkit – expanding scope & range
  • Many Data Analytics / Repository Projects
  • Google Brain Project
  • Many Toolkits / Frameworks
  • SmileCDR (HAPI!)
  • Microsoft Azure FHIR Server
slide-15
SLIDE 15

Adoption: Europe

  • International Patient Summary
  • “Document” – clinical summary for a patient
  • Corresponds roughly to Argonaut scope
  • Packaged as a document, not an API (push)
  • Makes rules about terminology (SNOMED CT)
  • Not just Europe
slide-16
SLIDE 16
  • MedMij - Personal health data in the

palm of your hand

  • Mobile access to all medical data over

life time

  • MedMij covers legal, organizational,

financial, semantic and technical aspects

  • 4 year initial project – 2016 - 2020

Adoption: Netherlands

slide-17
SLIDE 17

Adoption: England / UK

  • Interopen Project
  • Renal Clinical Repository
  • Many vendor projects
slide-18
SLIDE 18

Adoption: Australia

  • National Clinical Terminology Service (on Ontoserver)
  • Provider Directory Project (supporting secure messaging)
  • Document access to MyHR for mobile apps
  • Agency strongly interested in FHIR documents going forward
  • Lots of internal use in vendors (Telstra Health, Alcidion)
  • Some classic interop in GP space
  • Appointments / decision support
  • Not in common use in institutions yet
slide-19
SLIDE 19

Common Production Uses for FHIR

  • Exchanging Clinical Summary / Clinical Transfer
  • EHR Extensibility
  • Patient / provider registration
  • Data Analytics / Surveillance
  • Quality Measures / Clinical Performance
slide-20
SLIDE 20

Join Us

  • FHIR is a critical infrastructure enabler
  • A community solution for the IT requirements
  • But FHIR is not a solution to anything itself
  • Need new community infrastructure at many levels
  • Governance is critical: Build confidence and trust – open community treasure
  • Needs stable Governance foundations with consistent transparency
  • Join the community (FHIR, or others)
  • http://hl7.org/fhir, http://fhir.org
slide-21
SLIDE 21

Fueling FHIR for Change in the US

Mark L Braunstein, MD Visiting Scientist Australian eHealth Research Centre Professor of the Practice School of Interactive Computing Georgia Institute of Technology

slide-22
SLIDE 22

2016: 21st Century Cures Act Interoperability Data blocking Patient access (APIs) 2009: American Recovery and Reinvestment Act EHR Adoption and Meaningful Use

US Federal Interoperability Mandate

2019: Promoting Interoperability (PI) program 2014: Argonaut Project

slide-23
SLIDE 23

Using FHIR!

“By identifying the FHIR standard to implement our policies, we are promoting scalable data sharing, not just an individual patient record from hospital to hospital but a model that supports the flow of information across the entire healthcare system.”

  • -CMS Administrator, Seema Verma, HIMSS 2019
slide-24
SLIDE 24

24

Industry is Aboard

Amazon, Google, IBM, Microsoft, Oracle, and Salesforce CMS Blue Button 2.0 Developer Conference, July 30, 1019

“…we are fortunate to work with many teams and partners that draw on experiences across industries to support and accelerate the delivery of FHIR APIs in healthcare. Moreover, we are committed to introducing tools for the healthcare developer community. After the proposed rule takes effect, we commit to offering technical guidance based on our work including solution architecture diagrams, system narratives, and reference implementations to accelerate deployments for all industry stakeholders. We will work diligently to ensure these blueprints provide a clear and robust path to achieving the spirit of an API-first strategy for healthcare interoperability.”

http://blog.hl7.org/cloud-providers-unite-for-healthcare-interoperability-fhir

slide-25
SLIDE 25

App Ecosystems for Providers

slide-26
SLIDE 26

… and for Patients

26

FHIR Gateway SMART Apps

slide-27
SLIDE 27

What Problems?

slide-28
SLIDE 28

https://med.stanford.edu/content/dam/sm/ehr/documents/EHR-Poll-Presentation.pdf

EHRs: Mixed Results

slide-29
SLIDE 29

Notes

slide-30
SLIDE 30

CC/HPI: Abdominal Aortic Aneurysm Case

slide-31
SLIDE 31

Problem Specific Structured Documentation

slide-32
SLIDE 32

Key Findings Highlighted

slide-33
SLIDE 33

PE: Abdominal Aortic Aneurysm Case

slide-34
SLIDE 34

Procedure Reports

slide-35
SLIDE 35

Varicose Veins Assessment/Plan

slide-36
SLIDE 36

Procedure Note

slide-37
SLIDE 37

Questionnaires/Scoring

Quality of Life Score

slide-38
SLIDE 38

Notes Management

slide-39
SLIDE 39

Timeline Display

slide-40
SLIDE 40

Timeline Standalone

slide-41
SLIDE 41

Write-back

FHIR Documents Diagnoses/Problems (ICD-10) via FHIR or Proprietary API

  • Epic
  • Cerner
  • Allscripts
  • Athena
  • Nextgen
slide-42
SLIDE 42

Vault: Hierarchical Condiiton Coding

Each HCC is mapped to an ICD-10 code. Along with demographic factors (such as age and gender), insurance companies use HCC coding to assign patients a risk adjustment factor (RAF) score.

slide-43
SLIDE 43

PCPs Needs versus Capabilities

slide-44
SLIDE 44

Continuous, Coordinated Care

EHR Data Patient Generated Data Integrated patient messaging (provider coming)

slide-45
SLIDE 45

Targeted Information

slide-46
SLIDE 46

Trend Insights

slide-47
SLIDE 47

Suggested Evidenced-based Goals

slide-48
SLIDE 48

Predictive Analytics

Estimated A1C on current versus proposed therapy

slide-49
SLIDE 49

Personalized Clinical Decision Support

slide-50
SLIDE 50

Automatic Attribution

slide-51
SLIDE 51

Medicare

Reduce patient burden A research organization can pre-populate a medication lists for a patient during clinical trial enrollment. Streamline information about different kinds of care over time A primary care physician can access information on other patient care (e.g. related to behavioral health) to better inform treatment. Uncover new insights that can improve health outcomes A pharmacy can determine if a beneficiary gets healthier over time due to medication adherence. Access and monitor health information in one place A health application can aggregate data into a health dashboard for beneficiaries.

slide-52
SLIDE 52

VA API

slide-53
SLIDE 53

NIH

slide-54
SLIDE 54

Da Vinci Project: Value-based Care

54

“The goal is to enable improved patient care outcomes as well as empower better clinical decision making by shifting key information into provider teams’ work flow and sharing that information across organizational boundaries.”

https://www.pocp.com/biopharma-davinci-project

slide-55
SLIDE 55

Mentimeter- reflecting on the presentations…

slide-56
SLIDE 56

Australian initiatives implementing FHIR Quick FHIR

slide-57
SLIDE 57

Provider Directory

CSIRO Primary Care AU Base FHIR Core

Child Health

AU Standards

AU Argonaut

slide-58
SLIDE 58

MedVi View ew

  • Medication platform using a FHIR server with Cosmos DB
  • Framework provides a third party integration platform
  • MedsList and MedsRec key apps in ADHA testbed project – real-time discharge and admission between acute and primary care
  • Integrated with MyHR for upload of Meds Reconciliation (Pharmacist Shared Medication List – PMSL)

RTPM M (Safe feScr Scrip ipt and NDE)

  • Use of medication order and medication dispense order resources for API pre-check
  • Investigating EMR FHIR platforms for health service SSO

ePrescri scribin ing

  • Investigating conformance requirements and currently prototyping workflows.
  • Investigating potential use of Azure on FHIR
slide-59
SLIDE 59
  • HL7 Australia Profile
  • Supporting Secure Messaging
  • ADHA SMD POC
  • Federated Deployment
  • Service Registration Assistant
  • NHSD
  • VhDir International Guide
  • FHIR STU3 vs R4

FHIR Provider Directories

NHSD ADHA SRA Best Practice Telstra Health Secure Messaging HealthLink Secure Messaging Global Health Secure Messaging

slide-60
SLIDE 60

60 Paper Records Harmonised Content Clinical Information Specifications & Model FHIR Implementation Guide

Consumer Held Child Health Record

  • Sharing of child health information

between consumers and multiple providers

  • Jurisdictional Child Health Record

(baby book) Custodian

  • Full clinical and consumer

consultation by each jurisdiction

Harmonised Clinical & Consumer Content

  • Nationally agreed core components
  • f a child health record
  • Ensure each jurisdiction’s data is

represented in the national data set

  • CDHR Harmonisation Expert

Committee (Jurisdictional Child Health Record Custodians)

  • Australian Health Ministers Advisory

Council (AHMAC) – Health Services Principal Committee (HSPC)

  • Targeted Consultation by

jurisdictional Child Health Record custodians

Clinical Information Specifications & Model

  • Spec: How the information will be

structured in a digital record

  • Model: The clinical information

presented for clinical review and endorsement Spec:

  • Internal Review
  • Terminology Review by CSIRO

Model:

  • Clinical Informatics Endorsement

Committee (Peak Bodies & Colleges eg RACGP, RACP, etc) Spec:

  • Clinical TIGER team – Clinical

questions Model:

  • Endorsed through the organisation’s

standard endorsement process

  • Reviewed by National Research

Advisory Group to identify research gaps

Child Data Hub to CIS & Consumer App Information Exchange

  • Industry agreed specification for the

exchange of clinical information

  • HL7 Child Health Working Group
  • HL7 Australia (International

Standard)

  • FHIR Implementation Guide profiles

based on the HL7 Australia base resources collaboratively developed through the working group

High (≥50% Use) Medium (30-49% Use) Low (<30% Use) Child Information Nat % Use W/S Outcome Baby's Name 63 C Name of Birth Facility 100 A Date of Birth 100 C Time of Birth 75 A Sex (Male) 75 C Sex (Female) 75 C Child Information Nat % Use W/S Outcome This section is to be completed by a health professional 38 E Baby's Given Name/s 38 C Baby's Family Name 38 C Address 38 C Baby's Blood Group 38 E Child Information Nat % Use W/S Outcome UR (Unique Reference) 13 E Examiner Name 25 E Maternal Information Nat % Use W/S Outcome Mother's Name 63 C Pregnancy Complications 63 A Mother's Blood Group 63 E Labour (Spontaneous) 63 A Labour (Induced) 63 A Labour (Induced - Reason) 63 A Type of Birth (Normal/Vaginal) 75 A Type of Birth (Breech) 75 A Type of Birth (Forceps) 75 A Type of Birth (Caesarean) 75 A Type of Birth (Vac Ext) 75 A Maternal Information Nat % Use W/S Outcome Anti D Given 38 E Labour Complications 38 E Type of Birth (Home) 38 E Type of Birth (Other) 38 E Type of Birth (Other, Specify Details) 38 E Postpartum issues 38 E Maternal Information Nat % Use W/S Outcome Mother's Given Name 25 C Mother's Family Name 25 C Father's Name 13 C Mother's Date of Birth 13 E Mother's Home & Mobile Phone 25 E MRN (medical record number) 25 C Type of Birth (write) 25 E Type of Birth (water) 25 E Delayed cord clamp 13 T Birth Complications 25 E Maternal GBS Status 13 E Maternal GBS Status - Antibiotics given? 13 E Maternal rubella TITRE 13 E Mother has had in pregnancy (CMV / Toxoplasmosis / Rubella 13 E Workshop Identified Nat % Use W/S Outcome Fathers Given & Family Names A Sex Other T Other Parent A Legend A Agreed (Include) AA Agreed for ATSI T To be Agreed C Core Data O Out of Scope E Exclude

CDH CDHR Cl Clinical & Co Consumer r Inform rmation Management

Purpose Review/Endorse Artefact Consult

Data Source Conceptual Data Item Logical Data Item Logical Data Item Description Logical Data Item Code (If Applicable) Field Type ValueSet Elements ValueSet Element Code ValueSet Description Field Type Format Priority Cardinality Harmonised (H) Content impacts from orchestartion (O) (operational) (OP)/ (F) FHIR / restrictions / enhancements ( E ) BOLD equals Harmonised data Name of the Data Item The description of the logical data item description SNOMED Code which represents the data item FHIR Date, text, checkbox, radio button, numeric, drop down list Name of ValueSet Element Item BOLD equals Harmonised data SNOMED Code which represents the data item The description of the element Date, text, checkbox, radio button, numeric, ValueSet eg DD:MM:YYY Y Mandatory/ Required/ Optional Relationshi p of x to y eg IHI is 1..1 First Name (Given) First Name - will represent the name of baby ie 'Baby of <mother first name>' FHIR Text Text String Required 0..1 Last Name (Family) Last Name - will represent the last name of mother FHIR Text Text String Required 0..1 First Name (Given) First name of Mother FHIR Text Text String Required 0..* Last Name (Family) Last name of mother FHIR Text Text String Required 0..1 OR Full Name Full Name of Mother (used where First and Last names are not split into separate fields in a system) FHIR Text Text String Optional 0..1 *Street Address Street name, number, PO box etc FHIR Text Text String Optional 0..* City Name of City, Town FHIR Text Text String Optional 0..1 State State in which the baby lives FHIR Text Text String Optional 0..1 Postal Code Postal code for area FHIR Text Text String Optional 0..1 Country Name of Country FHIR Text Text String Optional 0..1 First Name (Given) First name of Father FHIR Text Text String Optional 0..* Last Name (Family) Last name of Father FHIR Text Text String Optional 0..1 OR Full Name Full Name of Father (used where First and Last names are not split into separate fields in a system) FHIR Text Text String Optional 0..1 H Address H Father's Name Newborn Delivery Health Interaction (DEFINITIONS) - LOGICAL MODEL NOTES / VERSION NO: 19/10 - 0.6 H Baby's Name H Mother's Name
slide-61
SLIDE 61

Queensland Clinical Terminology Service (QCTS)

Vision

To provide a lasting and effective solution for the management and meaningful use of up-to-date coding system reference data as well as associated artefacts (such as value sets and concept maps) which meets Queensland Health’s business and clinical needs.

Use of HL7 Fast Healthcare Interoperability Resources (FHIR)

  • Introduction of

– ValueSet, ConceptMap, and CodeSystem FHIR resources to represent local terminology subsets, maps, and coding systems respectively. – Terminology server applications exposing the HL7 FHIR Terminology Service API for application integration

  • Adoption of:

– FHIR R4 – The Australian Digital Health Agency’s National Clinical Terminology Service (NCTS) FHIR specifications for content types and Conformant Server Applications – The AEHRC Ontoserver syndicating terminology server

61

slide-62
SLIDE 62

Queensland Clinical Terminology Service (QCTS)

62

Solution Overview

slide-63
SLIDE 63

The Clinical Genomics Order Cycle

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

start

slide-64
SLIDE 64

Who

CSIRO AEHRC HL7, LOINC, SNOMED GA4GH

What

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

  • LOTS and LOTS of code systems in

the genomic space – bringing them into official FHIR code systems and implementing into Ontoserver etc

slide-65
SLIDE 65

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

Who

CSIRO AEHRC QGHA Genomics England

What

  • Smart on FHIR clinical tools

hooked into EHRs

  • Genomics England has an
  • rdering system that uses FHIR

data models internally

  • Phenopackets work to ensure

pedigree etc can align against a FHIR data model

slide-66
SLIDE 66

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

Who

Melbourne Genomics

What

  • GenoVic uses FHIR as its API at

the boundaries – and for internal data models

  • consent codes and

representation to standardise encoding of genomic consent forms (very much WIP)

slide-67
SLIDE 67

Who

HL7 FHIR WG (international)

What

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

  • aligning representation of

variants to match thinking in GA4GH

  • existing standards are the kings

here (VCF, BAM) despite certain limitations

slide-68
SLIDE 68

Who

HL7 FHIR WG (international)

What

Clinical system(EHR) Lab

  • rder(LIMS)

Bioinformatics Variant Interpretation Lab report

  • DiagnosticReport profiles to

report back genomic results in standardised discrete units – across various genomic domain (cancer v rare disease etc)

  • In Australia – currently more

likely PDF

slide-69
SLIDE 69

Existing Specifications Harmonised Content Primary Care Data Dictionary FHIR Implementation Guide

Primary Care, Standards Data Specifications, Data Sets, KPIs, Assessments, FHIR, OpenEHR Identification of all the existing specifications in Primary Care that would inform the development of the core data requirements. Initial meeting of stakeholders to identify all potential data inputs, use cases and priorities for the projects. Community established with clinical and technical working groups. Use case agreed- reusable core data set, associated SNOMED CT Value Sets and a FHIR IG to exchange.

Harmonised clinical data items and identification of core common items

Candidate core data elements which are common to multiple existing specifications, that enable structured data recording and data reuse. Clinical Content and Technical Working Groups consensus on the core data items to be defined and included in a data dictionary and identification of the first use cases to exchange these core data items. Outputs progressively developed and iterated through a series of face to face workshops (4) and webconferences (5) Primary Care clinical information model Release 1 of the Data Dictionary defines the core common data elements to enable quality use of information as well as enable the safe and meaningful exchange of information to other care providers. The Dictionary includes: meta data, definitions and recommended terminology bindings

Enter once, multiple use and interoperable exchange and reuse

Community, consensus based development process with multidisciplinary clinical content and technical working group. Endorsement proposed to be progressed through clinical colleges and professional groups. FHIR IG- Primary Care Au Practice to Practice Record Exchange An industry agreed specification, informed by the Primary Care Data Dictionary Core Common Model for the exchange of an individuals record when they request a transfer of their records from their current practice to a new practice. FHIR IG profiles based on the HL7au Base resources, progressively developed and tested through a Community process. Endorsement proposed to be progressed through HL7au

Purpose Development/Review Artefact

Primary Care Data Quality P2P

slide-70
SLIDE 70

Australia’s National Science Agency

Thank you

Come and visit us at the CSIRO booth # 35 Our researchers and scientists would love to share more with you about how their work is enabling digital health in Australia and around the world.