Project Goals/Objectives - the “IT”
Technology/Implementation Services -
technology the provides seamless interoperability
“Year of engineering(2013)” - one example of
short to long term - one or more instantiations to set of specifications
reference implementation that deploys a set of specifications - one example that has utility(short term)
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
Deployment Community - Difference subsets of communities - Implementer, Developer, User, Providers
- There is a core team and then there is others that will come in with their own money
- want to focus on the underserved
- learn by doing - standard evolves from practice
- build a collection of organizations with some skin in the game“Have an anchor and control it”
Short Term (1-3yrs)
development stakeholders (e.g., System integrators, solution providers)
development process documented
technical roadmap process defined and public
governance for component communities
sub-community charter and dependency lists
sub-community leaders
IP statement and review
system design document
reference implementation w/ plug n play
implementation stakeholders: System integrators, solution providers.
provide and educate people about opportunities
best practices guidelines
document samples and examples
reference implementations lessons learned
end-user stakeholders:
educate them on the value prop
case studies
rules of engagement - how to get involved, stages of engagement, feeds measurement
get assessment of needs, values and readiness
express fundamentals of participation
express technology deliverables
create a number of end-user groups - community of practice (e.g, discussion forums, meetings, implementors conference)
competitors stakeholders:
create a more concise list of competitors
create a short list of prime competitors (list of 3-5)
engage with/visit prime competitors - bring them in as collaborators
mind share / collaborate with competitors
make a clear definition of what a competitor is for OHIE
Medium Term (3-5yrs)
development stakeholders:
implementation stakeholders:
at least one unanticipated use of OpenHIE components
provide means for opportunities
university / innovations program
end-user stakeholders:
competitors stakeholders:
Future
implementation outsourced “self serve”
reusable license
franchise - the approach/process
defined process
implementation guide for each of the HIE components as well as a full “HIE implementation guide”
grow attendance on community calls
development stakeholders:
implementation stakeholders:
certification to differentiate
end-user stakeholders:
competitors stakeholders:
Measurement of Success
...
goals lead back to our mission
...
each goal will have a measurement of success
...
have one single measurement
...
have a third party reporting on in country implementation
...
implementing at depth in three - at scale in three
...
On May 20-21, 2013 an OpenHIE workshop was held At Regenstrief Institute in Indianapolis to create a written, first-round vetted five year OpenHIE strategic plan. The following goals for 2013 came out of that meeting Technology & Implementation Services & Deployment Community (Implementer, Developer, User, Providers).