Skip to content

Populating 'instantiates' field of CapabilityStatement. #5241

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
Open
v-isyamauchi-gh wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Populating 'instantiates' field of CapabilityStatement. #5241

v-isyamauchi-gh wants to merge 4 commits into from

Conversation

@v-isyamauchi-gh
Copy link
Contributor

@v-isyamauchi-gh v-isyamauchi-gh commented Nov 17, 2025

Description

The change will populate 'instantiates' field of CapabilityStatement when necessary.

Related issues

Addresses [issue #95785].

User Story 95785: Instantiate field and export endpoint is added under Capability statement

Testing

Tested manually and also by adding some UTs.

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)

@v-isyamauchi-gh v-isyamauchi-gh added this to the CY25Q3/2Wk07 milestone Nov 17, 2025
@v-isyamauchi-gh v-isyamauchi-gh requested a review from a team as a code owner November 17, 2025 23:24
@v-isyamauchi-gh v-isyamauchi-gh added New Feature Label for a new feature in FHIR OSS Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs Open source This change is only relevant to the OSS code or release. labels Nov 17, 2025
@v-isyamauchi-gh
Copy link
Contributor Author

v-isyamauchi-gh commented Nov 25, 2025

/azp run

@azure-pipelines
Copy link

azure-pipelines bot commented Nov 25, 2025

Azure Pipelines successfully started running 1 pipeline(s).

abiisnn
abiisnn previously approved these changes Nov 25, 2025
View reviewed changes
Copy link
Contributor

@abiisnn abiisnn left a comment

Choose a reason for hiding this comment

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

🍒

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@abiisnn abiisnn abiisnn left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

Azure API for FHIR Label denotes that the issue or PR is relevant to the Azure API for FHIR Azure Healthcare APIs Label denotes that the issue or PR is relevant to the FHIR service in the Azure Healthcare APIs New Feature Label for a new feature in FHIR OSS Open source This change is only relevant to the OSS code or release.

Projects

None yet

Milestone

CY25Q3/2Wk07

Development

Successfully merging this pull request may close these issues.

3 participants

@v-isyamauchi-gh @abiisnn