Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25340

Contradiction in the requirement to use SNOMED codes

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Laboratory Results Interface (LRI) (US) (V2)
    • 2.5.1_R1_2021SEP [deprecated]
    • Orders & Observations
    • OBX_LRI Profile
    • Hide

      Remove the sentence "This guide recommends the use of SNOMED CT for senders, with a reminder, that a future release of this guide will require the use of SNOMED CT for result reporting." under Usage Notes in Section 9.11.1

       

      Show
      Remove the sentence "This guide recommends the use of SNOMED CT for senders, with a reminder, that a future release of this guide will require the use of SNOMED CT for result reporting." under Usage Notes in Section 9.11.1  
    • Marti Velezis / Craig Newman: 9-0-4
    • Clarification
    • Non-substantive

    Description

      The LRI_PH_Component states in the Usage Notes for the OBX segment that "For coded lab test results SNOMED CT shall be used as the standard coding system for this field (OBX-5) if an appropriate SNOMED CT code exists."

      And the Usage Note for the LRI_PH_Component in Section 9.11.1 says "For coded test results SNOMED CT shall be used, if a suitable code exist."

      These two statements are consistent, but early in Section 9.11.1 it says "This guide recommends the use of SNOMED CT for senders, with a reminder, that a future release of this guide will require the use of SNOMED CT for result reporting."

      This third statement seems to be in conflict as it only "recommends" SNOMED. Perhaps the statement that this is for "senders" is important, but if so, the various statements should be clarified.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            craig.newman Craig Newman
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: