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

Core extensions should have min cardinality zero

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • (many)
    • Hide

      There are theoretical situations where, if an extension appears in a profile, it's nonsensical for it to be absent.  So rather than an error, spit out a warning if the root element in an extension definition has min!=0

      Show
      There are theoretical situations where, if an extension appears in a profile, it's nonsensical for it to be absent.  So rather than an error, spit out a warning if the root element in an extension definition has min!=0
    • Rick Geimer / Gino Canessa: 13-0-2
    • Enhancement
    • Non-substantive
    • R5

    Description

      https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Hard.20coding.20an.20Extension.3A.20messageheader-response-request/near/263183813

       

      The build tooling should prevent Core extensions from defining min cardinality higher than zero. (Obviously a profile can define slices where an extension is required...)

      Attachments

        Activity

          People

            GrahameGrieve Grahame Grieve
            jmandel Josh Mandel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: