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

Allow multiple codes on Observation-based population and extract profiles

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Structured Data Capture (SDC) (FHIR)
    • current
    • FHIR Infrastructure
    • Extractable Questionnaire [deprecated]
      Populatable Questionnaire [deprecated]
    • Hide

      We will make item.code repeat on the extractable profiles (i.e. will remove the 0..1 constraint)

      We will add the context of Questionnaire.item.code to the extract extension.

      Will change this line on the extraction page "

      Multiple item.code elements might be present. If so, each are considered one of the Observation.code Codings in the resulting extracted Observation."

      to

      "If the extension appears on specific item.code elements rather than the item as a whole, then only the specified codes should be propagated rather than all.  For example, an item might list codes for "Body weight", "Body weight (clothed)" and "Body weight (unclothed)".  In that case, only the "Body weight" code would be appropriate to include in the extracted content, even though all three might be appropriate for population.  If any item.codes are tagged with 'true', then only the tagged Codings will propagate.  I.e. any sibling item.codes with no extension are considered to have an extension of 'false'.  If no extension appears on any of the item.codes but an extension appears on the item, an ancestor item or the Questionnaire as a whole, then all codes are considered to be roughly equivalent translations and to be appropriate to list as sibling Codings within Observation.code.

      If an item has the extension flag set to 'true', some descendant items may have the extension with a value of 'false'.  If this occurs, then the item tagged with 'false' and its descendants will be excluded from the extraction process."

       

       

      Show
      We will make item.code repeat on the extractable profiles (i.e. will remove the 0..1 constraint) We will add the context of Questionnaire.item.code to the extract extension. Will change this line on the extraction page " Multiple  item.code  elements might be present. If so, each are considered one of the Observation.code Codings in the resulting extracted Observation." to "If the extension appears on specific item.code elements rather than the item as a whole, then only the specified codes should be propagated rather than all.  For example, an item might list codes for "Body weight", "Body weight (clothed)" and "Body weight (unclothed)".  In that case, only the "Body weight" code would be appropriate to include in the extracted content, even though all three might be appropriate for population.  If any item.codes are tagged with 'true', then only the tagged Codings will propagate.  I.e. any sibling item.codes with no extension are considered to have an extension of 'false'.  If no extension appears on any of the item.codes but an extension appears on the item, an ancestor item or the Questionnaire as a whole, then all codes are considered to be roughly equivalent translations and to be appropriate to list as sibling Codings within Observation.code. If an item has the extension flag set to 'true', some descendant items may have the extension with a value of 'false'.  If this occurs, then the item tagged with 'false' and its descendants will be excluded from the extraction process."    
    • Brian Postlethwaite/Paul Lynch: 5-0-0
    • Enhancement
    • Compatible, substantive

    Description

      A couple of profile changes are required to resolve FHIR-22703:

      1. Observation-based population and extract profiles should allow multiple codes to be present in an item (as allowed by the core Questionnaire)
      a. Populatable Questionnaire - Observation
      b. Extractable Questionnaire - Observation

      2. If we are allowing multiple codes in an item, the observation-extract extension should be changed to Coding (instead of boolean) to indicate exactly which code is going to be used for extraction. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            joeegarcia Josephine Garcia (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: