Orderable and Observable LOINC Terms

The LOINC release specifies whether each LOINC term is Orderable, Observable, or Both in the ORDER_OBS column of the Loinc.csv file. This classification helps healthcare systems determine which terms can be used for test orders versus those that are strictly for observations. In the LOINC Ontology, this information is provided in two simple type reference sets.

Reference Sets for Orderable and Observables

In SNOMED CT, subsets are represented using simple reference sets (Refsets), allowing implementers to filter and retrieve LOINC terms based on their orderability or observability. This structured approach facilitates the integration of LOINC terminology within SNOMED CT implementations.

For example, implementers can query:

• “Show all LOINC terms that are Orderable.”

• “Show all LOINC terms that are Observable.”

To support this, the LOINC Ontology includes two distinct reference sets:

• 635121010000106 | LOINC Observation Reference Set | – Contains LOINC terms classified as Observable.

• 635111010000100 | LOINC Orderable Reference Set |– Contains LOINC terms classified as Orderable.

The reference sets are distributed in a file named according to SNOMED CT conventions: der2_Refset_SimpleRefsetSnapshot_INT_20250321.txt

Example

Each row in this file corresponds to a LOINC term and includes a refsetId that determines whether the term belongs to the Orderable or Observable subset.

Some LOINC terms are classified as both Orderable and Observable. In such cases, the term will appear in both reference sets, ensuring that it is available in queries for either category.

LOINC Observation Reference Set (first 4 rows, total 24829)

id	effectiveTime	active	moduleId	refsetId	referencedComponentId
16864455-3679-4543-a360-1f0b5f5dca1d	20250321	1	11010000107	635121010000106	226581010000109
faf3eff6-5c15-4b9d-ae72-953d06a80391	20250321	1	11010000107	635121010000106	189881010000107
781fbd14-8883-456a-a324-3d56584edf8e	20250321	1	11010000107	635121010000106	179681010000102
8286c793-0c9b-434e-a4c4-f3ca1d79d67a	20250321	1	11010000107	635121010000106	200271010000103

LOINC Orderable Reference Set (first 4 rows, total 34791)

id	effectiveTime	active	moduleId	refsetId	referencedComponentId
565a60d6-7ee2-4699-a62a-3b1228761693	20250321	1	11010000107	635111010000100	189881010000107
ccabfb4b-2353-4a8e-bdd7-2e75d9759e62	20250321	1	11010000107	635111010000100	200271010000103
699290e8-15bc-4895-ad9b-fda371465526	20250321	1	11010000107	635111010000100	617571010000101
33a2cb27-47fa-4751-9f6e-8e580cba17f5	20250321	1	11010000107	635111010000100	189931010000103

View Members in the Browser

The counts for the Observation and Orderable Reference Sets can be seen in the browser, in the left-hand panel, and clicking on the "Refset" tab:

Clicking on either of these concepts will bring them up in the right-hand panel:

Note that the concept that represents the reference set does not have any children (these would be different, more specialised reference sets if they existed), but the reference set does have members. These can be listed by clicking on the members tab:

Now we can also obtain this list, or even something more interesting, by going into the "Expression Constraint Queries" tab. For this example, we're going to look for the intersection of these two sets. That is, the LOINC concepts which are BOTH orderable AND observables. The ECL for this query is: ^ 635121010000106 |LOINC Observation Reference Set| AND ^ 635111010000100 |LOINC Orderable Reference Set|

And here we see that, of the 34787 codes used for observation and the 24826 used for ordering, 24279 can be used for both. So the vast majority.

Note that the counts here refer purely to those LOINC concepts that successfully translated into The LOINC Ontology at time of publication. The full LOINC release in it's original format contains additional codes for each.

Provide Feedback