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

Clarify Use of Bundle.link.relation

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Very High Very High
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Bundle
    • Hide

      We will add a required binding to make the expectation explicit.  This is a potentially breaking change and will need to be highlighted as such as part of R5.

       

      @vassil will consider submitting a change request for us to define some explicit recommended codes.  If that happens, we can change the overall binding to a 'max' binding and have an extensible binding to the recommended set.

      Show
      We will add a required binding to make the expectation explicit.  This is a potentially breaking change and will need to be highlighted as such as part of R5.   @vassil will consider submitting a change request for us to define some explicit recommended codes.  If that happens, we can change the overall binding to a 'max' binding and have an extensible binding to the recommended set.
    • Gino Canessa/Josh Mandel: 12-0-0
    • Correction
    • Non-compatible
    • R5

    Description

      Bundle.link.relation has the description:

      A name which details the functional use for this link - see http://www.iana.org/assignments/link-relations/link-relations.xhtml#link-relations-1 .

      This hints that the field should to be one of those values, but does not actually state one way or the other.

      Either the description should be clarified to indicate that the IANA link-relations are an example set to use, or clarified that the IANA values are expected (in which case, I would argue the type should change from string to code).

      Attachments

        Activity

          People

            rgeimer Rick Geimer
            ginocanessa Gino Canessa
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: