API
direct

TYPE
MOBILE & WEB APP
YEAR
2022
ROLE
UX LEAD
HOME
>
APIDIRECT
APIdirect is the world's first healthcare API library - making it easy to discover, review, and deploy APIs for clinical automation. It bridges REST and No-Code platforms, turning complex endpoints into plug-and-play connectors for faster, standards-aligned integration.

INTERCONNECTED HEALTHCARE

WHY THIS PROJECT

PIONEERING THE OPPORTUNITY

API CARDS

FILTER API'S

EXPANDED API'S

API UPLOADS

INTER-CONNECTED HEALTHCARE

SEAMLESS API ACCESS FOR A SMARTER, FASTER HEALTHCARE ECOSYSTEM

APIdirect Interconnected Healthcare Interface
MARKET
Pioneer
In the industry
STRATEGY
400+
APIs Indexed
EFFICIENCY
35%
Faster Integration Time
TRUST & COMPLIANCE
FHIR
100% Compliant

Why This Project?

First

Defining the First UX: Crafted an end-to-end experience enabling clinical teams to explore the world's first healthcare API library

Scalable

Scalable Taxonomy: Designed metadata and filter systems that grew with the platform, enabling precise discovery across clinical contexts

Alignment

Alignment With Standardisation: Ensured technical trust and regulatory alignment through structured tagging and architecture

Time

Reducing Integration Time: Streamlined navigation, filters, and schema visibility to support faster implementation

Growth

Enabling Platform Growth: Designed a modular upload system that allowed community-driven API expansion without manual outreach

Trust

Dual Layer Trust: Expert and community feedback systems for clinical confidence and continuous API improvement

Pioneering The Opportunity

In modern healthcare, integration is everything - but technical fragmentation persists. As more hospitals embrace automation, there was no central hub for discovering, comparing, or onboarding healthcare APIs. This left developers, clinicians, and IT teams struggling to build integrations that could have accelerated patient care.

Alphalake ai envisioned APIdirect as the first global library of healthcare APIs, designed to bridge traditional REST interfaces and modern No-Code automation tools through intuitive UX and FHIR standardisation.

Pioneering The Opportunity

Understanding Needs

To deliver impact from day one, we prioritised features that solved real integration pain points while laying a foundation for scalable growth. Using a MoSCoW framework, we aligned on:

  • Must-haves - Searchable documentation, versioning, and upload to create a functional, scalable API library.
  • Should-haves - Reviews and secure access to build trust and adoption.
  • Won't-haves - Lower-impact tools & features (e.g. SDKs, bookmarking) deferred for future phases.

Product Research

With no direct competitors, we studied adjacent platforms to uncover shared UX patterns, gaps, and opportunities. Key takeaways included:

  • Industry leaders emphasised documentation depth and sandbox testing
  • Few platforms supported FHIR-specific workflows or no-code integration
  • Existing tools leaned heavily developer-first, leaving clinical and non-technical users underserved

My Role & Approach

Research

Led Research Sessions

With Clinicians & Health IT to shape foundational UX

Systems

Created Design Systems

For API Cards, Submission flows & Resource Groups

Strategic

Strategic Alignment

Balanced MVP constraints with long-term expansion

Architecture

Designed Architecture

Central to the function of the API Library

Clarity

Advocated for Clarity

And progressive disclosure across metadata-heavy content

DESIGNING THE EXPERIENCE

BRINGING STRUCTURE, CLARITY, AND SCALE TO HEALTHCARE INTEGRATION

API Cards & Metadata Design

Each card was engineered to maximize scannability.

Critical decisions included:

  • Tags for API Type and Category: Users could instantly see whether an API supported NoCode, FHIR, or required custom integration
  • Expandable Resource Groups: Rather than front-loading complexity, we used collapsible menus following FHIR structure
  • Visual Badges: Highlighted trust factors like compliance and verification
API Cards Design

Search & Filtering Framework

Knowing the library would scale rapidly, we built the filter taxonomy early:

  • 6 Core Categories: API Type, Status, User Type, Location, Care Setting, and System
  • Nested Tags: For instance, "User Type" splits into Clinicians, Patients, and Admins.
  • Futureproofing: The design supports tagging expansion without reworking the core IA.
Search & Filtering Framework

Expanded API View

Larger APIs (e.g., Cerner, Epic) couldn't be explained in a small card.

The full-view UI included:

  • Persistent metadata at top
  • Full breakdown of all resource groups and endpoints
  • Review system with two layers:
    • Expert Reviews: Vetted, domain-specific insights
    • Community Feedback: Moderated for relevance
Expanded API View

API Upload Flow

The biggest challenge: allowing any healthcare developer to submit new APIs without friction - while capturing enough schema detail to avoid backend bottlenecks

Design choices:

  • FHIR-first form, but with flexibility for non-standard APIs
  • Dynamic input fields for operations, resource groups, and use cases
  • Smart defaults to reduce dropout risk

Stakeholders later aligned on expanding this into a community-led forum ecosystem

API Upload Flow

Measuring Success & Business Impact

Measuring Success & Business Impact

Iterative Testing & Learnings

We refined flows through continuous feedback from clinical and developer stakeholders.

Key takeaways:

  • Defined MVP boundaries early to manage shifting scope
  • Prioritised modular design to support future scale
  • Simplified content through layered disclosure and clarity-first patterns

Outcome & Strategic Value

APIdirect launched as the first global healthcare API library, with a UX foundation built for trust, scale, and adoption.

  • 400+ APIs structured at launch
  • Enabled self-serve growth through flexible architecture
  • Positioned Alphalake as a leader in API accessibility for healthcare

Reflection

This project strengthened my ability to design at the intersection of product strategy and complex healthcare systems, balancing FHIR standards with usability, and building scalable structures that support long-term growth

From accelerating developer integration to enabling 400+ APIs at launch, APIdirect pushed me to think beyond features and into ecosystem-wide outcomes

It remains one of the clearest example of design driving clarity, adoption, and strategic value at scale I've led until today.

MORE CASE STUDIES

HUBBOX・LOGISTICS・WEB APP

HUBBOX

WONDR・DESIGN SYSTEM

W_ DESIGN SYSTEM

STRONGFIT・FITNESS・MOBILE APP

STRONGFIT