radiology codes - 2016-09 core #439

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Imaging Integration
    • ImagingStudy
    • 10.7.6
    • Hide

      Although the intent in the existing comment field, and in the ballot comment is good, ImagingStudy may be used for more than just radiology. This also reaches into other resources. Therefore, remove the ImagingStudy.procedure comment. Implementers will be left to determine the right value set for their environment.

      Show
      Although the intent in the existing comment field, and in the ballot comment is good, ImagingStudy may be used for more than just radiology. This also reaches into other resources. Therefore, remove the ImagingStudy.procedure comment. Implementers will be left to determine the right value set for their environment.
    • Doug Sluis/Brad Genereaux: 9-0-0
    • Correction
    • Non-substantive
    • DSTU2

      Existing Wording: Comments

      For the Procedure.code, LOINC radiology orderables would be a good value set to use.

      Proposed Wording: For the Procedure.code, LOINC radiology orderables would be a good value set to use. They were developed in a collaboration between LOINC/Regenstrief Inc, RadLex, and the Radiological Society of North America (RSNA).

      Comment:

      Agree with notion of use of LOINC. But should note that the LOINC codes are based on a model jointly developed and constructed by RadLex RSNA and LOINC. RSNA is very much behind it which will be good for its dissemination. Like the lab LOINC codes, there is a separable structure behind the simple code and name and these are RadLex codes.

      So at present, the anatomy codes are NOT SNOMED, in part because RadLex chose a different base coding system for anatomy think the one that is in OBO, and in part because at present SNOMED does not want to expand the domain of LOINC SNOMED cooperation beyond its current scope though we have asked.

      The key thing is that some of the components that are broken out into separate attributes in this specification will be available as separable components from the LOINC code and its companion RadLex parts. The other little worry is they may not align perfectly with DICOM (just dont know), though DICOM has been part of the collaboration.

      Summary:

      radiology codes

            Assignee:
            Unassigned
            Reporter:
            clemmcdonald
            clemmcdonald
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: