Closed matthewjoss closed 7 years ago
I edited the documentation and added a note to the transform informing others to modify this term 'LOINC:' to match whatever term your individual site uses.
Jeff said: For #3... This is tricky. I wrote it to support local children of LOINC codes, but not the 1:1 mapping case with different local codes. For now @GriffinWeber 's solution is good and we should all check our sites' reports to make sure this is not an issue for them. Maybe @vijayrag could ask the sites what their local lab basecodes are?
Griffin:
The PCORNetLabResultCM procedure queries for a c_basecode like 'LOINC:%'. At BIDMC, our c_basecode prefix is 'LAB|LOINC:%'. I fixed this by modifying the stored procedure. In the future it would be better if it didn't rely on a specific c_basecode, since that can vary by site.