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

Improve narrative guidance and validation of errors where coding.code does not match display

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US CARIN Blue Button (FHIR)
    • current
    • Financial Mgmt
    • C4BB Explanation Of Benefit
    • Hide

      It is beyond the scope of an IG to declare what is considered fair use and there is not consensus to declare that this information must be included. However, FHIR does require that the coding.display be a valid value from the code system and guidance will be added to the guide stating that and providing some consideration that may lead to implementers adding display or text valuesas defined in the resolution in  FHIR-31069.

      Summarized for this ticket:

      Add guidance in general guidance section (under CapabilityStatement Server Requirement) called "Payer Considerations for App Rendering"

      Many of the codes used in this guide are proprietary with [licensing requirements](Terminology.html). While it is recommended that consumer apps acquire the necessary licenses to show descriptions for these codes, not all app developers may be in a position to do so. Because of this, payers MAY choose to provide a concept text `[CodeableConcept].text` or the coding display `[CodeableConcept].coding.display. It is the responsibility of the payer to make sure that the descriptions provided are correct.

       

      If the 'display' element is populated, the string used in `displaySHALL be one of the display strings defined for that code by the code system (code systems may define multiple display strings for a single code).

      With the additional statement noting that "If the code description available is not known to be an exact match of a display string defined by the code system, the  `[CodeableConcept].text` should be used in place of the `[CodeableConcept].coding.display`."

       

      Show
      It is beyond the scope of an IG to declare what is considered fair use and there is not consensus to declare that this information must be included. However, FHIR does require that the coding.display be a valid value from the code system and guidance will be added to the guide stating that and providing some consideration that may lead to implementers adding display or text valuesas defined in the resolution in   FHIR-31069 . Summarized for this ticket: Add guidance in general guidance section (under CapabilityStatement Server Requirement) called "Payer Considerations for App Rendering" Many of the codes used in this guide are proprietary with  [licensing requirements] (Terminology.html). While it is recommended that consumer apps acquire the necessary licenses to show descriptions for these codes, not all app developers may be in a position to do so. Because of this, payers  MAY  choose to provide a concept text ` [CodeableConcept] .text` or the coding display ` [CodeableConcept] .coding.display. It is the responsibility of the payer to make sure that the descriptions provided are correct.   If the 'display' element is populated, the string used in ` display `  SHALL  be one of the display strings defined for that code by the code system (code systems may define multiple display strings for a single code). With the additional statement noting that  "If the code description available is not known to be an exact match of a display string defined by the code system, the  ` [CodeableConcept] .text` should be used in place of the ` [CodeableConcept] .coding.display`."  
    • Corey Spears / Mary Kay McDaniel: 9-0-0
    • Clarification
    • Non-substantive
    • Yes
    • current

    Description

      Narrative guidance and resource instance validation needs to be improved to ensure that coding.display values match the meaning defined in the codeSystem for the coding.code. 

      This is a server-side responsibility that needs to be clarified and underscored in the IG.  Inclusions of the correct display for a code is permitted by codeSystem usage licenses held by the organization serving up the data. It needs to be highlighted in the IG within the section about Terminology so that server-side obligations are clear, and to make it clear that including the display element is allowed under fair use of a licensed codeSystem.  

      See example on slide 5

      Attachments

        Activity

          People

            Unassigned Unassigned
            LisaRNelson Lisa R. Nelson
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: