Skip to content

Business Intelligence

FieldOps provides secure access to operational data through its Business Intelligence (BI) API.

The BI API enables organizations to connect their FieldOps data to analytics and reporting tools such as:

  • Microsoft Power BI
  • Microsoft Excel Power Query
  • Tableau
  • Other BI platforms that support REST API connections

This allows monitoring teams, programme managers, and decision-makers to build custom dashboards, analyse performance, and generate reports using their preferred analytics tools.

FieldOps also provides an AI Assistant for natural-language analysis of available operational data. BI and the AI Assistant serve different purposes: BI provides structured datasets for reporting and visualization, while the AI Assistant helps users explore and understand operational information conversationally.


How It Works

FieldOps exposes structured datasets through secure API endpoints.

Analytics Tool
      |
      | HTTPS Request
      | Authorization: Bearer Token
      |
      ↓
FieldOps BI API
      |
      ↓
Operational Data

BI tools do not connect directly to the FieldOps database. Instead, they consume controlled datasets through the FieldOps API layer.

This provides:

  • Secure access to organizational data
  • Controlled data exposure
  • Better performance and scalability
  • Compatibility with multiple analytics platforms

Supported Connections

FieldOps BI data can be accessed using:

Tool Connection Method
Microsoft Power BI Web connector with Bearer token authentication
Microsoft Excel Power Query Web connector with Bearer token authentication
Tableau REST API connection

Authentication

Access to BI data is controlled through BI API Tokens.

Each token is:

  • Linked to an organization
  • Securely authenticated
  • Permission controlled
  • Revocable
  • Traceable

When connecting an analytics tool, the token is supplied through the HTTP Authorization header:

Authorization: Bearer YOUR_BI_TOKEN

For more information, see:

BI Access Tokens


Available Data

FieldOps exposes curated BI datasets designed for reporting and analytics.

Examples include:

  • Visits
  • Projects
  • Programmes
  • Sites
  • Monitoring responses
  • Indicators and performance measures

Available datasets are documented here:

Available Datasets


BI and the AI Assistant

BI and the AI Assistant provide two different ways to work with FieldOps operational data.

Business Intelligence

BI is designed for structured reporting and visualization.

Use the BI API when you want to:

  • Build dashboards
  • Create recurring reports
  • Analyse large datasets
  • Combine FieldOps data with other reporting sources
  • Use tools such as Power BI, Excel, or Tableau

AI Assistant

The AI Assistant is designed for conversational exploration and operational analysis.

Use the AI Assistant when you want to:

  • Ask questions about projects, sites, visits, findings, and corrective actions
  • Investigate operational issues
  • Understand performance
  • Explore relationships across FieldOps data
  • Ask follow-up questions in natural language

For example:

Why has Kapsabet Sub-County Hospital been underperforming for the last three months?

The AI Assistant can retrieve relevant FieldOps information and help explain the underlying operational situation.

The AI Assistant does not replace the BI API. BI provides structured data for analytics platforms, while the AI Assistant provides a conversational way to explore available operational information.


Getting Started

To connect an analytics tool:

  1. Generate a BI API token.
  2. Select your preferred analytics platform.
  3. Connect to the FieldOps BI endpoint.
  4. Authenticate using your BI token.
  5. Load and analyse your data.

Connection guides:


Security Considerations

BI access is designed to provide reporting flexibility while maintaining control over organizational data.

FieldOps recommends:

  • Creating separate BI tokens for different reporting purposes.
  • Assigning only the required permissions.
  • Rotating tokens periodically.
  • Revoking unused tokens.

Never share BI tokens publicly or embed them directly in public reports.