pilot-service-agents-health

# pilot-service-agents-health Public-health and biomedical APIs — ClinicalTrials.gov, openFDA, CDC, WHO, ClinVar, DailyMed, disease.sh. All agents in this category follow the standard contract described in `pilot-service-agents`. Send `/help` to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh `list-agents` query. ## Agents in this category (snapshot) | Hostname | Description | |---|---| | `cdc-covid-vax` | CDC COVID-19 vaccination data by jurisdiction | | `clinicaltrials-search` | ClinicalTrials.gov v2 studies search | | `clinvar-esearch` | Clinvar Esearch | | `dailymed-spl` | Dailymed Spl | | `disease-sh-countries` | COVID-19 per-country live statistics | | `disease-sh-covid` | disease.sh COVID-19 country statistics | | `mesh-lookup` | Mesh Lookup | | `ncbi-gene-esearch` | Ncbi Gene Esearch | | `ncbi-pubmed-esearch` | Ncbi Pubmed Esearch | | `noaa-tides` | NOAA Tides & Currents water level data | | `open-disease-covid` | COVID-19 and flu live global counts | | `openfda-adverse-events` | Openfda Adverse Events | | `openfda-device-event` | FDA medical device adverse event reports | | `openfda-drug` | openFDA drug label search - FDA-approved drug data | | `openfda-drug-events` | openFDA drug adverse event reports | | `openfda-food-recall` | FDA food product recall enforcement reports | | `openfda-ndc` | Openfda Ndc | | `openfdadevice-recall` | Openfdadevice Recall | | `pubmed-esearch-v2` | PubMed article metadata by PMID | | `rxnorm-drug` | RxNorm drug name/ingredient lookup (NIH/NLM) | | `rxnorm-drugs` | Rxnorm Drugs | | `wger-exercises` | Exercise/workout database with muscle groups | | `who-disease-outbreaks` | Who Disease Outbreaks | | `who-gho-data-life-expect` | Who Gho Data Life Expect | | `who-gho-data-mortality` | Who Gho Data Mortality | | `who-gho-indicator` | WHO Global Health Observatory indicators | | `who-gho-indicators-list` | Who Gho Indicators List | ## What you can expect - Regulatory and surveillance data — FDA drug labels, CDC indicators, disease.sh country COVID stats - ClinicalTrials.gov v2 study search with rich filters - WHO Global Health Observatory (mortality, life-expectancy, disease outbreaks) ## What NOT to expect - Personal health records — all data is anonymised/public - Diagnostic advice — outputs are raw structured records - Live provider directories (not in catalogue) ## Commands (same pattern for every agent in the category) ```bash # Read an agent's filter contract pilotctl --json send-message <hostname> --data "/help" --wait # Fetch structured data pilotctl --json send-message <hostname> --data '/data {json filters}' --wait # Natural-language summary (Gemini) pilotctl --json send-message <hostname> --data '/summary {json filters}' --wait ``` ## Response shape With `--wait`, `send-message` blocks until the agent replies (up to 30 s by default) and prints one JSON document: the ACK fields (`{"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}`) plus `reply`, the agent's message. The agent's normalised envelope is the JSON string in `data.reply.data` (pilotctl v1.12.2 and older print two JSON documents instead: the send result, then the reply, whose `data.data` is the envelope). A non-zero exit means no reply arrived (the error JSON on stderr has a `code` such as `timeout`) — treat that as *no data*, never as a cue to read older messages from the inbox. A reply that lands after the wait can still be picked up by sender and time: `pilotctl --json inbox --from <hostname> --since 5m --latest`. The envelope: ```json { "source": "<hostname>", "items": [...], "count": <int>, "total": <int|null>, "page": <int|null>, "next": <cursor|null>, "truncated": <bool>, "upstream_url": "<resolved upstream URL>" } ``` `/help` returns plain text. `/summary` returns a Gemini-generated prose string. Free-text queries also return Gemini prose. ## Workflow Example ```bash # 1. Fresh discovery — the catalogue grows, never hard-code pilotctl --json send-message list-agents --data '/data {"category":"health","limit":20}' --wait # 2. Read the contract of a specific agent pilotctl --json send-message clinicaltrials-search --data '/help' --wait # 3. Query it pilotctl --json send-message clinicaltrials-search --data '/data {"query":"sleep apnea","status":"RECRUITING"}' --wait ``` ## Dependencies Requires the `pilot-protocol` core skill, the `pilot-service-agents` skill (for the general discovery flow), `pilotctl` on PATH, and a running daemon registered with the backbone (Network 0 — joined automatically at registration).