Page tree
Skip to end of metadata
Go to start of metadata

Terminology owner/maintenance organisation

Name, contact details, website

Maintaining Organization – Canada Health Infoway

Website: https://infoway-inforoute.ca/en/

Toronto Office

150 King Street West, Suite 1300 Toronto, Ontario M5H 1J9map of location
Tel.: (416) 979-4606
Toll Free: 1-888-733-6462

Formal name of the code system

pan-Canadian LOINC Observation Code Database

Short name or abbreviation of the code system name

pCLOCD
Technical identifier/s for the code system 

OID: 2.16.840.1.113883.2.20.5.1
Canonical URL: https://fhir.infoway-inforoute.ca/CodeSystem/pCLOCD
URN:

Scope/domain statement for the code system

(Official or from HTA)

LOINC® is the largest reference terminology used for Laboratory and Clinical observations in Canada today. The pan-Canadian LOINC Observation Code Database (pCLOCD) is a Canadian constraint of the larger LOINC terminology and includes example pan-Canadian names for jurisdictional lab viewers and recommended units of measure for use in Canada. The core LOINC components of the pCLOCD are translated to Canadian French. pCLOCD releases contains codes that are specific to use in Canada.

Link to information about the code system - including how to obtain the content

https://infoscribe.infoway-inforoute.ca/display/pCLD/General+Release+Information

Note: pCLOCD on January 31 and July 31 of each year. Questions and concerns to the current version of the pCLOCD should be made via the Infoway Infodesk: standards@infoway-inforoute.ca.

Arrangement or agreements with HL7 for use of content

Regenstrief Terms of Use - https://loinc.org/license/
Version management - timing and identification of versions

The pCLOCD standards is published twice a year. Each version of pCLOCD is distinguished by its unique release number and the LOINC version of the change that is reviewed and incorporated into the pCLOCD.


Release number formatting holds key information about the data. All Releases for all Specification Types will be identified by a unique Release Identifier using the following scheme from the Product Release Management Policies:


Rxx.yy.zz (ER)_LOINCn where:

  • xx – is the Major Number for a release. This will only change due to Major Change in functionality or format.
  • yy – is the Minor Number for a release. Each full release, if it does not cause a change in the Major number , will result in the Minor Number of the release being incremented.
  • zz – reflects the Delta number, incremented for each subsequent Delta Release applied to a Full release. When a new Full Release is published, the subsequent Delta Number is reset to “00”. 
  • (ER) is only added to the end of a Release Identifier when the release is published for External Review.
  • LOINCn – is the latest LOINC version update number published by Regenstrief.


The format of the release number is RXX.YY.ZZ. E.g. R05.11.00_2.67

IP Information and Licensing Information

Infoway manages access to the CodeSystem by users accepting the following agreement(s):


https://infocentral.infoway-inforoute.ca/en/standards/standards-accesss 


https://infocentral.infoway-inforoute.ca/en/about/tou/pclocd-terms

HL7 users of this information - which HL7 products use this link (if known)

N/A

Process to request content change

For information on requesting new codes, pleases refer to information from Canada Health Infoway here.

email: standards@infoway-inforoute.ca

Other useful Information

Core LOINC components of the pCLOCD are translated to Canadian French.


pCLOCD uses the UCUM standard for measurement units.

Information current as at (date)

2020/06/09
  • No labels

11 Comments

  1. Ted Klein Caroline Macumber  Jessica Bota  we created the pCLOCD stub. Please advise next steps. Thank you

    1. Joel, I do not see the Proposal with the created stub.   Which UP Jira project ticket ID is it?

      1. Ted Klein , he means this page when he says stub, i think. Not a UTG resource stub.

        1. We have to be more careful about precision in noun usage to avoid confusion.

      2. Sorry Ted, Carol is correct - by stub I meant this page. 

  2. Joel Francis, looks good, thank you so much! I've added it to the External Terminolgogies - Information page

    Julie James , I'll add to the agenda for tomorrow's HTA call for official approval

    Jessica Bota , can you open a ticket in UTG to create/update (if it exists already) an external code system entry for pCLOCD

    Reuben Daniels , can you lead the creation of a "Using pCLOCD with FHIR" page, should be an interesting one as I beleive it is represented as a Code System Supplement to LOINC

  3. Thanks Caroline Macumber  and Ted Klein  I will try to open a UTG Ticket and create an external CodeSystem. 

    Kelly Davison

  4. Jessica Bota were you able to open a ticket for us?

    1. Hi Joel Francis, I am meeting with Ted shortly to make sure I populate the ticket correctly. Will be in touch soon with the ticket number. 

      1. Joel Francis, the ticket has been created:  UP-70 - Getting issue details... STATUS

        I am under the impressing you will be completing the content changes. If you have questions, please let us know. The documentation (see submitter documentation) is here UTG Tooling and Proposal Documentation

  5. Thanks Jess Jessica BotaKelly Davison and I will take stab at it today. Thank you again!