Uploaded image for project: 'MedMij Standaarden'
  1. MedMij Standaarden
  2. MM-363

Add specification for what to do when endpoint "not-supported"

    Details

    • Type: Wijzigingsverzoek
    • Status: Gesloten
    • Priority: 3
    • Resolution: Rejected
    • Fix Version/s: Nader te bepalen
    • Blokkerend:
      Nee
    • Informatiestandaard:
      BgZ
    • Informatiestandaard onderdeel:
      Technisch

      Description

      The BgZ consists of many endpoints. A server may choose which it supports with a certain minimum (20).

      When it does not support an endpoint, the specification is unnecessarily unclear about what to expect. This means that both an empty Bundle and a Bundle with an OperationOutcome would be valid. In that case a client cannot see the difference between "no data" and "not supported". This seems relevant to know.

      The qualification testing currently also allows both variants. The first vendor implemented an HTTP 200 (OK) + OperationOutcome with severity information and issue code not-supported.

      I would like to see that behavior as the way to handle not-supported:

      <Bundle xmlns="http://hl7.org/fhir">
      <id value="5c7243b8-adda-4d34-be77-777ea7d32dbc"/>
      <type value="searchset"/>
      <total value="0"/>
      <link>
      <relation value="self"/>
      <url value="http://myserver.nl/MedMijServer/MedicationStatement?category=urn:oid:2.16.840.1.113883.2.4.3.11.60.20.77.5.3%7C6&_include=MedicationStatement:medication"/>
      </link>
      <entry>
      <resource>
      <OperationOutcome>
      <text>
      <status value="generated"/>
      <div xmlns="http://www.w3.org/1999/xhtml"> Feature not yet implemented. </div>
      </text>
      <issue>
      <severity value="information"/>
      <code value="not-supported"/>
      </issue>
      </OperationOutcome>
      </resource>
      <search>
      <mode value="outcome"/>
      </search>
      </entry>
      </Bundle>

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              edelman@nictiz.nl Pieter Edelman
              Reporter:
              henket Alexander Henket
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Estimations By Role

                  No roles have been estimated yet.