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

Incorrect use of observation.component

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • At-Home In-Vitro Test Report (FHIR)
    • 1.0.0-ballot
    • Orders & Observations
    • STU
    • Technical Guidance
    • Hide

      Changed this from a Question to a Change Request

      Will update modeling to use hasMember (referencing Observation-at-home-in-vitro-test-result) for multiplex assay tests, rather than using component.

      High-level structure will be:
       * DiagnosticReport
       ** Observation (panel/device)
       *** hasMember.Observation1
       *** hasMember.Observation2

       Will also update wording to align with new modeling (see FHIR-38411)

      Show
      Changed this from a Question to a Change Request Will update modeling to use hasMember (referencing Observation-at-home-in-vitro-test-result) for multiplex assay tests, rather than using component. High-level structure will be:  * DiagnosticReport  ** Observation (panel/device)  *** hasMember.Observation1  *** hasMember.Observation2  Will also update wording to align with new modeling (see FHIR-38411 )
    • Sarah Gaunt / Dan Rutz : 13 - 0 - 2
    • Correction
    • Compatible, substantive

    Description

      Multiplex Assay tests that serve as a single test to diagnose infection caused by multiple viruses (e.g. CDC Flu SC2 Multiplex Assay for SARS-CoV-2, influenza A, and/or influenza B viruses), use multiple Observation.component elements to record each type of test.

      I am not sure this statement is correct - I think individual results for different viruses should be sent as separate observations grouped by observation.hasMember for the ordered panel, becasue each interpretation is different (detected for Flu A would be abnormal, but not detected for SARS-COV-2, Flu B would be normal). Component should be used when interpretation is the same across all components, though I see, that component has its own interpretation now  - maybe bring this one to an OO Lab call, or the main call for discussion

      Attachments

        Activity

          People

            minigrrl Sarah Gaunt
            RikiM Ulrike Merrick
            Ulrike Merrick
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: