Clarify path resolution rules for PlanDefinition

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: High
    • FHIR Core (FHIR)
    • STU3
    • Clinical Decision Support
    • PlanDefinition
    • 12.18.6
    • Hide

      Update documentation as suggested:

      The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ([x]) to traverse multiple-cardinality sub-elements. Note that the index must be an integer or string constant

      Show
      Update documentation as suggested: The specified path must be resolvable from the type of the required data. The path is allowed to contain qualifiers (.) to traverse sub-elements, as well as indexers ( [x] ) to traverse multiple-cardinality sub-elements. Note that the index must be an integer or string constant
    • Floyd Eisenberg/Bas van den Heuvel: 12-0-0
    • Clarification
    • Non-substantive
    • STU3

      PlanDefinition.action.dynamicValue.path should clarify path resolution rules (should use the same rules as DataRequirement path elements (http://hl7.org/fhir/metadatatypes-definitions.html#DataRequirement.dateFilter.path) (without the restriction on result type of the resolved path)

            Assignee:
            Unassigned
            Reporter:
            Bryn Rhodes
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: