Document the PlanDefinition route required for form packages - #5
Open
alex-serednev wants to merge 1 commit into
Open
alex-serednev wants to merge 1 commit into
alex-serednev wants to merge 1 commit into
Conversation
The Forms page reads form packages alongside questionnaires, so the SMART access policy needs to allow the PlanDefinition route. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
alex-serednev
force-pushed
the
docs/smart-plandefinition-access
branch
from
September 19, 2026 06:34
ca3e30a to
000bf4a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the
PlanDefinitionroute to the SMART access policy on the EHR integration via SMART on FHIR page, plus a new Form packages access section covering why the route is needed.Why
Form packages are stored as
PlanDefinitionresources, and the Forms page reads them alongside questionnaires. A SMART access policy that does not include that route leaves the forms list unable to display correctly, so the route belongs in the documented policy.The policy generated by the SMART setup in the Formbox UI does not include it either, so the new section explains how to add it there, and notes that covering it in the generated policy can be done by request.
Changes
docs/aidbox-ui-builder-alpha/smart-app-integration.md### 4. Access policy— added thePlanDefinitionpattern to the$one-oflist### Form packages accesssection, placed after the setup steps and before### Sandbox noteValidation
bun lint— 12 checks passed, 5 warnings, all pre-existing and in other files. Output is identical before and after this change.🤖 Generated with Claude Code