V2.80 will not import

v2.80 will not import to the server. Any feedback is appreciated. Thanks.

Hello Temeka,

Can you please provide more information? How are you attempting to import? What is the system/database into which you are importing? Do you have any associated error messages?

Hopefully these answers will help us diagnose the issue.

I am uploading the v 2.80 files from the website. Here’s s screenshot of what is in the file.

I work for Trubridge (CPSI). We upload the latest in order for the LOINC code usage for lab reportable tests.

That file has to be uploaded in our dx’s table in our live server.

I cannot add the screen shot of the files, but it is the mapping, loinc tables, and more. It is the file I save to my desktop, from the loinc.org website for the v2.80.

No errors appear; it just does not upload from what I downloaded from the website to our live server.

@temeka Do you know the last successful LOINC import you did, i.e., which version number? We are trying to understand if there were any breaking changes since your last import.

Yes, it was the very last one prior to v2.80. I think it was v 2.70 or v2.73. That was two years ago in 2023.

Without knowing the details of your system, it is likely there were structural changes to the LOINC table which prevented the import. I recommend reviewing the Release Notes Archive for changes since your last import.

We recommend updating your systems within 90 days of each LOINC release. This will help address these types of breaking changes.

I am not sure if that would be feasible for a new install. If all of those releases have past, site would have to start from the earliest and then upload the latest? I just want to be sure I understand.

Example: If the site installs two years from now, they will have to go back and upload all of the earliest version, then the most recent one? Am I understanding your statement?

Sorry for the confusion. I am not suggesting importing each individual release from the last successful update. That would be unnecessary. Rather, I would review each of the recent release notes documents to see what has changed, if anything, in the file structure. I expect there was a structural change that is causing the file(s) to not import. For instance, you can see in release notes for v2.77 that the COMMON_SI_TEST_RANK field has been deleted.

If you do identify the cause, please provide an update so that others may find the solution.