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

What does it mean when min=0 and no 'must support'

    XMLWordPrintableJSON

    Details

    • Type: Question
    • Status: Resolved - No Change (View Workflow)
    • Priority: Medium
    • Resolution: Considered - Question answered
    • Specification:
      US CARIN Blue Button (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Financial Mgmt
    • Related Page(s):
      (NA)
    • Related Section(s):
      profiles
    • Resolution Description:
      Hide

      Fields that are min=0 without MS are not required to be supported by servers or clients.

      They are essentially not of interest for the use cases supported by this IG.

      In the real world, these fields will probably not be supported by servers, and will be ignored by clients.   Constraining to 0..0 blocks a subsequent IG from profiling this one if the field becomes important.

      Show
      Fields that are min=0 without MS are not required to be supported by servers or clients. They are essentially not of interest for the use cases supported by this IG. In the real world, these fields will probably not be supported by servers, and will be ignored by clients.   Constraining to 0..0 blocks a subsequent IG from profiling this one if the field becomes important.

      Description

      A-Q
      profiles: From a conformance perspective what does it mean when min=0 and no 'must support' is it a MAY? and what is going to happen in the real world when implementers have deadlines and see all this optional shit?

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            ehaas Eric Haas
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: