OHT Update:
 Bruce indicated that finances are thin but under control and OHT is operating in the green
 Membership has been growing slowly/steadily, with increasing broad international participation
 Bruce’s tenure/objective was to stabilize operations, shore up financial components, and
establish core operating procedures. Established US domestic footing for financial, tax,
accounting purposes.
 Executive Director search is underway and two final candidates have been downselected. The
search committee will report out imminently their recommendation en route to a Board
decision in June.
Determining Areas to Play:
 Focus on the short-term – Success to declare at HIMSS ‘15
 CONNECT has real opportunity
o Focus on adapting it to use / apply IHE, more than NHIN:;
Create a roadmap applied to Healtheway
o Creation of adapters / lowering bar to play and interoperate
o Hosted environment to provide for development and testing
 Recommendation to define “success objective” to achieve by HIMSS. What does success look
like?
o Note that we are a member-driven organization; our success stems from making our
members successful
o Seek intersect between what is good for the member and good for the community/
ecosystem
 Need to define goals in short term chunks keeping in mind the long term. Need to execute in
stages.
o Potentially define 3 goals along different dimensions / OHT Business Objective,
Technology objective, health industry outcome objective.
 Benefits
o Advertise partnerships and outcomes as a result of OHT membership
o Demonstrated participation in industry leadership / marketing benefit
Technology Goals:
 Make it easier to use/consume OHT products. Make it easier for projects to consume/adopt our
technology
 Create a project that complements CONNECT and makes it a broader more impactful platform
than when it came into OHT.
 Establish a specific technology enabler supporting Meaningful Use Stage 3 (MU3) with
international appeal
 (BH): Healthcare identifiers are made available from some interface; development of an
interface to VUHID server system to allow creation of a module to allow consumers to use the
OSS tool and provide access to these identifiers. Creation of a tool that implements the 10
transactions associated with these identifiers. Allow others to acquire and use these identifiers.
 Patient provided unique identifiers can be provided / offered and applied across multiple
organizations
 For OHT to be in a position to be able to provide testing and integration services and
infrastructure to the advantage of the open source community; and offer fee-for-service
capabilities that go beyond “Happy Path”
 Can we augment HIE capability with CONNECT with some analytics capability. Use info
exchange as a collector for “big data”. Translation of streams of data into analytics-friendly
form.
 Establish an applications-based platform. Ability to support mobile apps. Shared application
infrastructure / modular
Outcome Goals:
 Evidence based improvement in important healthcare outcomes (e.g., patient safety) resulting
from reduced identification disconnects by leveraging OHT Tools/solutions.
 Some combination of OHT projects being used to solve a healthcare challenge for underserved
communities
 Front page business success driven in part by OHT
 Creation of this module to allow anyone who wants to use these identifiers. “Solve the Patient
Matching Problem”. Realize the benefits that come when you eliminate duplicate records in
EMPI/ overlap of EMPI. Privacy benefits through more efficacy in privacy management. Better
opportunity to correct identity theft, fraud, etc.
 Alignment with [US] Federal Identity program (FICAM, for instance); US government approved
identity program.
 Sharable access consent policy ; ability to have technology in place to allow SAMSHA’s vision for
shared consent policy to be applied / used by patients
 Improve efficacy of patient matching
“OHT” Business Goals:
 Establish new revenue stream previously unrealized by OHT
 Realize revenue associated with the use of voluntary universal identifier infrastructure in
revenue sharing / SAAS model
 Be in a position to raise funding to provide OHT sponsored or fostered grants for key
components (e.g., $500k grants) and have one awarded by year-end
 Become the preferred destination / home for OSS healthcare projects (e.g., attract other OSS
projects into our community/umbrella)
 Demonstrable increase of membership (e.g., 25%)
 OHT to be a recipient of at least 1 grant generating direct or management oversight revenue;
cost-neutral at a minimum
 Demonstrate value and support of OHT member needs (e.g., Increase community/ networking
events.)
 Land a mainstream EHR vendor as part of the OHT community ; position as a complement to
commercial offerings
Other Items (Not a natural fit into the above buckets):












For CONNECT, need to attract the right audience. Potentially need to create resource pool
experienced in CONNECT.
Bringing on new projects needs to create a collateral community benefit (e.g., a new project
that brings in new members; a new initiative that brings in new IP, etc.) May be direct or
indirect benefit.
Need to provide business model for crowdsourced funding (multiple stakeholders into a shared
pot)
Not taking advantage of social media / advertising outlets
Kanter Foundation request to support some needs under “Big Data” umbrella. Potential shortterm win.
Past success of OHT is an asset. CONNECT is an asset. The fact that “we aren’t the ones who
have all the answers”, rather that we have a community under which problems can be solved.
Goal of the Board to help identify synergistic opportunities.
Once a platform is there, how do you foster/enable crowdsourcing in a marketplace around that
platform. Establish shared software infrastructure
OHT voice as part of policy decisions ; (for example, advocating policies that encourage and
incent the acquisition and consumption of OSS technologies)
Not to be too top-down on measures of success
Align ourselves with like communities (Eclipse, for instance)
o Build on HealtheWay collaboration ; find something sustainable
Resources are the CONNECT platform, existing projects, and human assets within the
community. Want active open source projects ; paying, active, engaged members

o