Embed Size (px)
DESCRIPTION
IHE Concrete Implementation. June, 2010. Motivation for IHE implementation. We are a group of organizations who have already implemented IHE profiles We recognized the user stories – IHE already addresses them We could leverage existing products and toolkits – it wasn’t scary - PowerPoint PPT Presentation
Citation preview
June, 2010
We are a group of organizations who have already implemented IHE profiles
We recognized the user stories – IHE already addresses them
We could leverage existing products and toolkits – it wasn’t scary
We can get this done fast
Optional HISP hops
XDR backboneStep up and down to edges
UDDIDirectory
Destination
HISPSourceHISP
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: [email protected] To: [email protected]
Source: Allscripts Source HISP: MedAllies Destination/
Destination HISP: Epic
User stories: 1, 2, 3, 4, 6
From: [email protected] To: [email protected]
Source/Source HISP: Epic Destination HISP: MedAllies Destination: email client
User stories: 1, 2, 3, 4, 6, 7, 8, 9, 10, 11
From: [email protected] To: [email protected]
Source: email client Source HISP: GE / MedAllies Destination /
Destination HISP Epic’s Lucy PHR
User stories: 6, 7, 8, 9, 10, 11
From: [email protected] To: [email protected]
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
5: Laboratory sends lab results to ordering providerLaboratory may not have a patient ID. If they do,
they would likely use XDR on the sending edge. If not:A: Use order number as pseudo patient identifierB: Relax XDR metadata requirements
12: Primary care provider sends patient immunization data to public healthSeveral initiatives within CMS already use XDR on
the receiving edge, so this may just be scenario 1.
Straightforward integration with NHIN Exchange
One metadata model supports both minimal and extended metadata
Developed, maintained, and enhanced through a formal and open process
Can work across the continuum of care settings, from small practices to integrated delivery networks
Supports point-to-point encryption; doesn’t currently support non-trusted intermediaries
Intended recipient metadata integrated into content container metadata
ebXML can look daunting
SOAP looks hard
EHRA supportNHIN Direct can make it to the real world
faster with IHE
Maturity of the approach: small changes to XDR are much preferable to inventing something newThis is a profile, not just a protocol
It’s simple, scalable, and sustainable
