Skip to content

Adding the 'instantiates' to the capability statement.#5469

Open
v-isyamauchi-gh wants to merge 2 commits intomainfrom
personal/v-isyamauchi/add-instantiates-field
Open

Adding the 'instantiates' to the capability statement.#5469
v-isyamauchi-gh wants to merge 2 commits intomainfrom
personal/v-isyamauchi/add-instantiates-field

Conversation

@v-isyamauchi-gh
Copy link
Copy Markdown
Contributor

Description

Adding the 'instantiates' to the capability statement.

Related issues

Addresses [issue #95785].

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

Testing

Tested by adding UTs and manual testing.

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 Mar 27, 2026
@v-isyamauchi-gh v-isyamauchi-gh requested a review from a team as a code owner March 27, 2026 22:19
@v-isyamauchi-gh v-isyamauchi-gh added No-Issue-Activity This issue is now considered stale and will be closed soon 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. No-PaaS-breaking-change No-ADR ADR not needed New Feature Label for a new feature in FHIR OSS labels Mar 27, 2026
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Mar 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.93%. Comparing base (ea948f8) to head (98bc250).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5469      +/-   ##
==========================================
+ Coverage   76.91%   76.93%   +0.01%     
==========================================
  Files         978      980       +2     
  Lines       35680    35760      +80     
  Branches     5356     5366      +10     
==========================================
+ Hits        27443    27511      +68     
- Misses       6903     6917      +14     
+ Partials     1334     1332       -2     

see 13 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@v-isyamauchi-gh
Copy link
Copy Markdown
Contributor Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

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

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 No-ADR ADR not needed No-Issue-Activity This issue is now considered stale and will be closed soon No-PaaS-breaking-change Open source This change is only relevant to the OSS code or release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants