Uploaded image for project: 'Other Specification Feedback'
  1. Other Specification Feedback
  2. OTHER-2617

SFCU *can* reference Observations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • Cross Paradigm Gender Harmony - Sex and Gender Representation (OTHER)
    • 1.0.0-ballot
    • Terminology Infrastructure
    • FHIR Guidance
    • 11.3.1
    • Hide

      Original Text:

      We opted to include the Sex for Clinical Use value in-line rather than as a reference to Observation after discussion on tradeoffs between two options. We felt that the in-line option was simpler while being sufficiently expressive. An extension with a reference to Observation allows for the expression of complex metadata associated with the value, however we expect the need for that complex metadata would be sufficiently rare to not outweigh the benefits of the simpler in-line extension option.

      Note to balloters: Input on the approach of an extension with an in-line value vs. an extension with a reference to an Observation is appreciated.

       

      New Text:

      We opted to include the Sex Parameter for Clinical Use value in-line rather than as a reference to Observation after discussion on tradeoffs between two options. We felt that the in-line option was simpler while being sufficiently expressive. An extension with a reference to Observation allows for the expression of complex metadata associated with the value, however we expect the need for that complex metadata would be sufficiently rare to not outweigh the benefits of the simpler in-line extension option.

      Note that in this discussion, there are two types of relevant observations:

      • The Observation which describes the SPCU.
      • Any Observations such as organ inventory or lab results that is supporting info for the SPCU.  This information may be communicated as supportingInfo.

       

      Show
      Original Text: We opted to include the Sex for Clinical Use value in-line rather than as a reference to Observation after discussion on tradeoffs between two options. We felt that the in-line option was simpler while being sufficiently expressive. An extension with a reference to Observation allows for the expression of complex metadata associated with the value, however we expect the need for that complex metadata would be sufficiently rare to not outweigh the benefits of the simpler in-line extension option. Note to balloters: Input on the approach of an extension with an in-line value vs. an extension with a reference to an Observation is appreciated.   New Text: We opted to include the Sex Parameter for Clinical Use value in-line rather than as a reference to Observation after discussion on tradeoffs between two options. We felt that the in-line option was simpler while being sufficiently expressive. An extension with a reference to Observation allows for the expression of complex metadata associated with the value, however we expect the need for that complex metadata would be sufficiently rare to not outweigh the benefits of the simpler in-line extension option. Note that in this discussion, there are two types of relevant observations: The Observation which describes the SPCU. Any Observations such as organ inventory or lab results that is supporting info for the SPCU.  This information may be communicated as supportingInfo.  
    • Carol Macumber / MaryKay McDaniel : 5-0-0
    • Clarification
    • Non-substantive

    Description

      The SFCU extension includes a supportingInfo CodeableReference which provides the ability to reference an Observation if needed. This discussion should be updated to reflect that.

      Existing Wording:

      We opted to include the Sex for Clinical Use value in-line rather than as a reference to Observation after discussion on tradeoffs between two options. We felt that the in-line option was simpler while being sufficiently expressive. An extension with a reference to Observation allows for the expression of complex metadata associated with the value, however we expect the need for that complex metadata would be sufficiently rare to not outweigh the benefits of the simpler in-line extension option.

      Note to balloters: Input on the approach of an extension with an in-line value vs. an extension with a reference to an Observation is appreciated.

      (Comment 59 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            Rongparker Ron G. Parker
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: