LOINC Reload - 2.70 and 2.71

[jamlung-ri]

We have received both LOINC versions 2.70 and 2.71 from Apelon. Since we already wanted to delete and reload the previous version of LOINC, we are going to use these versions as a test for OCL source versioning. Versions 2.70 and 2.71 will be created and later validated.

[jamlung-ri]

LOINC 2.70 has been loaded into OCL Staging and validated using the script. There were a coupel of small issues that I am working with Jess, but it mostly went successfully, and very quickly too.

Issues from diff file (because they had a "/" character in the ID):

{"type": "Concept", "id": "PANEL.DRUG/TOX", "concept_class": "none", "datatype": "string", "extras": {"Code in Source": "PANEL.DRUG/TOX"}, "retired": true, "source": "LOINC", "owner_type": "Organization", "owner": "Regenstrief-Institute", "names": [{"locale": "en", "locale_preferred": true, "name": "Drug Level Toxicology order set", "name_type": "Fully Specified"}]},
{"type": "Concept", "id": "DRUG/TOX", "concept_class": "none", "datatype": "string", "extras": {"Code in Source": "DRUG/TOX"}, "retired": true, "source": "LOINC", "owner_type": "Organization", "owner": "Regenstrief-Institute", "names": [{"locale": "en", "locale_preferred": true, "name": "Drug levels & Toxicology", "name_type": "Fully Specified"}]},
{"type": "Concept", "id": "PANEL.HEM/BC", "concept_class": "none", "datatype": "string", "extras": {"Code in Source": "PANEL.HEM/BC"}, "retired": true, "source": "LOINC", "owner_type": "Organization", "owner": "Regenstrief-Institute", "names": [{"locale": "en", "locale_preferred": true, "name": "Hematology & blood count order set", "name_type": "Fully Specified"}]},
{"type": "Concept", "id": "HEM/BC", "concept_class": "none", "datatype": "string", "extras": {"Code in Source": "HEM/BC"}, "retired": true, "source": "LOINC", "owner_type": "Organization", "owner": "Regenstrief-Institute", "names": [{"locale": "en", "locale_preferred": true, "name": "Hematology (coagulation) differential count", "name_type": "Fully Specified"}]}

[jamlung-ri]

Issues were fixed, and the content has been mostly loaded into Staging, although I am delayed on testing it since Staging is struggling with large sources at the moment.

[jamlung-ri]

LOINC 2.71 seems to have some issues:

• There are multiple duplicate concepts, which appears to have happened when multiple versions were created for a resource and many of them are marked as "latest=true" (import issue?)
• There were some additional mappings in 2.71 that seemed like they were present in 2.70 but were not present in the 2.71 import file (content issue). I can take these up with Apelon.

Duplicate Concept List:

ERROR: OCL has more than one concept with id "LP73184-1" ERROR: OCL has more than one concept with id "LP73184-1"
ERROR: OCL has more than one concept with id "LP73184-1"
ERROR: OCL has more than one concept with id "LP73184-1"
ERROR: OCL has more than one concept with id "LOINC_COMPONENT" ERROR: OCL has more than one concept with id "LP248771-0"
ERROR: OCL has more than one concept with id "LOINC_COMPONENT" ERROR: OCL has more than one concept with id "LOINC_CLASS" ERROR: OCL has more than one concept with id "LOINC_CLASS" ERROR: OCL has more than one concept with id "LOINC_COMPONENT" ERROR: OCL has more than one concept with id "LOINC_COMPONENT" ERROR: OCL has more than one concept with id "LP57347-4" ERROR: OCL has more than one concept with id "LP57347-4" ERROR: OCL has more than one concept with id "LP57347-4" ERROR: OCL has more than one concept with id "LP57347-4" ERROR: OCL has more than one concept with id "LP72124-8" ERROR: OCL has more than one concept with id "PANEL.HEM/BC" ERROR: OCL has more than one concept with id "HEM/BC" ERROR: OCL has more than one concept with id "DRUG/TOX"

[snyaggarwal]

I will take a look at this data. There was a bug sometime back that caused this, which is fixed now. I will fix this data.

[snyaggarwal]

@jamlung-ri This should be good now.

[jamlung-ri]

Things are looking good in LOINC! Next step is to inform Jess at Apelon about the extra mappings. Otherwise, LOINC is in really good shape at the moment.

[jamlung-ri]

Next step on this is to talk with the LOINC team, where we can walk them through LOINC in OCL Staging. We will want a sort of demonstration of how countries would be using this content.

[jamlung-ri]

Things are looking good in LOINC! Next step is to inform Jess at Apelon about the extra mappings. Otherwise, LOINC is in really good shape at the moment.

Update: The extra mappings have been retired, and Jess has been informed about them. Otherwise, LOINC 2.70 and 2.71 are done in Staging.