Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R5
Work Group:

FHIR Infrastructure
Related Page(s):

Exchanging Resources
Grouping:
- Deferred
Resolution Description:

Hide

Will try to do this. Will need some research to figure out how to populate some of the columns. (E.g. does GraphQL or SPARQL require http/https?) May be able to consolidate the number of columns a bit. This might or might not make it into R5. If not, it'll be done for R6.

Show
Will try to do this. Will need some research to figure out how to populate some of the columns. (E.g. does GraphQL or SPARQL require http/https?) May be able to consolidate the number of columns a bit. This might or might not make it into R5. If not, it'll be done for R6.
Resolution Vote:
Gino Canessa/Rik Smithies: 27-0-6
Change Category:
Clarification
Change Impact:
Non-substantive

In the table in the section Overview of approaches, it would be nice to add some additional context to help with decision making.

Specifically, I think it would be useful to note if:

Client or server is expected to be a FHIR implementation (e.g., destination of a RESTful create)
Protocols allowed / used (e.g., http, https, etc.).
MIME types used (e.g., FHIR MIMEs for REST, JSON for CDS Hooks, GraphQL, etc.).