New Version Testing

Home Forums LOINC Groups New Version Testing

This topic contains 3 replies, has 4 voices, and was last updated by  brad hart 5 days, 13 hours ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #22756

    Vidyut Desai
    Participant

    Is there a guidelines/recommendations on new version testing?

    Given that the versions are backwards compatible, I would think new version should not impact any previously existing LOINC codes in any EMR/LIS.

    Thanks.

    #22796

    Andrea Pitkus
    Participant

    It depends on what you are using from the LOINC release.  Some of the descriptions such as the LOINC Long Name may be updated with each release.  There have been technical changes from time to time too which are in the release notes.

    #22815

    Karen Kovach
    Participant

    We use the Canadianized version of LOINC – pCLOCD and do have a process that compares the new version and latest version, the basics would be the same for LOINC.  The process produces 3 reports:  1) identifies net new terms  and will overwrite our local codes if one has been created and included in the newest version 2)  identifies terms that are not in the new version that were not in the last version (this should ideally not happen, but has on occasion).    3) identifies changes to term attritubutes  for terms that are mapped to our local LIS codes.   We use a locally developed tool for our mapping and have this process as a separate function within, we used to do this on spreadsheets which was very laborious.  Saskatchewan uses approx 4500 LOINC codes and on average need to review about a dozen terms per version update.

    Karen Kovach

    eHealth Saskatchewan

    Regina, Saskatchewan

    Canada

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.