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

Define a place to record Name-to-use comment text.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R4
    • Patient Administration
    • Patient
    • 8
    • Hide

       While the model includes a comment for Name-to-use, there is not a clear use case, and so does not meet the 80/20 bar for inclusion in the base FHIR spec.

       

      We considered whether to create an extension in the Gender Harmony IG, but as with the base spec, we don't have a clear use case, so we are proposing that if a future use-case specific implementation guide needs a comment, the authors of that IG can define the extension in that IG.

      Show
       While the model includes a comment for Name-to-use, there is not a clear use case, and so does not meet the 80/20 bar for inclusion in the base FHIR spec.   We considered whether to create an extension in the Gender Harmony IG, but as with the base spec, we don't have a clear use case, so we are proposing that if a future use-case specific implementation guide needs a comment, the authors of that IG can define the extension in that IG.
    • Rob McClure / Brian Postlethwaite : 10-0-0

    Description

      Gender harmony defines a comment to provide context for name-to-use (name.use=usual). It doesn't appear that this elment is mapped in FHIR. Define a standard mechanism, such as an extension to record a comment on use.

      (Also filed against Gender Harmony ballot.)

      (Comment 2 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: