Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-22629

Endpoint.contentType shouldn't be mandatory

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • EndPoint
    • Hide

      The cardinality for the payload type will be relaxed to make it optional.

      Where jurisdictions or projects deem that it should be mandatory they can profile it for their usage.

      Show
      The cardinality for the payload type will be relaxed to make it optional. Where jurisdictions or projects deem that it should be mandatory they can profile it for their usage.
    • Thomas T Rosenlund/Kathy Pickering:10-0-1
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      For FHIR REST and messaging endpoints, there's no appropriate code to identify the type(s) of content that can be posted to the endpoint. Furthermore, there's a standardized mechanism for determining what the endpoint is capable of that is dynamic and more accurate than anything that an endpoint registry could expose. Therefore, making the Endpoint.payloadType 1..* is inappropriate. It should be 0..*. Da Vinci CDEX expects to identify the endpoint to be a CommunicationRequest.recipient and there's no need for (nor appropriate value for) identifying the payloadType.

      Attachments

        Activity

          People

            Egelkraut Reinhard Egelkraut
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: