June, 2010

SOAP / IHE Concrete ImplementationSOAP / IHE Concrete Implementation

Optional HISP hops

XDR backboneStep up and down to edges

UDDIDirectory

Destination

HISP

Source

HISP

Step upto XDR

Step upto XDR

Step downfrom XDR

Step upto XDR

SMTP

REST

XMPP

XDR, XDM

SMTP

REST

XMPP

XDR, XDM

SourceSystems

DestinationSystems

Provide and Register

1. EMR to EMR2. EMR to email3. Email to PHR4. Web app to email

From: harry.winston@goodhealthclinic.org To: edward.stukel@epic.ehr.nhin.org

Source: Allscripts Source HISP: MedAllies Destination/

Destination HISP: Epic

User stories: 1, 2, 3, 4, 6

From: harry.winston@goodhealthclinic.org To:

john.smith@happyvalleyclinic.nhindirect.org

Source/Source HISP: Epic Destination HISP: MedAllies Destination: email client

User stories: 1, 2, 3, 4, 6, 7, 8, 9, 10, 11

From: harry.winston@goodhealthclinic.org To: marlowephillips@lucy.phr.nhin.org

Source: email client Source HISP: GE / MedAllies Destination /

Destination HISP Epic’s Lucy PHR

User stories: 6, 7, 8, 9, 10, 11

From: harry.winston@goodhealthclinic.org To:

john.smith@happyvalleyclinic.nhindirect.org

Source: IBM web app Source HISP: GE / Vangent Destination HISP: MedAllies Destination : email client

User stories: 1, 2, 3, 4, 6, 7, 8, 9, 10, 11

12

The question of metadataXD* profiles provide a consistent structure for

metadata that is independent of content\When we realize we’re dealing with user

stories that require metadata, we’ll have a place to put it

We can degrade down to zero patient-specific metadata if that is required by policy - we can bring this to IHE to profile it if we want

Maturity of the approach: small changes to XDR are much preferable to inventing something newThis is a profile, not just a protocol

Trivial interoperability with NHIN Exchange

Why SOAP / IHEWhy SOAP / IHE