Clarify LOINC mappings for ElementDefinition - 2018-May Core Norm Infrastructure #78

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • FHIR Infrastructure
    • ElementDefinition
    • 2.29.2.1
    • Hide

      that mapping needs to be clearer, and we need a section or a reference to one about the relationship between LOINC, element definitions, and observation definitions

      Show
      that mapping needs to be clearer, and we need a section or a reference to one about the relationship between LOINC, element definitions, and observation definitions
    • Grahame Grieve/Rick Geimer: 9-0-0
    • Non-substantive
    • STU3

      Existing Wording: ElementDefinition.requirements

      Definition: This element is for traceability of why the element was created and why the constraints exist as they do. This may be used to point to source materials or specifications that drove the structure of this element.

      LOINC Code: R/O/C

      Comment:

      I don't believe that the definition of ElementDefinition.requirements matches the LOINC meaning (which flags content as required, optional, or conditional).

      Further, why do ElementDefinition elements have a LOINC mapping listed in the detailed description, rather than on the mappings page?

      Summary:

      Clarify LOINC mappings for ElementDefinition

            Assignee:
            Unassigned
            Reporter:
            Elliot Silver
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: