Interoperability Doug Fridsma, MD PhD President & CEO, AMIA - - PowerPoint PPT Presentation
Interoperability Doug Fridsma, MD PhD President & CEO, AMIA Getting to Interoperability To get to interoperability (or to avoid information blocking) we need a common understanding of the problem Cant solve the problem all at
Doug Fridsma, MD PhD President & CEO, AMIA
2 AMIA PowerPoint Template
common understanding of the problem
problem
Interoperability (IEEE)
Interoperability only makes sense in the context of what you want to DO
Transitions of Care Care summary Clinical Trial Eligibility Public Health Reporting Public Health Reporting
the ”thing you want to do”
there is no shared “building blocks”
8
“You can’t build a skyscraper by nailing 10,000 dog houses together”
Patient Practice Population Public
Think HORIZONTALLY rather than vertically
Informatics, standards, testing, business drivers, governance
Big Data and population health Electronic Health Record and Quality Consumer empowerment Clinical and Translational Research
Legal Responsibilities (e.g. HIPAA, 42 CFR Part 2)
Public Policy
Contractual Decisions (e.g. Epic App Orchard)
Intellectual Property
Market-based Motivations (e.g. ACOs)
Business Drivers
When to apply the data (e.g. lab test results)
Workflow (dynamic)
How to apply the data (e.g. Admission v. Discharge Summary)
Context (static)
Purpose-specific APIs and services that leverage the other four layers
Services
Terminologies, Structured data, coded (e.g. ICD-10, SNOMED)
Semantic
Message formatting (e.g. CCDA v2)
Syntactic
How the message move from A to B
Transport
How we ensure that messages are secure and private
Security
Traditional technology stack Implementation Policy and Business drivers API
Legal Responsibilities (e.g. HIPAA, 42 CFR Part 2)
Public Policy
Contractual Decisions (e.g. Epic App Orchard)
Intellectual Property
Market-based Motivations (e.g. ACOs)
Business Drivers
When to apply the data (e.g. lab test results)
Workflow (dynamic)
How to apply the data (e.g. Admission v. Discharge Summary)
Context (static)
Purpose-specific APIs and services that leverage the other four layers
Services
Terminologies, Structured data, coded (e.g. ICD-10, SNOMED)
Semantic
Message formatting (e.g. CCDA v2)
Syntactic
How the message move from A to B
Transport
How we ensure that messages are secure and private
Security
Traditional technology stack Implementation Policy and Business drivers API
Legal Responsibilities (e.g. HIPAA, 42 CFR Part 2)
Public Policy
Contractual Decisions (e.g. Epic App Orchard)
Intellectual Property
Market-based Motivations (e.g. ACOs)
Business Drivers
When to apply the data (e.g. lab test results)
Workflow (dynamic)
How to apply the data (e.g. Admission v. Discharge Summary)
Context (static)
Purpose-specific APIs and services that leverage the other four layers
Services
Terminologies, Structured data, coded (e.g. ICD-10, SNOMED)
Semantic
Message formatting (e.g. CCDA v2)
Syntactic
How the message move from A to B
Transport
How we ensure that messages are secure and private
Security
Traditional technology stack Implementation Policy and Business drivers API
Legal Responsibilities (e.g. HIPAA, 42 CFR Part 2)
Public Policy
Contractual Decisions (e.g. Epic App Orchard)
Intellectual Property
Market-based Motivations (e.g. ACOs)
Business Drivers
When to apply the data (e.g. lab test results)
Workflow (dynamic)
How to apply the data (e.g. Admission v. Discharge Summary)
Context (static)
Purpose-specific APIs and services that leverage the other four layers
Services
Terminologies, Structured data, coded (e.g. ICD-10, SNOMED)
Semantic
Message formatting (e.g. CCDA v2)
Syntactic
How the message move from A to B
Transport
How we ensure that messages are secure and private
Security
Traditional technology stack Implementation Policy and Business drivers API
Legal Responsibilities (e.g. HIPAA, 42 CFR Part 2)
Public Policy
Contractual Decisions (e.g. Epic App Orchard)
Intellectual Property
Market-based Motivations (e.g. ACOs)
Business Drivers
When to apply the data (e.g. lab test results)
Workflow (dynamic)
How to apply the data (e.g. Admission v. Discharge Summary)
Context (static)
Purpose-specific APIs and services that leverage the other four layers
Services
Terminologies, Structured data, coded (e.g. ICD-10, SNOMED)
Semantic
Message formatting (e.g. CCDA v2)
Syntactic
How the message move from A to B
Transport
How we ensure that messages are secure and private
Security
Traditional technology stack Implementation Policy and Business drivers API
Transitions of Care Care summary Clinical Trial Eligibility Public Health Reporting Public Health Reporting
AMIA PowerPoint Template 15
What is needed: A common format for granular data
cases
Restore the importance of the narrative and unstructured text
Patients are more than a collection of discrete data
The unstructured data is where discoveries are made
Restore the balance of power for access to data
When you send, conform to the standard
When you receive, accept ANY version that conforms to the standard
Create the conditions of interoperability when you create the standard, rather than when you implement it
AMIA @AMIAinformatics Official Group of AMIA AMIA informatics www.amia.org #WhyInformatics
Doug Fridsma MD PhD
23
Fridsma@amia.org
AMIA @AMIAinformatics Official Group of AMIA AMIA informatics www.amia.org #WhyInformatics AMIA is the professional home for more than 5,400 informatics professionals, representing frontline clinicians, researchers, public health experts and educators who bring meaning to data, manage information and generate new knowledge across the research and healthcare enterprise.
24 AMIA 2017 | amia.org