15
Interoperability: Where are we now and where are we going? www.amia.org

Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Interoperability: Where are wenow and where are we going?

amia.orgwww.amia.org

Interoperability: Where are wenow and where are we going?

Page 2: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

STANDARDS AND INTEROPERABILITY:HARD IN THE CONCRETE, IMPOSSIBLEIN THE ABSTRACT

Page 3: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Interoperability only makes sense in the context of whatyou want to DO

Interoperability (IEEE)• Ability of two or more systems to exchange information• Ability of those systems to use the information that has

been exchanged

Page 4: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

THERE WILL NEVER BE ONE MODELTO RULE THEM ALL

Page 5: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Different information models of thesame information

PatientsPatients TestsTests StudiesStudies

ClinicalCare

ResearchData warehouse Clinical Studies

amia.org

VisitsVisits

Lab testsLab tests

ResultsResults

ResultsResults

PatientsPatients

ArmsArms

PatientsPatients

ResultsResults

Page 6: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Meaning

ContentStructure

Technical stack

How should well-defined values be coded so thatthey are universally understood?

How should the message be formatted so that itis computable?

amia.org6

How does the message move from A to B?

How do we ensure that messages are secure andprivate?

Transport

Security

ServicesPurpose-specific APIs and services that leveragethe 4 other building blocks

Page 7: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

THE ONLY STANDARD YOU NEVERCHANGE, IS A STANDARD YOU NEVERUSE

Page 8: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Standards life cycle

Widely adopted, but declining value

Currentstate-of-the-art

Mapping?

amia.org

You are here

Newand emergingva

lue

time

Page 9: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

A PATH OF LEAST REGRET: THREETHINGS WE NEED

Page 10: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

BUILD DOCUMENTS FROM DATA,NOT THE OTHER WAY AROUND

Page 11: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

What is needed: A common formatfor granular data• Quality Measures• Clinical Decision Support• Registries• Common data formats for

– Text data– Categorical data– Numerical data– More…

amia.org

• Quality Measures• Clinical Decision Support• Registries• Common data formats for

– Text data– Categorical data– Numerical data– More…

Page 12: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

FULL EXPORT OF THE PATIENTRECORD (AND NARRATIVE)

Page 13: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Restore the importance of thenarrative and unstructured text• Move patient between vendor “ecosystems”• Precision medicine• Restore the balance of power for access to

data• Maintain the importance of the narrative in

the medical record

amia.org

• Move patient between vendor “ecosystems”• Precision medicine• Restore the balance of power for access to

data• Maintain the importance of the narrative in

the medical record

Page 14: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

amia.org

TEST BOTH SIDES OF EXCHANGE

Page 15: Interoperability: Where are we now and where are we going? · STANDARDS AND INTEROPERABILITY: HARD IN THE CONCRETE, IMPOSSIBLE IN THE ABSTRACT. Interoperability only makes sense in

Postel’s principle

• When you send, conform to the standard– Pick a set of options and make sure it conforms to

a valid instance of the standard• When you receive, accept ANY version that

conforms to the standard– Any variation that is valid

• Create the conditions of interoperability whenyou create the standard, rather than whenyou implement it

amia.org

• When you send, conform to the standard– Pick a set of options and make sure it conforms to

a valid instance of the standard• When you receive, accept ANY version that

conforms to the standard– Any variation that is valid

• Create the conditions of interoperability whenyou create the standard, rather than whenyou implement it