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

Make expectations around 'required' super-explicit

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Terminologies
    • Hide

      Will add a paragraph to the 'required' section:

      "The use of an extension (e.g. [data-absent-reason]) cannot be used to bypass required binding requirements.  The binding must be satisfied regardless of what extensions are present."

      and to the 'extensible' section:

      "The use of an extension (e.g. [data-absent-reason]) cannot be used to bypass extensible binding requirements.  For example, if a value set includes the concept of "unknown", then a [data-absent-reason] of "unknown" cannot be sent without sending a Coding with the "unknown" concept.  (In which case also sending an 'unknown' DAR would be inappropriate and unnecessary.)

      Show
      Will add a paragraph to the 'required' section: "The use of an extension (e.g. [data-absent-reason] ) cannot be used to bypass required binding requirements.  The binding must be satisfied regardless of what extensions are present." and to the 'extensible' section: "The use of an extension (e.g. [data-absent-reason] ) cannot be used to bypass extensible binding requirements.  For example, if a value set includes the concept of "unknown", then a [data-absent-reason] of "unknown" cannot be sent without sending a Coding with the "unknown" concept.  (In which case also sending an 'unknown' DAR would be inappropriate and unnecessary.)
    • Rick Geimer / Alexander Henket: 26-0-2
    • Clarification
    • Non-substantive
    • R5

    Description

      There are some people who still aren't completely clear on the expectations around 'required' bindings.  Thus suggest adding a paragraph to the 'required' section:

      "The use of an extension (e.g. [data-absent-reason]) cannot be used to bypass required binding requirements.  The binding must be satisfied regardless of what extensions are present."

      and to the 'extensible' section:

      "The use of an extension (e.g. [data-absent-reason]) cannot be used to bypass extensible binding requirements.  For example, if a value set includes the concept of "unknown", then a [data-absent-reason] of "unknown" cannot be sent without sending a Coding with the "unknown" concept.  (In which case also sending an 'unknown' DAR would be inappropriate and unnecessary.)

      Attachments

        Activity

          People

            GrahameGrieve Grahame Grieve
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: