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

Clarify she/her/hers as single or multiple pronouns

XMLWordPrintableJSON

    • 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
    • Model
    • 3.2.6
    • Hide

      In review of this we found that the related url included in the issue is a faithful representation of the original logical model: Pronouns have a binding of Extensible but our new model uses Example. Resolution is

      • Add a new 3.2.1 section called "Model Updates" on that page that highlights the changes we have made in the new model from the old, including changes in the binding strengths. 
        • Move text from 3.2 to 3.2.1 and adapt as below
          • With the exception of the following updates, the model included in this implementation guide is exactly in the published Gender Harmony Informative Specification.
            • Addition of Recorded Sex or Gender attribute = type with datatype = code or constrained text
              • The addition was made to clarify and cover the original intent of Record Sex or Gender, including the ability to specify the type or category of sex or gender that is recorded (e.g., Sex Assigned At Birth)."
            • Update of Pronoun binding strength
              • The binding strength to the Pronoun value set was originally extensible. In review with product line management, this was updated to example across products to allow for greater flexibility in establishing a base set of jurisdiction appropriate pronouns
      • Update current Model 3.2.6 Pronouns to change binding Strength from extensible to example
      • Add short addition to Description element in the Pronouns value set (currently in FHIR but to be moved to THO) 
        • "The set of pronouns included are expected to be supplemented when implemented with additional useful concepts, likely including those representing each individual forms of the pronoun set (subjective, objective, possessive.)"
      • In V2 Chapter 2C - table 0822 personal pronouns, value set information table
        • Currently says "This value set defines a set of codes that can be used to indicate the pronouns used to communicate about an individual."
        • Should say "This value set defines an initial set of codes that can be used to indicate the pronouns used to communicate about an individual. Some jurisdictions will want to add additional codes, such as those for the individual possessive forms."
      • In cross paradigm IG Design Consideration, "Supports additional values (extensible)" should be changed to "Supports additional values (example)" under Pronouns
      Show
      In review of this we found that the related url included in the issue is a faithful representation of the original logical model: Pronouns have a binding of Extensible but our new model uses Example. Resolution is Add a new 3.2.1 section called "Model Updates" on that page that highlights the changes we have made in the new model from the old, including changes in the binding strengths.  Move text from 3.2 to 3.2.1 and adapt as below With the exception of the following updates, the model included in this implementation guide is exactly in the published Gender Harmony Informative Specification. Addition of Recorded Sex or Gender attribute = type with datatype = code or constrained text The addition was made to clarify and cover the original intent of Record Sex or Gender, including the ability to specify the type or category of sex or gender that is recorded (e.g., Sex Assigned At Birth)." Update of Pronoun binding strength The binding strength to the Pronoun value set was originally extensible . In review with product line management, this was updated to example across products to allow for greater flexibility in establishing a base set of jurisdiction appropriate pronouns Update current Model 3.2.6 Pronouns to change binding Strength from extensible to example Add short addition to Description element in the Pronouns value set (currently in FHIR but to be moved to THO)  "The set of pronouns included are expected to be supplemented when implemented with additional useful concepts, likely including those representing each individual forms of the pronoun set (subjective, objective, possessive.)" In V2 Chapter 2C - table 0822 personal pronouns, value set information table Currently says "This value set defines a set of codes that can be used to indicate the pronouns used to communicate about an individual." Should say "This value set defines an initial set of codes that can be used to indicate the pronouns used to communicate about an individual. Some jurisdictions will want to add additional codes, such as those for the individual possessive forms." In cross paradigm IG Design Consideration, "Supports additional values (extensible)" should be changed to "Supports additional values (example)" under Pronouns
    • Riki Merrick / Sean Muir : 13-0-0
    • Clarification
    • Compatible, substantive
    • current

      Provide text to clarify whether "she", "her", "hers" represent three pronouns or one combined "she/her/hers" pronoun. Clarify how to handle cases like "they/her/its" where a mix of pronouns are used, or "they/her/[Name's]" where they actually don't want a pronoun used for possessive.

      (Comment 31 - imported by: Lloyd McKenzie)

            Rob_McClure Rob McClure
            Rongparker Ron G. Parker
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: