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

US Core SFCU Extension not aligned with R5 SFCU Extension

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Core (FHIR)
    • 5.0.1
    • Cross-Group Projects
    • US Core Sex For Clinical Use [deprecated]
    • Hide

      For the current ballot of US Core, remove the SFCU extension, and retain the birth-sex extension as the mechanism to meet USCDI Patient Sex. 

       

      Rationale: (see comments)

      Show
      For the current ballot of US Core, remove the SFCU extension, and retain the birth-sex extension as the mechanism to meet USCDI Patient Sex.    Rationale: (see comments)
    • Eric Haas/Jason Vogt: 12-0-0
    • Clarification
    • Compatible, substantive

    Description

      13.157.1

       

      Issues with the proposed extension to implement the USCDI v3 data element sex.
      1. To implement USCDI v3 sex and message that it is "SFCU like" is helpful, however
      • the US Core SFCU extension as defined does not include supportingInfo 

      which is important to understanding the meaning of SFCU http://hl7.org/fhir/2022Sep/extension-patient-sexforclinicaluse.html.  Suggest comparing and contrasting the two extensions

      • The extension and element name should not be sex for clinical use - avoid potential confusion with the FHIR R5 SFCU
      • The US Core extension is defined only for Patient whereas the R5 SFCU extension may be used on many resources
      • The US Core SFCU code system is not the applicable vocabulary standard as defined in USCDI v3 - providing a mapping to SNOMED CT is interesting, but by having a separate code system that is very close to that in terms of concepts to the one proposed in FHIR R5 sends the message that this extension is the same as the proposed FHIR R5 extension - and its not. Its similar, but not the same. 
      • I realize these issues might not become issues until FHIR R5 is published, and that this version of US Core is based on FHIR R4, however there are probably adjustments that can be made to clarify the intended use and path forward. |

         

      Attachments

        Activity

          People

            Unassigned Unassigned
            carmela_couderc Carmela A. Couderc
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: