prior-auth: document FHIR_VALIDATION_LENIENT - #27
Merged
Conversation
Rost-is-love
approved these changes
Aug 5, 2026
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
2 participants
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
Documents the
FHIR_VALIDATION_LENIENTdeployment flag on both prior-auth pillar pages, following the existing env-var convention (CDS_REQUIRED_HEADERS/CDS_ENABLED_HOOKSon the CRD page):422with the fullOperationOutcomeon any error-level finding); lenient mode logs display-name and referenced-resource profile mismatches as warnings, keeps structural/profile/missing-reference errors blocking, and filters422bodies down to blocking findings. Positioned for sandbox/onboarding use, with production advised to stay strict.Written for a reader with no history: what the flag does and when to use it, no background on how it came about.