Uploaded image for project: 'Health'
  1. Health
  2. HEALTH-146

LOINC codes for Analysis Sevices. Re-applying LIMS' Analyte CAS #s

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1.2, 3.1.5
    • Fix Version/s: None
    • Labels:
      None

      Description

      Finally we have to do it. Some labs use codes for quick test selection, e.g. from a 1000 analytes

      in LIMS it'll be the CAS #

      in Health LOINC #

      See attached file of LOINC numbers collected - front 3 sheets were left blank for labs to list their own tests and then x -refernce them using the LOINC codes

      The idea thus to apply Bika Analysis Services coding generically, referencing the code used (Could be more than one in some instances)

      NB Note For full LOINC compliance, all other fields passed down interfaces need to be tagged with their LOINC codes too, e.g. patient ID etc

        Activity

        Hide
        xispa Jordi (Inactive) added a comment -

        The correspondence between Analysis Services and LOINC tests can cause missunderstandings, imo. Specially when the number of tests available is high.
        I suggest the user be able to 'select' a LOINC test when creating an AS: the AS name and code will be automatically populated then. Moreover, if the related LOINC's "Laboratory Term Class" for that LOINC test/AS doesn't exist yet as an AS Bika Category, the system could create it automatically.
        The same could be applied for: "LOINC Term Class" - "Analysis Service Category" and "LOINC Panels" - "Analysis Request Template" relations.

        Show
        xispa Jordi (Inactive) added a comment - The correspondence between Analysis Services and LOINC tests can cause missunderstandings, imo. Specially when the number of tests available is high. I suggest the user be able to 'select' a LOINC test when creating an AS: the AS name and code will be automatically populated then. Moreover, if the related LOINC's "Laboratory Term Class" for that LOINC test/AS doesn't exist yet as an AS Bika Category, the system could create it automatically. The same could be applied for: "LOINC Term Class" - "Analysis Service Category" and "LOINC Panels" - "Analysis Request Template" relations.
        Hide
        lemoene lemoene added a comment -

        The way I interpretted it is for the current Bika ASs must map to the LOINC tests 1 to 1, ditto Bika Analysis Categories, Bika Analysis Profiles/Templates and LOINC Panels and it should all be resolved in te system set-up. E.g. every one of these in the Bika set-up should uniquelu map to its LOINC equivalent.

        Getting the system to create objects automatically I think is notb necessary and over-complicates things?

        Show
        lemoene lemoene added a comment - The way I interpretted it is for the current Bika ASs must map to the LOINC tests 1 to 1, ditto Bika Analysis Categories, Bika Analysis Profiles/Templates and LOINC Panels and it should all be resolved in te system set-up. E.g. every one of these in the Bika set-up should uniquelu map to its LOINC equivalent. Getting the system to create objects automatically I think is notb necessary and over-complicates things?
        Hide
        xispa Jordi (Inactive) added a comment -

        Since any AS can be linked to a specific LOINC test, this relation should be displayed/modified somewhere in-site. Therefore, a field 'LOINC Test' with a searchable textbox linked to registered "LOINC Tests" must be added inside the AS creation/edit form. Manual creation of LOINC tests (or Term classes, etc.) has no sense imo, so Bika Health should have, by default, all LOINC tests registered in the system, also if no setup-data import is done. The same applies for Analysis categories and AR Templates/Profiles.

        Not sure, but in most cases I suppose the user will set the same AS name and keyword to newly created ASes as those from the 'linked' LOINC test. Why don't to use the 'LOINC Test' field described above to automatically set the name and keyword of the AS to be created? IMO, it will make the creation easier and will help to avoid missunderstandings between AS keywords and LOINC tests codes.

        Regards to the automatic creation of 'Analysis Service Categories' due to the creation of new ASes linked to a LOINC: I was thinking about the registry form (HEALTH-140), in which the tests must be displayed inside panels. These panels should be displayed/hide depending the 'AR Template' or 'AS Category' selected. As far as Bika's Categories have to be linked again with LOINC Term Classes, I think the best way is to follow the same procedure descibed above for AS. That will help to maintain the integrity and consistency of all the system. LOINC's Term Classes must be registered in the system by default again, so I think that the automatic creation of the missing Bika's category linked to the LOINC Term class to which the new AS is associated (by using the linked LOINC Test info), might speed up the process, as well as, ensure the integrity and consistency again.

        Thinking loud: another option could be to create all LOINC Term classes as Analysis Categories and set all of them disabled by default during the site creation.

        Show
        xispa Jordi (Inactive) added a comment - Since any AS can be linked to a specific LOINC test, this relation should be displayed/modified somewhere in-site. Therefore, a field 'LOINC Test' with a searchable textbox linked to registered "LOINC Tests" must be added inside the AS creation/edit form. Manual creation of LOINC tests (or Term classes, etc.) has no sense imo, so Bika Health should have, by default, all LOINC tests registered in the system, also if no setup-data import is done. The same applies for Analysis categories and AR Templates/Profiles. Not sure, but in most cases I suppose the user will set the same AS name and keyword to newly created ASes as those from the 'linked' LOINC test. Why don't to use the 'LOINC Test' field described above to automatically set the name and keyword of the AS to be created? IMO, it will make the creation easier and will help to avoid missunderstandings between AS keywords and LOINC tests codes. Regards to the automatic creation of 'Analysis Service Categories' due to the creation of new ASes linked to a LOINC: I was thinking about the registry form ( HEALTH-140 ), in which the tests must be displayed inside panels. These panels should be displayed/hide depending the 'AR Template' or 'AS Category' selected. As far as Bika's Categories have to be linked again with LOINC Term Classes, I think the best way is to follow the same procedure descibed above for AS. That will help to maintain the integrity and consistency of all the system. LOINC's Term Classes must be registered in the system by default again, so I think that the automatic creation of the missing Bika's category linked to the LOINC Term class to which the new AS is associated (by using the linked LOINC Test info), might speed up the process, as well as, ensure the integrity and consistency again. Thinking loud: another option could be to create all LOINC Term classes as Analysis Categories and set all of them disabled by default during the site creation.
        Hide
        lemoene lemoene added a comment -

        Is happening for CAS numbers in LIMS now. We need to take a fresh look after rockfruit is done, then requote for adapting it to LOINC for the Namibian Labs

        Show
        lemoene lemoene added a comment - Is happening for CAS numbers in LIMS now. We need to take a fresh look after rockfruit is done, then requote for adapting it to LOINC for the Namibian Labs

          People

          • Assignee:
            Unassigned
            Reporter:
            lemoene lemoene
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 2 days
              2d
              Remaining:
              Remaining Estimate - 2 days
              2d
              Logged:
              Time Spent - Not Specified
              Not Specified