1. Technology the provides seamless interoperability
2.  “Year of engineering(2013)” - one example of this
3.  Short to long term - one or more instantiations to set of specifications
4.  Reference implementation that deploys a set of specifications - one example that has utility(short term)
5.  Forcing function is the technology

Short Term - 1-3yrs - version 1 limited to early adopters, version 2 pick up features

• Interoperability

• ESB - what it means

• Hardened components - list some - what can they download and use

• Implementation Services that are going to change

• Target the underserved

• Target standard set of partners

• Produce the code that

• Reference implementation that gets used

• Identify and embrace standards

• Engage with SDOs through connect-a-thons and other appropriate processes to contribute to benefit evolving standards

• feed information back from real world examples

• Use when available

• Input back to SDOs when issues - be part of the solution

• be authors of what can be endorsable

Medium term - 3-5 yrs

• multiple version of the components (by different development teams)

• multiple implementations of the technology in varied environments (all components)

• documented specifications

• engage with SDOs and create when they don’t exist.

Future State 

• The technologies and approach are working in high resource countries as well.

• full embrace of the SDOs

• # of endpoint solutions and 40% market share

• every POC will start with OpenHIE as the infrastructure

• Will presume a future where OpenHIE is mandatory