associatedFeature Observation.component cardinality seems off

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium

      In the AssociatedFeature profile, the current cardinality for Observation.component is 0..0 even though there is at least 1 required slice. It seems like it should be 1..2 (to account for the required featureType and optional obsCount)

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: