Skip to main content

Integration Options: UI, SDK, and API


This guide assists integration developers in connecting the Air Doctor Doctor App to their platforms via UI components, SDK methods, and APIs.

Integrating Air Doctor into Hospital Systems

Integration Options

Combine approaches, for example, use UI Screens for frontend speed and APIs for backend logic.

UI Screens

  • Provide prebuilt login, booking, and session flows.
  • Enable rapid UI integration with minimal development.
  • Ideal for organizations prioritizing speed over customization.

Integration Flow with UI Screens

UI Screens (prebuilt flows)

Server APIs (for persistence, logs)

Responsibilities (UI)

ActionUI Screens
Log inProvided screen
View appointmentsProvided screen
Book appointmentProvided screen
Upload documentsProvided screen
Logging outcomeNot handled by UI Screens
Flow customizationNot supported

Integration Patterns

Use these patterns to streamline your workflow:

PatternSequenceBest Use
Quick Launch + LoggingUI → APIFast deployment with backend logging.
Embedded FlowSDK → APIBuild consistent UI flows that link to your backend.
Full CustomAPI OnlyDevelop everything — UI and backend logic — in-house.

Use Case Example: Insurance Portal

Integration layers: Use UI Screens for ready-made booking flows, the SDK for embedded session logic, and the API for backend data exchange with hospitals and EHR systems.

Integration sequence:

UI Screens - Supply login and booking workflows. SDK - Drives behavior within partner’s app. API - Connects partner backend to Air Doctor for processing bookings, documents, and logs.


Next Steps