Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

Support for capability statement #416

Closed
psiotwo opened this issue Nov 2, 2019 · 3 comments
Closed

Support for capability statement #416

psiotwo opened this issue Nov 2, 2019 · 3 comments
Assignees
@cmark
Labels
feature pinned

Comments

@psiotwo
Copy link

psiotwo commented Nov 2, 2019

Would be great to expose capability statement on /metadata endpoint (TerminologyCapabilities), as specified in http://hl7.org/fhir/http.html.
@cmark
Copy link
Member

cmark commented Nov 4, 2019

Hi @psiotwo,

Indeed, that would be really great addition to the FHIR API, definitely on our radar.

Cheers,
Mark

@cmark cmark added the feature label Nov 4, 2019
@stale
Copy link

stale bot commented Jan 3, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 3, 2020
@apeteri apeteri removed the wontfix label Jan 3, 2020
@cmark cmark added the pinned label Jan 21, 2020
@cmark
Copy link
Member

cmark commented Oct 29, 2021

Hi @psiotwo,

It's been a while. I just want to let you know that the /metadata endpoint is now available in the latest 8.0.0 release.

Cheers,
Mark

@cmark cmark closed this as completed Oct 29, 2021
@cmark cmark self-assigned this Oct 29, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@cmark cmark

Labels
feature pinned
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@psiotwo @cmark @apeteri