pan-Canadian LOINC Observation Code Database (pCLOCD) Terms of Use:
https://infocentral.infoway-inforoute.ca/en/about/tou/pclocd-terms
LOINC and RELMA Terms of Use:
https://infocentral.infoway-inforoute.ca/en/about/tou/loinc-terms
Maintenance R05.12.00
July, 2020
Version Tracking
The version table should be updated each time the document receives significant edits and is passed to an audience other than close participants to an editing process.
Release | Author(s) | Change Description | Date |
|---|---|---|---|
| 1.0 | First Published Draft Version | 2008-Mar-03 | |
1.1 | Lorie Carey | Changes based on draft feedback | 2008-Jul-02 |
1.2 | Lorie Carey | Changes resulting from PRM White Paper | 2008-Oct-06 |
02.03.00 | Lorie Carey | Updated to include processes to support French translations | 2009-Apr-14 |
04.00.00 | Lorie Carey | Update and revise document | 2012-July-23 |
04.01.00 | Lorie Carey | Published version | 2012-July-31 |
04.01.01 | Lorie Carey | URL edits | 2012-Aug-20 |
04.02.00 | Lorie Carey | Changes to reflect new RFC processes | 2014-Jan-29 |
05.00.00 | Lorie Carey | Changes to reflect new pCLOCD Terms of Use, added hyperlink to new LOINC codes | 2014-Jul-29 |
05.01.00 | Lorie Carey | Updated | 2015-Jan-28 |
05.07.00 | Linda Monico | Updated | 2017-July-28 |
05.12.00 | Linda Monico | Updated | 2020-Jul |
pan-Canadian LOINC Observation Code Database (pCLOCD) Terms of Use
Copyright Notice and License
Canada Health Infoway Inc. (Infoway) has created the pan-Canadian LOINC® Observation Code Database (pCLOCD) from LOINC® to address local requirements in Canada. Infoway maintains the copyright on these localized additions.
The LOINC® codes, LOINC® Table (regardless of format), LOINC® Release Notes, LOINC® Changes File, and LOINC® Users' Guide are copyright © 1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee. All rights reserved.
LOINC® is a registered United States trademark of Regenstrief Institute, Inc. Regenstrief Institute, Inc. and, as applicable, the LOINC Committee reserve all rights not expressly granted herein.
Permission is hereby granted to a user who agrees to these Terms of Use (User), without payment of license fees or royalties, to use, copy, or distribute the pCLOCD (in all formats in which it is distributed by Infoway) for any commercial or non-commercial purpose, subject to the following terms and conditions:
...
- For LOINC codes, one of the following LOINC display names from the LOINC Table must be included:
- The fully-specified name, which includes the information from the COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, and METHOD_TYP fields;
- The LOINC short name (from the SHORTNAME field);
- The LOING long common name (from the LONG_COMMON_NAME field); or,
- The LOINC Display name (from the DisplayName field).
- For LOINC identifiers other than LOINC codes, the primary corresponding display name (e.g. LOINC Answer List Name, LOINC Answer String Display Text, LOINC Part Name, LOINC Group Name) must be included.
...
Publication Date: September 2021
LOINC and RELMA Terms of Use
The pan-Canadian LOINC Observation Code Database (pCLOCD) contains a portion of the LOINC® table, LOINC panels and forms file, and/or LOINC hierarchies file, or is derived from one or more of the foregoing, subject to a license from Regenstrief Institute, Inc. Your use of the LOINC table, LOINC codes, LOINC panels and forms file, and LOINC hierarchies file also is subject to this license. The current complete LOINC table, LOINC Users' Guide, LOINC panels and forms file, and LOINC hierarchies file are available for download here: http://loinc.org/. The LOINC table and LOINC codes are copyright © 1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee.
1. General pCLOCD Information
...
InfoCentral will also contain the previously published versions for reference purposes or restorations, if older versions are required, please contact us at standards@infoway-inforoute.ca.
3. Basic Utilization Information
...
The pCLOCD “Result Value Type” attributes designate the recommended or, as outlined below, the required reporting data format to be selected. The following table summarizes the possible Result Value Type values:
Result Value Type | Description / Example | Result Value Communication |
|---|---|---|
| Text | Free-form textual information. |
Example(s): 1+, 2+ “Positive” “Not found” | The result value should be communicated using a data type that reflects textual / string data. |
Numeric | A real number. |
Example(s): “5” “5.234” | The result value should be communicated using a data type that reflects numeric data. |
Text or Numeric | Either Text or Numeric could be applied. |
Example(s): ‘”5” “<5.0” | The result value should be communicated using a data type that reflects either numeric data or textual / string data. |
Date/Time | A date and/or time. |
Example(s): “19960523” “199605121000” “1201” | The result value should be communicated using a data type that reflects date / time data. |
Coded | A coded response: |
“112283007” (Escherichia coli) | The result value should be communicated using a data type that reflects coded data. If coded data is transmitted it should be drawn from SNOMED CT®. | |
Coded or Text | Either Code or Text could be applied. | The result value should be communicated using a data type that reflects either coded data or textual / string data. |
Table 1 pan-Canadian LOINC Observation Code Database Attribute
...
There are result observations in classes other than Microbiology and Anatomic Pathology where interpretations are reported. These “interpretation” types of records are characterized by a LOINC Property of “IMP” and will allow for coded and text result values. The expected result value is differentiated only by the LOINC Scale. The observation records in the pCLOCD that should be used for text result values will have the LOINC scale as NAR (Narrative). The records that should be used for coded text result values will have the LOINC scale as NOM (Nominal). Examples include:
LOINC Code | Pan-Canadian Name | Result Value Type | LOINC Property | LOINC Scale |
|---|---|---|---|---|
| 41274-2 | Alpha-1-Fetoprotein Interpretation | Coded | IMP | Nom |
49246-2 | Alpha-1-Fetoprotein Interpretation | Text | IMP | Nar |
3.4 Pan-Canadian Name
The natural language test name is the name that is most often referred to for ordering and reporting a laboratory test/observation. The structure of LOINC sufficiently demonstrates the difficulty to fully identify tests using test names that are both unambiguous and yet easy to read. Many LOINC attributes are abbreviated for database use and not easily understandable; therefore, translations for the LOINC attributes have been included in the pCLOCD and used to automatically generate the pan-Canadian Name.
...
Pan-Canadian Component Name; LOINC System; LOINC Timing; LOINC Method
The LOINC System, Timing and Method are all optional but, if included, must be in the order provided above.
...
Requests for change (RFC) can be made by anyone with an Infoway account. Requests must be made using the Infoway's Request Management System tool (InfoRMS) tool. The tool utilizes the users Infoway Account credentials to log in and is located at this URL: To use this tool, a Infoway account with access to InfoRMS is required. Once your access is confirmed, you can login at the following URL: https://informs.infoway-inforoute.ca/projects/PCL
The tool provides the ability to log an RFC by single entry or by using a template for batch requests. The pCLOCD template should be downloaded and completed each time there is a new request to ensure the For batch requests, download most current version of the template is usedpCLOCD RFC template on InfoRMS. The template is an Excel file that contains multiple tabs. The “How to Read” tab outlines the color code used for column headings and also clearly describes the various columns and tabs. Users should be familiar with the “How to Read” tab before utilizing any other tab. Once completed it can be uploaded, this will automatically generate tickets for each RFC.
When a request RFC batch or single ticket is received, it will be evaluated as to its completeness, accuracy, and priority level. Users will be notified of incomplete or inaccurate requests using the workflow status in the tool. An acknowledgement of the request RFC is provided each time a request is submitted. For more information on InfoRMS, please review the information provided on InfoCentral at this URL:https://infocentral.infoway-inforoute.ca/en/resources/docs/standards/implementation-pclocd/maintenance-p/1187-infoway-rfc-process-for-loinc-and-pclocd-contentis submitted.
6.1 Requesting a New Code
...
The unique jurisdictional identifier can be used until a LOINC or XCA code is returned. Jurisdictions that intend to use their temporary jurisdictional code must plan appropriate processes for ensuring that all receivers of the data (within and outside of the jurisdiction) can interpret the data. More information on pre-adopting codes can be found here.
All requests for change will be logged and tracked. An analysis will be undertaken that may result in further communication with the requestor. If the request is determined to be a valid request for a new record, it will be assigned a pan-Canadian code using the following format:
- “XCAnnnnn-n” where,
- “XCA” is the permanent first three characters;
- “nnnnn” is a five digit sequential number that will increment by one for each new observation code; and
- “-n” represents the check digit created from the five digits using the Mod 10 algorithm provided in Appendix A.
...
The pan-Canadian code will be the unique identifier that is used to submit the code to Regenstrief. The new XCA/ LOINC code will be sent back to the original requestor as soon as possible. The unique temporary jurisdictional identifier can be used until the Infoway Standards Team provides the LOINC or final XCA code. Jurisdictions that plan on using their temporary jurisdictional code must plan appropriate processes for ensuring that all receivers of the data (within and outside of the jurisdiction) can interpret the data.
...
Updates from Regenstrief will be reviewed and incorporated into the pCLOCD. New versions of the pCLOCD will be published twice a year, once in approximately January March and July September (typically one month after the Regenstrief file is published).
...
The Infoway Standards Team publishes an update to the standard twice a year, once in approximately January March and July September (typically one month following the Regenstrief publication). Timely submission of new codes to the Infoway Standards Team from any jurisdiction will be included in these updates. Regenstrief publishes an update to the LOINC standard twice a year, approximately in June February and DecemberAugust. The changes from these publications will be analyzed and reflected in the published Canadian update in both official languages. Release cycles for pCLOCD can be found here.
The ongoing process of creating new codes from jurisdictional requests will not be published outside of the scheduled dates as outlined above, except within the InfoRMS RFC. Whether jurisdictions plan on using their temporary jurisdictional code or the new LOINC code, they must understand that other jurisdictions may not have those new codes in their database until the next release of the standard and so must plan appropriate processes for ensuring that all receivers of the data (within and outside of the jurisdiction) can interpret the data.
...
https://infocentral.infoway-inforoute.ca/en/collaboration/communities/health-terminologies
All inquiries can be emailed to the Infoway Infodesk: [email protected]
Contact Us for inquiries.
12. Mod 10 Check Digit Algorithm
The algorithm for calculating a Mod 10 check digit for a LOINC code is as follows:
Instructions | Example Using the number: 12345 |
|---|---|
1) Assign positions to the digits, from right to left | 1st = 5 2nd = 4 3rd = 3 4th = 2 5th = 1 |
2) Take the odd digit positions counting from the right (1st, 3rd, 5th, etc.) | 531 |
3) Multiply by 2 | 1062 |
4) Take the even digit positions starting from the right (2nd, 4th, etc.) | 42 |
5) Append (4) to the front of the results of (3) | 421062 |
6) Add the digits of (5) together | 4+2+1+0+6+2 = 15 |
7) Find the next highest multiple of 10 | 20 |
8) Subtract (6) from (7) | 20 - 15 = 5 |
Thus, 5 is the Mod 10 check digit for 12345 | 12345-5 |
Table 2 Mod-10 Algorithm
| Table of Contents |
|---|