Clarify Questionnaire/SDC defintion element path type

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: High
    • Structured Data Capture (SDC) (FHIR)
    • 2.0 [deprecated]
    • FHIR Infrastructure
    • (many)
    • Hide

      Will update to refer to snapshot.id rather than snapshot.path.  (The former is unique, the latter is not.) Will also clarify that the id doesn't need to be explicitly defined as an element in the referenced StructureDefinition, but rather it needs to be an id that could be created in a derived profile by referring to a declared element and, as needed, appending a simple path.  For example, http://hl7.org/fhir/Patient#Patient.name.given.  However, for more complex things (e.g. referring to a particular extension or a particular repetition), it will be necessary to define a distinct profile where slicing ensures that a single element id corresponds to the desired element.  I.e. you would need to use http://somewhere.org/SomePatient#Patient.name.given:foo where 'foo' was a slice that referred to the first middle name in order to tie to a definition that specific.

      Will clarify that it is permissible to specify a definition that points to a 'complex' item where nested elements refer to 'child' items.  i.e. a group can be tied to a definition.  However, where this occurs, the definition for the group doesn't define an allowed answer, it merely provides navigational context for interpreting the items (questions) with leaf-level definitions.

       

       

      Show
      Will update to refer to snapshot.id rather than snapshot.path.  (The former is unique, the latter is not.) Will also clarify that the id doesn't need to be explicitly defined as an element in the referenced StructureDefinition, but rather it needs to be an id that could be created in a derived profile by referring to a declared element and, as needed, appending a simple path.  For example, http://hl7.org/fhir/Patient#Patient.name.given.   However, for more complex things (e.g. referring to a particular extension or a particular repetition), it will be necessary to define a distinct profile where slicing ensures that a single element id corresponds to the desired element.  I.e. you would need to use http://somewhere.org/SomePatient#Patient.name.given:foo  where 'foo' was a slice that referred to the first middle name in order to tie to a definition that specific. Will clarify that it is permissible to specify a definition that points to a 'complex' item where nested elements refer to 'child' items.  i.e. a group can be tied to a definition.  However, where this occurs, the definition for the group doesn't define an allowed answer, it merely provides navigational context for interpreting the items (questions) with leaf-level definitions.    
    • Grahame Grieve/Paul Lynch: 6-0-1
    • Clarification
    • Non-substantive

      In the SDC page on extraction, in the section on Definition-based extraction, it is specified that the Questionnaire.item.definition element be used:

      to point to the resource or profile element that Questionnaire item corresponds to. ... The definition SHALL have the full canonical URL of the resource (or profile) followed by '#' followed by the snapshot.path of the element the Questionnaire item corresponds to.

      And in the Questionnaire page, in the section on Questionnaire Definitions, it says:

      The url refers to an ElementDefinition in StructureDefinition, and always starts with the canonical URL for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.

      It is unclear why the SDC extraction page requires "snapshot.path", especially if we want to be able to refer to the elements of a complex type during extraction, for example with `Patient.name.given`. Should the correct defintion path be `http://hl7.org/fhir/StructureDefinition/Patient#Patient.name.given` or `http://hl7.org/fhir/StructureDefinition/HumanName#HumanName.given`?

      In a similar vein, what is a "fragment identifier", as referred to in the Questionnaire page? Is it a sort of path that can go into the fields of complex types (or even other resource types?) Is it different from other path types (snapshot.path, differential.path, fhirpath, ...)

      Summary: Clarify the definition of the type of path that appears in Questionnaire.item.definition and QuestionnaireResponse.item.definition, and is used for definition-based extraction (SDC).

            Assignee:
            Lloyd McKenzie
            Reporter:
            gabcbrown
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: