The pan-Canadian LOINC Observation Code Database (pCLOCD) standard is published as an Excel file that contains ten tabs. The four tabs that were edited in this release include Infoway Terms of Use, LOINC® Copyright, Nomenclature and the Change Log. This release contains the pCLOCD March 2024 version R05.20.00_2.77 and interim changes applied, desribed in detail below.
This is an updated pCLOCD release since March 2024. This pCLOCD interim release reflects significant data quality enhancements from our new Terminology Server project. This interim pCLOCD release is identified as: pCLOCD R05.20.01.00_2.77 and contains 155 edits to pCLOCD records.
It is helpful to review the general pCLOCD release information alongside this pCLOCD release note.
Implementing the Terminology Server has significantly enhanced pCLOCD. Previously, pCLOCD has only existed as a denormalized database that presented some drawbacks, such as increased data redundancy and inconsistency, leading to data quality issues and management challenges.
As part of the Terminology Server project, pCLOCD has been transformed into a standardised FHIR form. Building a terminology as a FHIR (Fast Healthcare Interoperability Resources) Code System requires the normalization of data to ensure consistency, interoperability, and accuracy in healthcare information exchange. Data normalization involves standardizing the format and structure of data elements to align with established coding standards and terminologies, such as SNOMED CT, LOINC, or ICD.
Normalization is beneficial for several reasons, including:
- Interoperability: Normalized data allows different healthcare systems and applications to understand and use the information consistently, facilitating seamless data exchange and integration.
- Accuracy: By adhering to standardized codes and terminologies, the risk of misinterpretation and errors in data is minimized, ensuring accurate representation of clinical concepts.
- Efficiency: Normalized data supports automated processing and reduces the need for manual intervention, thus improving the efficiency of data management and retrieval.
- Quality: Standardization enhances the quality of data, making it reliable and valuable for clinical decision-making, research, and reporting.
- Compliance: Adhering to established standards and norms ensures compliance with regulatory requirements and best practices in healthcare information management.
Thus, normalization is a critical step in building a robust and effective FHIR Code System, enabling the consistent use of terminologies across different healthcare settings and applications.
1. There are a total of 39,797 records this release. No new records have been added since the previously released version.
2. 38,921 records are translated to Canadian French. No new records have been translated since the previously release version the last version. Note: Terms that are marked ‘Review Draft’ should be reviewed before they are used as the translation has not been previously published. Terms that are marked as ‘Complete’ have been previously published.
3. 96 records were modified in English for this release and are marked as R05.20.01_2.77
a. 35 records are of the change type Minor for English changes.
b. 61 corrections was made to Viewer Name.
5. 100 records were modified in French for this release and are marked as R05.20.01_2.77
a. 33 records are of the change type Major for the French translation.
b. 21 records are of the change type Minor for the French translation.
c. 46 records corrections were made to Viewer Names
7. Both languages contain a number of codes that only have changes in the other language; those are identified as ‘No Change’.
Of specific interest in this release, current implementers may want to review these changes:
There are edits that have been applied to pCLOCD not identified with the Interim Release Identifier. These edits ensure consistency and accuracy and include:
- Removal of whitespaces
- Corrections to pCLOCD attributes to align with pCLOCD editorial guidelines and rules. These rules are found in Section 3.1 of pCLOCD Maintenance Guide.
- Corrections to pCLOCD/LOINC content to align with LOINC TALL Man Lettering in Names. More documentation also available in section 2.1.4 Case insensitivity of LOINC user guide.
Questions and feedback welcome, contact us