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

DiagnosticReport codes include all of LOINC

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Orders & Observations
    • DiagnosticReport
    • Hide

      We will adjust the definition for DiagnosticReport.code to read:

      "A LOINC code or name that describes this diagnostic report. While this code set is not restricted, the code should appropriately represent the DiagnosticReport." 

       

       

      Show
      We will adjust the definition for DiagnosticReport.code to read: "A LOINC code or name that describes this diagnostic report. While this code set is not restricted, the code should appropriately represent the DiagnosticReport."     
    • Hans Buitendijk / Riki Merrick : 8 - 0 - 1
    • Clarification
    • Non-substantive
    • R6

    Description

      Is it really the intent to use all of LOINC as this preferred value set? Using all of LOINC doesn't provide much guidance.

      Should it be restricted to scale:doc, or similar? All uses of the ValueSet within the spec are preferred; there's no harm in choosing a too narrow definition, since users can add other values if they want.

      Attachments

        Activity

          People

            jdlnolen John D.L. Nolen
            esilver Elliot Silver
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: