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.

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

FHIR Server needs capability statements #200

Open
lmcnabb opened this issue May 21, 2023 · 0 comments
Open

FHIR Server needs capability statements #200

lmcnabb opened this issue May 21, 2023 · 0 comments
Labels

Comments

@lmcnabb
Copy link
Collaborator

lmcnabb commented May 21, 2023

Identified need from May 2023 Connectathon & WGM:

We need to define our scope for our capability statement.  What I heard was: Every FHIR server needs a capability statement, really two.  1. API capability statement and 2. terminology capability statement.  For every operation you define - you need to describe.  From my notes if they make sense, you can do a few diff things:  It's being scoped out code that a server can use to declare capability statements, or client code declare what it wants to use, they are moving to a kind of coded grammar.  For people who want feature negotiation.  Could be part of modern app registration paradigm (e.g., terminology registration?)

@lmcnabb lmcnabb added the Epic label May 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant