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
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
Australia’s National Science Agency
Grahame Grieve, Mark Braunstein, Michael Lawley, Brett Esler, Reuben Daniels, Kate Ebrill, Steve Badham, Andrew Patterson, Danielle Bancroft, Brian Postlethwaite August 2019
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
Grahame Grieve 13-Aug 2019 Melbourne (IHE/HIC)
Open Community Open Standard
healthcare information
web infrastructure (social media)
connected to world wide health community
healthcare information
where possible
healthcare standards
(http://hl7.org/fhir)
Standards History
Implementation History
processes)
healthcare system
information)
palm of your hand
life time
financial, semantic and technical aspects
Mark L Braunstein, MD Visiting Scientist Australian eHealth Research Centre Professor of the Practice School of Interactive Computing Georgia Institute of Technology
2016: 21st Century Cures Act Interoperability Data blocking Patient access (APIs) 2009: American Recovery and Reinvestment Act EHR Adoption and Meaningful Use
2019: Promoting Interoperability (PI) program 2014: Argonaut Project
“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.”
24
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
26
FHIR Gateway SMART Apps
https://med.stanford.edu/content/dam/sm/ehr/documents/EHR-Poll-Presentation.pdf
Quality of Life Score
FHIR Documents Diagnoses/Problems (ICD-10) via FHIR or Proprietary API
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.
EHR Data Patient Generated Data Integrated patient messaging (provider coming)
Estimated A1C on current versus proposed therapy
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.
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
MedVi View ew
RTPM M (Safe feScr Scrip ipt and NDE)
ePrescri scribin ing
NHSD ADHA SRA Best Practice Telstra Health Secure Messaging HealthLink Secure Messaging Global Health Secure Messaging
60 Paper Records Harmonised Content Clinical Information Specifications & Model FHIR Implementation Guide
Consumer Held Child Health Record
between consumers and multiple providers
(baby book) Custodian
consultation by each jurisdiction
Harmonised Clinical & Consumer Content
represented in the national data set
Committee (Jurisdictional Child Health Record Custodians)
Council (AHMAC) – Health Services Principal Committee (HSPC)
jurisdictional Child Health Record custodians
Clinical Information Specifications & Model
structured in a digital record
presented for clinical review and endorsement Spec:
Model:
Committee (Peak Bodies & Colleges eg RACGP, RACP, etc) Spec:
questions Model:
standard endorsement process
Advisory Group to identify research gaps
Child Data Hub to CIS & Consumer App Information Exchange
exchange of clinical information
Standard)
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 ExcludeCDH 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 NameVision
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)
– 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
– 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
62
Solution Overview
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
start
CSIRO AEHRC HL7, LOINC, SNOMED GA4GH
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
the genomic space – bringing them into official FHIR code systems and implementing into Ontoserver etc
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
CSIRO AEHRC QGHA Genomics England
hooked into EHRs
data models internally
pedigree etc can align against a FHIR data model
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
Melbourne Genomics
the boundaries – and for internal data models
representation to standardise encoding of genomic consent forms (very much WIP)
HL7 FHIR WG (international)
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
variants to match thinking in GA4GH
here (VCF, BAM) despite certain limitations
HL7 FHIR WG (international)
Clinical system(EHR) Lab
Bioinformatics Variant Interpretation Lab report
report back genomic results in standardised discrete units – across various genomic domain (cancer v rare disease etc)
likely PDF
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
Australia’s National Science Agency
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.