Use of "detailed metadata" separate resurce is confusing

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Terminology Infrastructure
    • Normative
    • CodeSystem
    • Hide

      Mark this section as informative because it's not making any rules, and the understanding of medications (for instance) is changing as the various medication terminologies iterate on the medication resources. May also make it somewhat less specific as well. Examples: Medication resource instances for RxNorm code details, ObservationDefinition instance for LOINC code details

      Show
      Mark this section as informative because it's not making any rules, and the understanding of medications (for instance) is changing as the various medication terminologies iterate on the medication resources. May also make it somewhat less specific as well. Examples: Medication resource instances for RxNorm code details, ObservationDefinition instance for LOINC code details
    • Rob Hausam/Grahame Grieve: 15-0-1
    • Correction
    • Non-substantive
    • STU3

      The described "division" of concept "detail" from basic concept information is very confusing. Both LOINC and RxNorm are provided as code system needing this but the one aligned existing resource, http://hl7.org/fhir/2018May/medication.html, does not seem to be used for RxNorm. In fact all the content of the two example code systems would presumably be captured in any FHIR TS using the base code system resource via properties and relationships (as properties. ) Better real examples and clarity on impact need to be provided. Particulalry the impact of implementing this on Lookup and other code system operations.

            Assignee:
            Unassigned
            Reporter:
            Rob McClure
            Rob McClure
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: