Skip to content

Add meta history to PATCH #5290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
LTA-Thinking merged 7 commits into from
Dec 31, 2025
Merged

Add meta history to PATCH #5290

LTA-Thinking merged 7 commits into from
Dec 31, 2025

Conversation

@LTA-Thinking
Copy link
Contributor

@LTA-Thinking LTA-Thinking commented Dec 23, 2025 •
edited
Loading

Description

Adds support for the _meta-history parameter to PATCH requests.

Related issues

Addresses User Story 167336

Testing

New and existing E2E tests

FHIR Team Checklist

  • Update the title of the PR to be succinct and less than 65 characters
  • Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
  • Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
  • Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
  • Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
  • When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
  • CI is green before merge Build Status
  • Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)

@LTA-Thinking LTA-Thinking added this to the FY26\Q2\2Wk\2Wk13 milestone Dec 23, 2025
@LTA-Thinking LTA-Thinking requested a review from a team as a code owner December 23, 2025 22:02
@LTA-Thinking LTA-Thinking added Enhancement Enhancement on existing functionality. Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs labels Dec 23, 2025
@LTA-Thinking
Copy link
Contributor Author

LTA-Thinking commented Dec 30, 2025

/azp run

@azure-pipelines
Copy link

azure-pipelines bot commented Dec 30, 2025

Azure Pipelines successfully started running 1 pipeline(s).

mikaelweave
mikaelweave approved these changes Dec 31, 2025
View reviewed changes
Copy link
Contributor

@mikaelweave mikaelweave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@LTA-Thinking LTA-Thinking merged commit ba9f7d1 into main Dec 31, 2025
61 of 65 checks passed
@LTA-Thinking LTA-Thinking deleted the personal/rojo/patch-metadata branch December 31, 2025 17:53
@jestradaMS jestradaMS added PaaS-breaking-change Add this label if your changes will require additional changes in PaaS repos to be complete and removed PaaS-breaking-change Add this label if your changes will require additional changes in PaaS repos to be complete labels Jan 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mikaelweave mikaelweave mikaelweave approved these changes

Assignees

No one assigned

Labels

Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Enhancement Enhancement on existing functionality. No-PaaS-breaking-change

Projects

None yet

Milestone

FY26\Q2\2Wk\2Wk13

Development

Successfully merging this pull request may close these issues.

4 participants

@LTA-Thinking @mikaelweave @jestradaMS