SLIDE 1
Advancing Healthcare Data Interoperability Using FHIR
August 2020
- Key FHIR Attributes
- FHIR and Existing Platforms
- Native FHIR
- FHIR and the Final Rule
- Summary
2
Interoperability Using FHIR August 2020 Agenda Key FHIR Attributes - - PowerPoint PPT Presentation
Interoperability Using FHIR August 2020 Agenda Key FHIR Attributes - - PowerPoint PPT Presentation
Advancing Healthcare Data Interoperability Using FHIR August 2020 Agenda Key FHIR Attributes FHIR and Existing Platforms Native FHIR FHIR and the Final Rule Summary 2 FHIR Everywhere 3 A Few Key Features Operationally,
SLIDE 2
SLIDE 3
3
FHIR Everywhere
SLIDE 4
Operationally, FHIR provides:
- A REST Server with
healthcare-specific information model
4
A Few Key Features
DELETE PUT POST GET
HTTP Requests JSON Responses
SLIDE 5
Operationally, FHIR provides:
- A REST Server with
healthcare-specific information model
- A simple & extensible
Data Model
5
A Few Key Features
Demographics Hx Record Problems Medications Allergies Summaries
SLIDE 6
Operationally, FHIR provides:
- A REST Server with
healthcare-specific information model
- A simple & extensible
Data Model
6
A Few Key Features
FHIR REST API FHIR Resources FHIR Requests FHIR Resources
SLIDE 7
Adding FHIR to Existing Platforms
Database Proprietary Data Model
Data Transforms Message & Document Parsers
FHIR REST API FHIR Mapping FHIR Requests FHIR Resources
SLIDE 8
Native FHIR Clinical Data Repository
FHIR API Database FHIR Data Model
Data Transforms Message & Document Parsers
Provider Applications Patient Applications Payer Access
SLIDE 9
9
Clinical Data Processing
Transforming Data into Information
Exchanged Info;
- Cerner CCDA, HL-7 v3
- EPIC CCDA, HL-7 v2
- Labcorp HL-7 v2
- Quest HL-7
- Hospital Lab HL-7
- Radiology HL7,DICOM
- Blue Button
- Other repositories
- Any clinical data
- Etc..
Transform data into standardized FHIR JSON documents. This lets us take data from any system and make it useful for patients, providers, and payers.
FHIR JSON Documents
SLIDE 10
10
Clinical Data Processing
Building Universal Health Records
FHIR JSON Documents
Demographics Hx Record Problems Medications Allergies Summaries
Once the data is
- rganized as useful
health information, we can build aggregated universal health records.
SLIDE 11
Native FHIR Clinical Data Repository
FHIR API Database FHIR Data Model
Data Transforms Message & Document Parsers
Provider Applications Patient Applications Payer Access
SLIDE 12
- ONC Cures Act Final Rule
– Interoperability via standardized API: FHIR API – Defined set of data elements: USCDI – Single patient & multi-patient access
- CMS Interoperability & Patient Access Final Rule
– Claims data available to patients (via FHIR API) – Provider directory (via FHIR API) – Payer-to-payer exchange – ADT notifications
12
A Push from the Final Rule
SLIDE 13
- Ideal health IT systems technology
– Fits modern architecture – Robust, flexible data model – Development friendly
- Meaningful effort is still required
– Patient matching – Data quality – Data completeness
- But FHIR is a significant step forward in allowing us
to extract information, and value, from our data
13
FHIR as a Strong Data Foundation
SLIDE 14