athenahealth's More Disruption Please Program Custom Case Solution & Analysis

1. Evidence Brief (Case Researcher)

Financial Metrics

athenahealth 2015 revenue: $925M (Exhibit 1).
MDP program goal: Open API platform to integrate third-party applications (Paragraph 4).
Market context: EHR market dominated by Epic and Cerner (Paragraph 2).

Operational Facts

Core product: athenaNet, a cloud-based EHR/practice management system (Paragraph 3).
MDP structure: Marketplace for apps that plug into athenaNet; athenahealth takes a percentage of revenue generated by partner apps (Paragraph 8).
Developer access: athenahealth provided an API for developers to build on top of their network (Paragraph 9).

Stakeholder Positions

Jonathan Bush (CEO): Visionary proponent of open platforms; views EHRs as needing to move from closed systems to connected networks (Paragraph 5).
Hospital/Provider clients: Need integrated tools to manage complexity, but sensitive to data security and clinical workflow disruption (Paragraph 12).
Third-party developers: Want access to athenahealth’s massive physician user base but frustrated by integration hurdles (Paragraph 10).

Information Gaps

Specific revenue split percentages between athenahealth and MDP partners.
Quantified churn rates specifically attributed to MDP-related integration issues.
Direct overhead costs of maintaining the developer portal vs. revenue generated.

2. Strategic Analysis (Strategic Analyst)

Core Strategic Question

Can athenahealth scale the MDP marketplace into a significant revenue stream without compromising the stability and security of its core EHR service?

Structural Analysis

Value Chain: The platform model shifts athenahealth from a software vendor to a network orchestrator. The bottleneck is the high cost of vetting and integrating third-party code.
Network Effects: The strategy relies on two-sided network effects. More apps attract more providers, and more providers attract more developers.

Strategic Options

Option 1: Aggressive Openness. Remove all barriers to entry for developers. Trade-off: Rapid growth in app count vs. high risk of security breaches and clinical workflow failures.
Option 2: Curated Marketplace. Strict vetting, certification, and exclusive partnerships. Trade-off: Slower growth vs. higher quality, safer environment for providers.
Option 3: Platform-as-a-Service (PaaS) Focus. Charge developers for platform access rather than revenue sharing. Trade-off: Predictable income vs. reduced alignment with developer success.

Preliminary Recommendation

Pursue Option 2. The clinical nature of the product makes quality control a non-negotiable. Trust is the company’s primary asset; a single security incident would negate all platform gains.

3. Implementation Roadmap (Implementation Specialist)

Critical Path

Step 1: Formalize a tiered certification program for developers.
Step 2: Establish a dedicated clinical safety review board to audit third-party code.
Step 3: Build automated sandbox environments for developer testing.

Key Constraints

Workflow Friction: If third-party apps disrupt physician charting, providers will abandon athenaNet.
Data Security: HIPAA compliance remains the primary regulatory barrier to entry.

Risk-Adjusted Implementation

Pilot the certification program with five high-demand app partners before scaling. Implement a two-year phase-in for legacy developers to meet new security standards. If a partner app experiences a security failure, immediate suspension must be automated to protect the network reputation.

4. Executive Review and BLUF (Executive Critic)

BLUF

athenahealth must transition from a permissive open-access model to a high-trust, curated marketplace. The current strategy assumes that developers will prioritize security and clinical efficacy as much as athenahealth does; this is a false premise. The company is risking its core EHR franchise to capture ancillary revenue. By implementing a strict certification layer, athenahealth protects its primary revenue base while forcing partners to prove their clinical utility. Growth will slow in the short term, but the platform will survive the inevitable regulatory scrutiny. The current model is unsustainable because it lacks a mechanism to force accountability on third-party developers.

Dangerous Assumption

The assumption that third-party developers will self-regulate for security and clinical safety without rigorous, mandatory oversight.

Unaddressed Risks

Regulatory Liability: If a third-party app leads to a medical error, athenahealth will be held liable by providers and regulators.
Platform Fragmentation: Unchecked app growth creates a fragmented UI that destroys the productivity gains athenaNet promises.

Unconsidered Alternative

Transition to a 'walled garden' where athenahealth owns the integration logic entirely, charging a premium for technical support rather than relying on a revenue-share model that misaligns incentives.