...
UCUM provides a single coding system for units that is complete, free of all ambiguities, and that assigns to each defined unit a concise semantics [1](ref.: http://aurora.regenstrief.org/~ucum/ucum.html). It consists of a basic set of symbols for units, called atomic unit symbols or unit atoms, and multiplier prefixes. It also consists of an expression syntax by which these symbols can be combined to yield valid unit expressions (with no spaces between atomic units, prefixes, and annotations).
...
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.
6.2 Requesting a Change or Correction
Requests to correct or change an existing code can be made using InfoRMS.
...
Other Jurisdictions can also begin using the new LOINC code as published in the Completed RFC in InfoRMS.
8. Understanding Changes to the pCLOCD
When implementing the changes that occur in a new release of the pCLOCD, several factors should be taken into consideration. Changes made to each record are based on the change process that was developed by Regenstrief. The Infoway Standards Team utilizes the same change nomenclature and change principles.
...
- Change Major – this includes system (specimen) changes, methodology changes and property changes as well as changes and/or corrections to the Canadian Component Name. These changes may impact mapping decisions made previously and may change the intent and use of the code; they need to be reviewed carefully.
- Change Minor – this includes subtle corrections to the Canadian Component Name or changes to the LOINC class. These changes will have less of an impact on previously mapped tests, but should be reviewed nonetheless. They will not typically impact the intent of the code.
- Change Name – this includes changes to the LOINC component name which ultimately affects the Canadian Component name and the Canadian Name. These changes may impact mapping decisions made previously and may change the intent and use of the code; they need to be reviewed carefully.
8.3 New Codes
When the update is published, it will include some new codes. These new codes will be one of two types.
...
- V Name Changes
The pCLOCD includes an example viewer name for each active code that is published. The viewer name is based on the pan-Canadian Component Name and follows the Guiding Principles and Rules. Current maintenance practises allow for corrections and changes that result from changes to the core LOINC components to be reflected in the example viewer name. When the only change to a code is in the viewer name, the change type is identified as V Name. - No Change
The pCLOCD tracks changes to both languages, and periodically, a change will be made to either the English or French only version and there has been no impact to the other language. In those cases, the appropriate language change type will be indicated as “No Change”.
9. Implementing a New Release
Jurisdictions that have not previously used the pCLOCD may begin to use the new version immediately.
...
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.
11. Additional Artifacts and Support
Readers should recognize that new codes will be added from time to time to accommodate the requirements of Canada's health jurisdictions. As such the aggregate list can never be seen as "complete" but rather as a framework through which data interchange can be enabled by recognizing and documenting applicable order and/or result observation codes.
...
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
...