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

endpoint.payloadFormat 0..*

    XMLWordPrintableJSON

Details

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

      Include new codes to the example valueset for the concepts:

      "any" the content of the data used on the endpoint is undefined and could be anything (such as would be used with an IHE XDS repoistory)

      "none" no content is expected or required for this endoint type (just making the connection will be enough notification for the receiving system. e.g. a ping connection to wake a service up to start receiving content)

      Show
      Include new codes to the example valueset for the concepts: " any " the content of the data used on the endpoint is undefined and could be anything (such as would be used with an IHE XDS repoistory) " none " no content is expected or required for this endoint type (just making the connection will be enough notification for the receiving system. e.g. a ping connection to wake a service up to start receiving content)
    • Cooper Thompson/Wes Richel: 6-0-0
    • Correction
    • Compatible, substantive
    • DSTU2

    Description

      Endpoint.payloadFormat is indicated as 1..1; yet even the description indicates that it should be blank if no payload. This item should be 0..* to support no payload; and to support a list of mime types.

      Secondary worry is that this i too disconnected from the list of payloadTypes. One might have a different mime type support for each of the payload types.

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_moehrke John Moehrke
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: