Details
-
Change Request
-
Resolution: Persuasive
-
High
-
FHIR Core (FHIR)
-
R5
-
Patient Administration
-
EndPoint
-
-
Reinhard Egelkraut / Brian Postlethwaite : 7-0-0
-
Correction
-
Compatible, substantive
-
R5
Description
Endpoint.payloadType should either be optional, or should have a better value set associated with it. The example value set provided does not seem to even have a way to specify that this endpoint is a FHIR server.
And the whole payloadType concept seems weird for a RESTful endpoint. The payload is whatever you query for or whatever a user chooses to POST (think of the Binary endpoint for example). Requiring this to be pre-defined up front might have made sense for XDS, but not for a FHIR endpoint. Personally, I think this should just be optional.
Attachments
Issue Links
- relates to
-
FHIR-19427 Endpoint payloadType code needed for DICOM payloads
- Published
-
FHIR-28467 Endpoint payload types should reference proper FormatCodes
- Published
-
FHIR-39617 Please clarify how connectionType, payloadType, and payloadMimeType interact for various Endpoint types
- Triaged
-
FHIR-36074 Endpoint.payloadType should be 0..*
- Duplicate
- mentioned in
-
Page Loading...