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

minValueSet should not be a SHOULD

    XMLWordPrintableJSON

Details

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

      Discussed and voted to not change SHOULD to MAY. 

      Show
      Discussed and voted to not change SHOULD to MAY. 
    • Reuben Daniels/Peter Jordan: 3-0-1

    Description

      FHIR-23707 asserts that the use of minValueSet is a 'SHOULD'.  I strongly argue this is not true.  The vast majority of places where FHIR implementation guides mark elements as mustSupport with either required or extensible bindings, there is no need for declaring minValueSet and, in fact, no chance of agreeing to them.  This should be changed to 'may'.  We might want to add some guidance on when having a minValueSet is appropriate, but it's not a generic SHOULD across all specifications.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: