← Back to Builder

Settings

The Settings page (More ▾ → Settings) configures the external servers and services the builder can talk to. Everything here is optional — the builder works offline without any of it; these settings only enable features that need a server (terminology expansion, $populate, external validation, translation).

Settings are saved in your browser, and synced to your account when you are signed in (see Cloud save). Each field has a Reset to return it to its default.

Servers & services

  • Terminology Server — a FHIR $expand endpoint used to resolve ValueSet bindings so choice options can be pulled from a value set.
  • FHIR Base Server — a FHIR server used for searching resources (e.g. finding a patient) and as the fallback for SDC operations.
  • SDC Server — a server that implements the SDC operations such as $populate; falls back to the FHIR Base Server when blank.
  • CORS Proxy — a proxy that forwards requests to FHIR servers that don't send CORS headers, which browsers otherwise block. Needed for browser-based calls to some external servers.
  • NLM Clinical Tables API — an endpoint for searching clinical terminology (LOINC, SNOMED, ICD); it is CORS-enabled so no proxy is required.
  • Translation API — the machine-translation provider used by Translate: Google gtx (free, no key), DeepL, LibreTranslate or OpenAI. Pick a provider, set its endpoint, and (for DeepL/OpenAI) an API key.

Signing in to protected FHIR servers

The FHIR Base Server and the SDC Server each have optional sign-in fields for servers that require a login: Authorize URL, Token URL, Client ID and Scope. When you fill them in, the builder signs you in through a pop-up window using the standard OAuth authorization-code flow with PKCE (a way to log in without the builder ever seeing your password), then sends the resulting access token with its requests to that server. If the session expires, a banner appears with a Log in button so you can sign in again. The tokens are kept in your browser's local storage on this device, so sign out of shared computers by clearing site data.

Validators

The Validators section manages the validation pipeline. A built-in validator always runs; you can add external validators that send the questionnaire to a FHIR server's $validate endpoint. See Validation.

Active configuration sources

Because a setting can come from a default, your browser, or your cloud account, the Active Configuration Sources section shows how each value is resolved — higher-priority sources override lower ones — so you can tell where a given value is coming from.

Next: Comparison with other tools.