Recipe 5 — Your own sections & templates + end-user runtime overrides

Pair your project-owned templates with per-call runtime overrides so end users get last-mile control without you maintaining a section variant per user.

Beta

← Back to Customization Cookbook

Scenario: Same as Recipe 4, but your product UI lets clinicians tweak individual sections per encounter.

What you do:

Run Path 2 against your own template (instead of a Standard). The overrides shape is the same as Recipe 3 — templateRef.overrides.instructions for template-level tweaks, templateRef.overrides.sections[] for per-section tweaks.

POST /documents — Path 2 against your own template

{
  "outputLanguage": "en-US",
  "interactionId": "<your-interaction-id>",
  "templateRef": {
    "templateId": "<your-template-id>",
    "overrides": {
      "sections": [
        {
          "sectionId": "<your-section-id>",
          "generation": {
            "instructions": {
              "writingStylePrompt": "Lay-person friendly. No medical abbreviations. Address the patient in second person."
            }
          }
        }
      ]
    }
  }
}

Why this lever: You retain stable templates as the governed baseline; end users get last-mile control without you maintaining a section variant per user. The same presets-vs-free-prompt design choice from Recipe 3 applies.

Caveat: End-user overrides via free-prompt can drift in unpredictable ways. Always test edge cases (very long prompts, conflicting instructions, prompts that try to override schema). When in doubt, fall back to presets.

---

Previous: Recipe 4 — Author your own sections & templates · Next: Recipe 6 — Inherit from your own sections to scale