Explain whether cardinalities other than 0, 1 and * are allowed - 2018-Jan Core #127

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - Question answered
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • Profiling
    • 5.1.0.6
    • Hide

      Any cardinality that is a proper constraint of the resource is permitted in a profile. When defining resources, HL7 has a policy of limiting cardinality values to 0, 1 and * because more specific are generally context-specific and resources are required to be contextless. Profiles are typically context-specific, so tighter cardinalities are fine

      Show
      Any cardinality that is a proper constraint of the resource is permitted in a profile. When defining resources, HL7 has a policy of limiting cardinality values to 0, 1 and * because more specific are generally context-specific and resources are required to be contextless. Profiles are typically context-specific, so tighter cardinalities are fine
    • Richard Ettema/Grahame Grieve: 4-0-0
    • Enhancement

      Comment:

      Suggesting indicating whether or not a specific range in cardinality is supported. For example: 1..4. I'm not aware of any places in the base spec that a cardinality like that is used. Would a cardinality be supported whose max is not 0, 1 or *?

      Summary:

      Explain whether cardinalities other than 0, 1 and * are allowed

            Assignee:
            Unassigned
            Reporter:
            Sean McIlvenna
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: