FQM-280: Verify coverage information system actions only add/update the coverage-information extension#83
Merged
Conversation
cd6da72 to
cd025ba
Compare
cd025ba to
2f2543e
Compare
Jammjammjamm
approved these changes
May 20, 2026
arscan
approved these changes
May 20, 2026
Contributor
|
FYI @karlnaden, thanks! |
karlnaden
approved these changes
May 20, 2026
Draft
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
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.
Summary
This updates the CRD 2.2.1 server Coverage Information system action validation test to verify
resp-37: when a server returns a Coverage Information update, the returned resource may only add or modify the coverage-information extension and must not change any other resource content. I was on the fence about putting it in this test or adding a new test. Happy to switch it to its own test if reviewers prefer.To get a source resource to compare against, we pull from the hook request context, prefetch, or mock_ehr_bundle as needed across hook types. If we can't find one, we emit a warning.
Testing Guidance
encounter-start, which doesn't return a coverage information systemAction.Anticipated Provider-side Test Impact
None