$everything

The FHIR $everything operation retrieves a comprehensive bundle of all data associated with a person in a single request. This operation returns the patient's full patient record, including demographics, conditions, medications, observations, procedures, and all related clinical and non-clinical resources.

$everything FHIR Endpoints

Sandbox: https://fhir.client-sandbox.icanbwell.com/4_0_0/Person/{person_id}/$everything
Production: https://fhir.icanbwell.com/4_0_0/Person/{person_id}/$everything

Replace {person_id} with the unique identifier in the b.well user profile.

Authentication

All requests to the b.well FHIR Server require authentication. See System Authentication for details on obtaining an access token.

Include your access token in the Authorization header of all requests:

Example Request:

GET https://fhir.client-sandbox.icanbwell.com/4_0_0/Person/12345/$everything?_since=2025-11-01T00:00:00Z
Authorization: Bearer {your_access_token}
Accept: application/fhir+json

Response:

The standard response will be a FHIR Bundle containing all the associated data for the individual, including:

Clinical Resources - Observation, Condition, Procedure, MedicationStatement, AllergyIntolerance, etc.
Non-Clinical Resources - Practitioner, Location, Organization, and supporting data
Encounter Information - Healthcare visits and events
Patient Demographics - Patient demographic information
Referenced Resources - Related resources based on query parameters

Optional Query Parameters:

Parameter	Type	Description	Default
`_includePatientLinkedOnly`	Boolean	Includes only linked clinical resources; excludes non-clinical resources	`false`
`_type`	String	Filter for specific resource types (comma-separated)	All types
`_since`	DateTime	Fetch resources updated after this date-time	None

Note: The _type & _since parameters are recommended when testing in interactive API playgrounds to manage response payload size and prevent browser performance issues.

Optional Custom Headers: For large datasets, the endpoint supports streaming responses using NDJSON format. To enable streaming, set the Accept header to application/fhir+ndjson.

Each line in the response will contain a single FHIR resource as a JSON object. Lines are separated by newline character (\n)
Resources are streamed as they are retrieved from the database, therefore the response is not wrapped in a FHIR bundle

For more details on the FHIR $everything operation, refer to the FHIR Specification.