Oo Who Gho

WHO Global Health Observatory

Operate WHO Global Health Observatory through your OOMOL-connected account. This skill calls the who_gho connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

WHO Global Health Observatory needs no account connection. Assume the oo CLI is installed and signed in. Do not run oo auth login proactively — just run the action. Fall back to First-time setup only when a command actually fails.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "who_gho" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "who_gho" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• get_indicator_data — Retrieve WHO GHO observations for an indicator with structured dimension and year filters.
• list_dimension_values — List the available values for one WHO GHO dimension.
• list_dimensions — List dimensions available in the WHO Global Health Observatory OData API.
• search_indicators — Search WHO GHO indicators by partial or exact indicator name.

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change WHO Global Health Observatory state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• WHO Global Health Observatory homepage: https://www.who.int/data/gho