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, FHIR provides: HTTP JSON • A REST Server with Requests Responses healthcare-specific information model GET POST PUT DELETE 4
A Few Key Features Operationally, FHIR provides: Demographics Hx Record • A REST Server with Problems healthcare-specific Medications information model Allergies Summaries • A simple & extensible Data Model 5
A Few Key Features FHIR Requests FHIR Resources Operationally, FHIR provides: • A REST Server with FHIR REST API healthcare-specific information model • A simple & extensible FHIR Resources Data Model 6
Adding FHIR to Existing Platforms FHIR Requests FHIR Resources FHIR REST API Message & Document Data Transforms Database Parsers Proprietary FHIR Mapping Data Model
Native FHIR Clinical Data Repository Message & Document Parsers Data Transforms Patient Applications FHIR Data Model Database FHIR API Provider Applications Payer Access
Clinical Data Processing Transforming Data into Information FHIR JSON Documents Exchanged Info; • Cerner CCDA, HL-7 v3 • EPIC CCDA, HL-7 v2 Transform data into • Labcorp HL-7 v2 standardized FHIR JSON • Quest HL-7 documents. • Hospital Lab HL-7 • Radiology HL7,DICOM This lets us take data • from any system and Blue Button make it useful for • Other repositories patients, providers, and • Any clinical data payers. • Etc.. 9
Clinical Data Processing Building Universal Health Records Demographics FHIR JSON Documents Hx Record Once the data is Problems organized as useful Medications health Allergies information, we can build Summaries aggregated universal health records. 10
Native FHIR Clinical Data Repository Message & Document Parsers Data Transforms Patient Applications FHIR Data Model Database FHIR API Provider Applications Payer Access
A Push from the Final Rule • 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
FHIR as a Strong Data Foundation • 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
Thank You Visit Us on the Web www.medicasoft.us info@medicasoftllc.com
Recommend
More recommend
