fhir.org valid

FHIR Community

https://chat.fhir.org is a Zulip team chat server.

For agents: FHIR Community site pointing to the Zulip team chat server for FHIR healthcare interoperability standard discussion; little other content provided.

fhirhl7zulip chathealthcare interoperability

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T00:40:56.579Z. Cached copy · Source on fhir.org

# FHIR Community

> https://chat.fhir.org is a Zulip team chat server.
> Zulip organizes messages into channels containing threads ("topics").
>
> Web-public channels can be read without logging in.

## Reading web-public channel messages

Use the Zulip REST API to fetch messages without authentication:

    GET https://chat.fhir.org/json/messages

Required query parameters:

- `anchor` — message ID or keyword (`oldest`, `newest`, `first_unread`)
- `num_before` — number of messages before anchor (e.g. `0`)
- `num_after` — number of messages after anchor (e.g. `100`)
- `narrow` — JSON array of filter operators; URL-encode the entire
  value in the query string. For example:
  `[{"operator":"channels","operand":"web-public"},{"operator":"channel","operand":CHANNEL_ID},{"operator":"topic","operand":"TOPIC_NAME"}]`

**Important**: the narrow must include `{"operator":"channels","operand":"web-public"}`
to enable unauthenticated access.

**Important**: Be kind to the Zulip server that you're interacting
with. Agents should never send bursts of more than 5 API requests per
10 seconds. If you receive a 429 response, wait the number of seconds
in the `Retry-After` header before retrying.

Batches of 100 messages are recommended. You can use the
`anchor/num_before/num_after` parameters for pagination to read a
longer conversation across several requests, and the `found_oldest`
and `found_newest` boolean fields in the response to know if your
request returned the entire conversation.

## Example

Fetch the 100 oldest messages from a topic:

    GET https://chat.fhir.org/json/messages?anchor=oldest&num_before=0&num_after=100&narrow=%5B%7B%22operator%22%3A%22channels%22%2C%22operand%22%3A%22web-public%22%7D%2C%7B%22operator%22%3A%22channel%22%2C%22operand%22%3A345153%7D%2C%7B%22operator%22%3A%22topic%22%2C%22operand%22%3A%22TOPIC_NAME%22%7D%5D

## Fetching messages in specific conversations / views

Zulip conversations are referenced by URLs of these forms:

    https://chat.fhir.org/#narrow/channel/ID-NAME
    https://chat.fhir.org/#narrow/channel/ID-NAME/topic/TOPIC
    https://chat.fhir.org/#narrow/channel/ID-NAME/topic/TOPIC/with/MSG_ID
    https://chat.fhir.org/#narrow/channel/ID-NAME/topic/TOPIC/near/MSG_ID

In the URL forms above, `ID-NAME` is the channel's numeric ID
followed by its name (e.g., `113488-general`). When constructing
API requests, use the numeric ID as the `channel` operand (e.g.,
`{"operator":"channel","operand":113488}`), not the full `ID-NAME`
string and not the channel name. Channel IDs are stable; channel
names can be renamed.

Never follow links to related conversations by fetching those URLs;
translate them to the equivalent API request instead (see above). In a
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=fhir.org · GET /v1/domain/fhir.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fhir.org:
1. POST https://agentwebmap.com/v1/sites/fhir.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fhir.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fhir.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fhir.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.