Skip to content
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

Make the Name in Capability statement an app setting #2241

Closed
CaitlinV39 opened this issue Sep 23, 2021 · 1 comment
Closed

Make the Name in Capability statement an app setting #2241

CaitlinV39 opened this issue Sep 23, 2021 · 1 comment
Labels
Tech-Debt VSTS-Current We are working on this item in the current sprint
Milestone
S74

Comments

@CaitlinV39
Copy link
Contributor

User story
As a developer, I want to be able to set the "Name" in the capability statement based on the setting. Specially, if the FHIR server is deployed as the Azure API for FHIR, the Name should be Azure API for FHIR and if the FHIR server is deployed to the Azure Healthcare APIs it should say the Azure Healthcare APIs.

Acceptance criteria
The name in the capability statement can be configured based on the context of deployment
@CaitlinV39 CaitlinV39 added the VSTS-Pending Prioritization We would like to add this to the backlog label Sep 24, 2021
@brendankowitz brendankowitz mentioned this issue Oct 21, 2021
Merged
5 tasks
@CaitlinV39
Copy link
Contributor Author

CaitlinV39 commented Oct 22, 2021 •
edited by azure-boards bot
Loading

AB#86146

@CaitlinV39 CaitlinV39 added VSTS-Current We are working on this item in the current sprint and removed VSTS-Pending Prioritization We would like to add this to the backlog labels Oct 22, 2021
@CaitlinV39 CaitlinV39 added this to the S74 milestone Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Tech-Debt VSTS-Current We are working on this item in the current sprint
Projects
None yet
Milestone
S74
Development

No branches or pull requests
2 participants
@brendankowitz @CaitlinV39