Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

05.15.00Linda MonicoUpdated2021-Sep


pan-Canadian LOINC Observation Code Database (pCLOCD) Terms of Use

...

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.

...