2015May sdc #150 - A requested fix for profiling.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • ElementDefinition
    • Hide

      Motion: We think this ballot comment is the result of a misunderstanding of the specification, but we agree that the spec is not as clear as it needs to be! We will add an example to the spec indicating how to achieve the desired result described at?http://stackoverflow.com/questions/29969955/fhir-profile-structdef-how-are-children-sub-elements-of-a-named-slice-tied-to.?

      Show
      Motion: We think this ballot comment is the result of a misunderstanding of the specification, but we agree that the spec is not as clear as it needs to be! We will add an example to the spec indicating how to achieve the desired result described at? http://stackoverflow.com/questions/29969955/fhir-profile-structdef-how-are-children-sub-elements-of-a-named-slice-tied-to.?
    • Marten / Kevin: 6-0-0
    • Enhancement
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: eld-5: Either a namereference or a fixed value (but not both) is permitted (xpath: not(exists(f:nameReference) and exists(f:*[starts-with(local-name(.), 'value')])))

      Proposed Wording: Remove eld-5

      Comment:

      Current profile capability seems to limit the ability to uniquely define a constrain sliced sub-element.

      http://stackoverflow.com/questions/29969955/fhir-profile-structdef-how-are-children-sub-elements-of-a-named-slice-tied-to

            Assignee:
            Unassigned
            Reporter:
            Calvin E. Beebe
            Calvin E. Beebe
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: