CapabilityStatement ticket implementations - #4129
Open
bvdh wants to merge 10 commits into
Open
Conversation
- Remove the Messaging CapabilityStatement rules subsection from capabilitystatement-notes.xml - Eliminate outdated draft-status wording for MessageDefinition and supportedMessage/event transition - Keep adjacent RESTful and Document CapabilityStatement notes intact
- Add read-conditional-modified-since and read-conditional-not-match interaction codes - Mark conditionalCreate, conditionalRead, conditionalUpdate, conditionalPatch, and conditionalDelete as deprecated with migration guidance - Deprecate conditional read/delete status code systems and value sets in favor of interaction codes
- Update CapabilityStatement.kind definition to describe general implementation expectations - Add explicit comment to use requirements when specific system knowledge is unavailable - Keep CapabilityStatementKind value set and code system concepts unchanged
- Add explicit version-independent binding guidance to CapabilityStatement.fhirVersion - Add binding-definition extension text for FHIR-version binding semantics - Add tooling narrative to versioning.html for prior-release version-independent behavior
- Add `other` concept to `restful-interaction` code system with ticket-defined meaning - Include `other` in `ValueSet/type-restful-interaction` compose and narrative table - Update CapabilityStatement.rest.resource.interaction.code short list to include `other`
- Add comment on CapabilityStatement.searchParam.type for down-conversion behavior - Specify that additional future search parameter types map to `special` - Keep SearchParamType terminology and required binding canonical unchanged
- Add other to ValueSet/system-restful-interaction compose include list - Add matching other narrative row in system interaction value set table - Update CapabilityStatement.rest.interaction.code short list to include other
- Replace incorrect resource-specific phrase in rest.searchParam comment - Keep remaining system-level comment guidance unchanged - Leave rest.resource.searchParam comment text unchanged
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.
Scope
Commits on fhir-fork branch CapabilityStatement addressing the tickets listed in the current batch scope.
Per-Ticket Change Summary
otherconcept torestful-interactioncode system with ticket-defined meaning.Notes on Overlaps