LOINC Terminology Service using HL7® FHIR®

Revised 2024-10-29

Definitions
Versioning and Translations
CodeSystem
ValueSet
ConceptMap
Questionnaire
Known Issues

Access LOINC's terminology content through the HL7® FHIR® API

You can access current LOINC content programmatically. Our server uses the terminology services defined by HL7's FHIR standard.

FHIR version: R4

LOINC version: 2.78
Additional versions available via explicit request: 2.69, 2.70, 2.71, 2.72, 2.73, 2.74, 2.75*, 2.76, 2.77 More Info

The service base URL is:

https://fhir.loinc.org

*Version 2.75 contains errors and was replaced by version 2.76. We do not recommend accessing this version and it may be removed from this service in the future.

BETA Status

LOINC's FHIR services have a BETA maturity status meaning that aspects of the implementation may change without notice and/or the services may not be be available 100% of the time. The is partly due to the fact that the FHIR standard itself is evolving. For these reasons, we do not recommend using this API in a production setting. This Beta label is not to be confused with our content versioning designations. With the exception of LOINC Groups and Consumer Names, all content available from LOINC's terminology service is production level and current with the latest LOINC release. At present, no pre-release terms are available from this API.

You can visit our dedicated User Forum to discuss this server. If you notice something not working as expected, please let us know.

Definitions

This primer will familiarize you on FHIR terminology concepts and how they are used within LOINC's implementation. We will also let you know what you need to get started with this LOINC API and provided examples.

FHIR resource

A FHIR resource is an individual specification for how to represent a particular concept related to healthcare. Currently more than 100 FHIR resources have been defined, including clinical (Medication, Immunization, Diagnosis), people or organizations (Patient, Provider), financial (Claim, Account), security (Provenance, AuditEvent), and terminology (CodeSystem, ValueSet).

Select FHIR terminology resources

CodeSystem: Describes key elements of a terminology (i.e., code system).

ValueSet: Identifies a set of codes from one or more code systems that is used for a specific purpose. LOINC Answer lists and LOINC Groups are examples of value sets provided by the LOINC FHIR terminology server.

ConceptMap: Defines a mapping between one or more concepts in one code system to one or more concepts in another code system. LOINC Part to SNOMED CT concept and LOINC term to RadLex Playbook concept are examples of concept maps.

Operation

An operation is a command that specifies an action performed on a resource.

Select FHIR terminology operations/parameters

$lookup: Returns information about a specific resource, such as a concept (e.g., LOINC term or Part), ValueSet (e.g., LOINC Answer list), or ConceptMap.

$expand: Returns the set of codes included in a ValueSet.

$validate-code: Checks to see if a specific code is in a given ValueSet.

$translate: Use with the ConceptMap resource to find all of the concepts a particular source concept is mapped to.

property: Specific information about a resource. There are general properties defined across code systems (e.g., ), as well as specific properties defined within the LOINC code system (e.g., VersionFirstReleased, COMPONENT, ORDER_OBS, CLASSTYPE). Use with $lookup to return only the information related to that property.

designation: Designations within FHIR are described as additional representations of a given concept. They are used in the LOINC TS to provide non-English translations and alternate names.

You need a LOINC login

All requests to LOINC's FHIR terminology server require a LOINC username and password. If you do not already have a LOINC account, you may sign up for free.

Your LOINC account also enables you to download LOINC files, use SearchLOINC, and participate in our Forum.

Tips on using examples

All provided examples will work within a browser. You will need to provide your login information upon the first request of a session. We also suggest using the free Postman software as an API client.

Each example includes a button so you may copy the URL and paste it into a browser window or within a Postman GET request. (As with the browser, you will need to provide your credentials using Postman’s Basic Auth option.)

Versioning of resources

As of April 2022, LOINC's Terminology Service supports previous versions of CodeSystem, ValueSet, and ConceptMap resources. Below you will see how to reference a particular LOINC version as part of requests to these three API endpoints. A request which does not specify a version will always return the current version of the terminology. Presently, LOINC versions 2.69 through current are available.

Translations as designations

LOINC's Linguistic Variants are provided as designations. Available translations are automatically returned on CodeSystem $lookup and ValueSet $expand operations. This functionality was introduced with the April 2022 TS update.

In addition to translations, designations support alternate names for concepts defined in LOINC. Consumer Names and Short Names are now available as designations. (See this important disclaimer regarding the maturity and use of Consumer Names.)

CodeSystem

The CodeSystem resource specifies a set of codes drawn from one or more code systems. Code systems define which codes (symbols and/or expressions) exist, and how they are understood.

We have created a canonical definition of how to represent LOINC as a CodeSystem in FHIR that extends its representation to include more LOINC-specific features. LOINC's CodeSystem definition is available for download available at https://loinc.org/fhir/loinc.xml (sourced by this repository on GitHub). With the LOINC 2.68 release, we expanded the LOINC-specific properties available in our FHIR representation to include those that are published in the LoincPartLink_supplementary file, which is available in the Part file.

NOTE Over time, we do anticipate updating this canonical definition in collaboration with the FHIR and LOINC community.

The following are identifiers within the LOINC code system. All are included within the LOINC CodeSystem resource.

All LOINC fields are now represented as Properties

NEW As of the March 2023 TS update, all LOINC fields now exist as CodeSystem Properties within this terminology service. Previously only a subset of fields from the LOINC table structure were defined as Properties. This brings parity between the downloadable version of LOINC and the content available from this API.

You can see this quick reference of all CodeSystem Property values, including specialty ones for Radiology and Document Ontology. Alternatively, you can also refer to LOINC's CodeSystem definition, loinc.xml, included in our downloadable distribution or on GitHub.

Get the specialized properties available for LOINC as a CodeSystem in FHIR

Use the canonical URI for LOINC, http://loinc.org, to retrieve all the information about LOINC as a CodeSystem in FHIR through this request:

https://fhir.loinc.org/CodeSystem/?url=http://loinc.org

The server provides the following sample response, represented in JSON:

{
  "resourceType": "Bundle",
  "id": "cf47d890-3db2-4cf9-be0a-030d97fb06e0",
  "meta": {
    "lastUpdated": "2024-08-06T20:51:56.297+00:00"
  },
  "type": "searchset",
  "total": 11,
  "link": [ {
    "relation": "self",
    "url": "https://fhir.loinc.org/CodeSystem/?_format=json&url=http%3A%2F%2Floinc.org"
  } ],
  "entry": [ {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.78",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.78",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2024-08-06T14:20:52.079+00:00",
        "source": "#vOW1siNqnlKTacAG"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.78",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.77",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.77",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2024-02-27T14:21:54.129+00:00",
        "source": "#jJgpq42phGZQYVUJ"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.77",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2024, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.76",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.76",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2023-09-18T13:12:56.420+00:00",
        "source": "#Iq0oagBKxuwchLET"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.76",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2023, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.75",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.75",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2023-08-15T12:13:34.574+00:00",
        "source": "#jbZx93niroRM29l2"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.75",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2023, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.74",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.74",
      "meta": {
        "versionId": "2",
        "lastUpdated": "2023-03-16T18:50:46.576+00:00",
        "source": "#dHmY9SEh0qkjjk6u"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.74",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2023, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.73",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.73",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2022-08-08T12:22:19.084+00:00",
        "source": "#AZS6Rngm9Lxg4rZ1"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.73",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2022, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.72",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.72",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2022-04-11T19:30:02.777+00:00",
        "source": "#oqTccQUQSklOt4mO"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.72",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2022, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.71",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.71",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2022-04-11T19:04:31.865+00:00",
        "source": "#X1BQxN8V2M9KtlnF"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.71",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.70",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.70",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2022-04-11T18:38:49.609+00:00",
        "source": "#1A9GVinO2SrIAv0M"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.70",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc-2.69",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc-2.69",
      "meta": {
        "versionId": "1",
        "lastUpdated": "2022-04-11T17:01:52.685+00:00",
        "source": "#NNzcjosQ50Vo102c"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "version": "2.69",
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright ©1995-2021, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Multiaxial Hierarchy. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Multiaxial Hierarchy",
        "type": "code"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  }, {
    "fullUrl": "https://fhir.loinc.org/CodeSystem/loinc",
    "resource": {
      "resourceType": "CodeSystem",
      "id": "loinc",
      "meta": {
        "versionId": "7",
        "lastUpdated": "2024-08-06T14:22:11.542+00:00",
        "source": "#vOW1siNqnlKTacAG"
      },
      "url": "http://loinc.org",
      "identifier": [ {
        "system": "urn:ietf:rfc:3986",
        "value": "urn:oid:2.16.840.1.113883.6.1"
      } ],
      "name": "LOINC",
      "title": "LOINC Code System",
      "status": "active",
      "experimental": false,
      "publisher": "Regenstrief Institute, Inc.",
      "contact": [ {
        "telecom": [ {
          "system": "url",
          "value": "http://loinc.org"
        } ]
      } ],
      "description": "LOINC is a freely available international standard for tests, measurements, and observations",
      "copyright": "This material contains content from LOINC (http://loinc.org). LOINC is copyright Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.",
      "caseSensitive": false,
      "valueSet": "http://loinc.org/vs",
      "hierarchyMeaning": "is-a",
      "compositional": false,
      "versionNeeded": false,
      "content": "not-present",
      "filter": [ {
        "code": "parent",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Parent selects immediate parent only. For example, the code '79190-5' has the parent 'LP379670-5'",
        "operator": [ "=" ],
        "value": "A Part code"
      }, {
        "code": "child",
        "description": "Allows for the selection of a set of codes based on their appearance in the LOINC Component Hierarchy by System. Child selects immediate children only. For example, the code 'LP379670-5' has the child '79190-5'. Only LOINC Parts have children; LOINC codes do not have any children because they are leaf nodes.",
        "operator": [ "=" ],
        "value": "A comma separated list of Part or LOINC codes"
      }, {
        "code": "copyright",
        "description": "Allows for the inclusion or exclusion of LOINC codes that include 3rd party copyright notices. LOINC = only codes with a sole copyright by Regenstrief. 3rdParty = only codes with a 3rd party copyright in addition to the one from Regenstrief",
        "operator": [ "=" ],
        "value": "LOINC | 3rdParty"
      } ],
      "property": [ {
        "code": "parent",
        "uri": "http://hl7.org/fhir/concept-properties#parent",
        "description": "A parent code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "child",
        "uri": "http://hl7.org/fhir/concept-properties#child",
        "description": "A child code in the Component Hierarchy by System",
        "type": "code"
      }, {
        "code": "COMPONENT",
        "uri": "http://loinc.org/property/COMPONENT",
        "description": "First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge",
        "type": "Coding"
      }, {
        "code": "PROPERTY",
        "uri": "http://loinc.org/property/PROPERTY",
        "description": "Second major axis-property observed: Kind of Property (also called kind of quantity)",
        "type": "Coding"
      }, {
        "code": "TIME_ASPCT",
        "uri": "http://loinc.org/property/TIME_ASPCT",
        "description": "Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)",
        "type": "Coding"
      }, {
        "code": "SYSTEM",
        "uri": "http://loinc.org/property/SYSTEM",
        "description": "Fourth major axis-type of specimen or system: System (Sample) Type",
        "type": "Coding"
      }, {
        "code": "SCALE_TYP",
        "uri": "http://loinc.org/property/SCALE_TYP",
        "description": "Fifth major axis-scale of measurement: Type of Scale",
        "type": "Coding"
      }, {
        "code": "METHOD_TYP",
        "uri": "http://loinc.org/property/METHOD_TYP",
        "description": "Sixth major axis-method of measurement: Type of Method",
        "type": "Coding"
      }, {
        "code": "CLASS",
        "uri": "http://loinc.org/property/CLASS",
        "description": "An arbitrary classification of terms for grouping related observations together",
        "type": "Coding"
      }, {
        "code": "VersionLastChanged",
        "uri": "http://loinc.org/property/VersionLastChanged",
        "description": "The LOINC version number in which the record has last changed. For new records, this field contains the same value as the VersionFirstReleased property.",
        "type": "string"
      }, {
        "code": "CHNG_TYPE",
        "uri": "http://loinc.org/property/CHNG_TYPE",
        "description": "DEL = delete (deprecate); ADD = add; PANEL = addition or removal of child elements or change in the conditionality of child elements in the panel or in sub-panels contained by the panel; NAM = change to Analyte/Component (field #2); MAJ = change to name field other than #2 (#3 - #7); MIN = change to field other than name; UND = undelete",
        "type": "string"
      }, {
        "code": "DefinitionDescription",
        "uri": "http://loinc.org/property/DefinitionDescription",
        "description": "Narrative text that describes the LOINC term taken as a whole (i.e., taking all of the parts of the term together) or relays information specific to the term, such as the context in which the term was requested or its clinical utility.",
        "type": "string"
      }, {
        "code": "STATUS",
        "uri": "http://loinc.org/property/STATUS",
        "description": "Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED",
        "type": "string"
      }, {
        "code": "CONSUMER_NAME",
        "uri": "http://loinc.org/property/CONSUMER_NAME",
        "description": "An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize.",
        "type": "string"
      }, {
        "code": "CLASSTYPE",
        "uri": "http://loinc.org/property/CLASSTYPE",
        "description": "1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys",
        "type": "string"
      }, {
        "code": "FORMULA",
        "uri": "http://loinc.org/property/FORMULA",
        "description": "Contains the formula in human readable form, for calculating the value of any measure that is based on an algebraic or other formula except those for which the component expresses the formula. So Sodium/creatinine does not need a formula, but Free T3 index does.",
        "type": "string"
      }, {
        "code": "EXMPL_ANSWERS",
        "uri": "http://lostringinc.org/property/EXMPL_ANSWERS",
        "description": "For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”.",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_TEXT",
        "uri": "http://loinc.org/property/SURVEY_QUEST_TEXT",
        "description": "Verbatim question from the survey instrument",
        "type": "string"
      }, {
        "code": "SURVEY_QUEST_SRC",
        "uri": "http://loinc.org/property/SURVEY_QUEST_SRC",
        "description": "Exact name of the survey instrument and the item/question number",
        "type": "string"
      }, {
        "code": "UNITSREQUIRED",
        "uri": "http://loinc.org/property/UNITSREQUIRED",
        "description": "Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment",
        "type": "string"
      }, {
        "code": "RELATEDNAMES2",
        "uri": "http://loinc.org/property/RELATEDNAMES2",
        "description": "This field was introduced in version 2.05. It contains synonyms for each of the parts of the fully specified LOINC name (component, property, time, system, scale, method).",
        "type": "string"
      }, {
        "code": "SHORTNAME",
        "uri": "http://loinc.org/property/SHORTNAME",
        "description": "Introduced in version 2.07, this field contains the short form of the LOINC name and is created via a table-driven algorithmic process. The short name often includes abbreviations and acronyms.",
        "type": "string"
      }, {
        "code": "ORDER_OBS",
        "uri": "http://loinc.org/property/ORDER_OBS",
        "description": "Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both",
        "type": "string"
      }, {
        "code": "HL7_FIELD_SUBFIELD_ID",
        "uri": "http://loinc.org/property/HL7_FIELD_SUBFIELD_ID",
        "description": "A value in this field means that the content should be delivered in the named field/subfield of the HL7 message. When NULL, the data for this data element should be sent in an OBX segment with this LOINC code stored in OBX-3 and with the value in the OBX-5.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_NOTICE",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE",
        "description": "External copyright holders copyright notice for this LOINC code",
        "type": "string"
      }, {
        "code": "EXAMPLE_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UNITS",
        "description": "This field is populated with a combination of submitters units and units that people have sent us. Its purpose is to show users representative, but not necessarily recommended, units in which data could be sent for this term.",
        "type": "string"
      }, {
        "code": "LONG_COMMON_NAME",
        "uri": "http://loinc.org/property/LONG_COMMON_NAME",
        "description": "This field contains the LOINC name in a more readable format than the fully specified name. The long common names have been created via a tabledriven algorithmic process. Most abbreviations and acronyms that are used in the LOINC database have been fully spelled out in English.",
        "type": "string"
      }, {
        "code": "EXAMPLE_UCUM_UNITS",
        "uri": "http://loinc.org/property/EXAMPLE_UCUM_UNITS",
        "description": "The Unified Code for Units of Measure (UCUM) is a code system intended to include all units of measures being contemporarily used in international science, engineering, and business. (www.unitsofmeasure.org) This field contains example units of measures for this term expressed as UCUM units.",
        "type": "string"
      }, {
        "code": "STATUS_REASON",
        "uri": "http://loinc.org/property/STATUS_REASON",
        "description": "Classification of the reason for concept status. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status where the reason is clear. DEPRECATED or DISCOURAGED terms may take values of: AMBIGUOUS, DUPLICATE, or ERRONEOUS.",
        "type": "string"
      }, {
        "code": "STATUS_TEXT",
        "uri": "http://loinc.org/property/STATUS_TEXT",
        "description": "Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status.",
        "type": "string"
      }, {
        "code": "CHANGE_REASON_PUBLIC",
        "uri": "http://loinc.org/property/CHANGE_REASON_PUBLIC",
        "description": "Detailed explanation about special changes to the term over time.",
        "type": "string"
      }, {
        "code": "COMMON_TEST_RANK",
        "uri": "http://loinc.org/property/COMMON_TEST_RANK",
        "description": "Ranking of approximately 2000 common tests performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "COMMON_ORDER_RANK",
        "uri": "http://loinc.org/property/COMMON_ORDER_RANK",
        "description": "Ranking of approximately 300 common orders performed by laboratories in USA.",
        "type": "string"
      }, {
        "code": "HL7_ATTACHMENT_STRUCTURE",
        "uri": "http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE",
        "description": "This property is populated in collaboration with the HL7 Payer-Provider Exchange (PIE) Work Group (previously called Attachments Work Group) as described in the HL7 Attachment Specification: Supplement to Consolidated CDA Templated Guide.",
        "type": "string"
      }, {
        "code": "EXTERNAL_COPYRIGHT_LINK",
        "uri": "http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK",
        "description": "For terms that have a third party copyright, this field is populated with the COPYRIGHT_ID from the Source Organization table (see below). It links an external copyright statement to a term.",
        "type": "string"
      }, {
        "code": "PanelType",
        "uri": "http://loinc.org/property/PanelType",
        "description": "For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'",
        "type": "string"
      }, {
        "code": "AskAtOrderEntry",
        "uri": "http://loinc.org/property/AskAtOrderEntry",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional Ask at Order Entry (AOE) observations for a clinical observation or laboratory test. A LOINC term in this field may represent a single AOE observation or a panel containing several AOE observations.",
        "type": "Coding"
      }, {
        "code": "AssociatedObservations",
        "uri": "http://loinc.org/property/AssociatedObservations",
        "description": "A multi-valued, semicolon delimited list of LOINC codes that represent optional associated observation(s) for a clinical observation or laboratory test. A LOINC term in this field may represent a single associated observation or panel containing several associated observations.",
        "type": "Coding"
      }, {
        "code": "VersionFirstReleased",
        "uri": "http://loinc.org/property/VersionFirstReleased",
        "description": "This is the LOINC version number in which this LOINC term was first published.",
        "type": "string"
      }, {
        "code": "ValidHL7AttachmentRequest",
        "uri": "http://loinc.org/property/ValidHL7AttachmentRequest",
        "description": "A value of Y in this field indicates that this LOINC code can be sent by a payer as part of an HL7 Attachment request for additional information.",
        "type": "string"
      }, {
        "code": "DisplayName",
        "uri": "http://loinc.org/property/DisplayName",
        "description": "A name that is more 'clinician-friendly' compared to the current LOINC Short Name, Long Common Name, and Fully Specified Name. It is created algorithmically from the manually crafted display text for each Part and is generally more concise than the Long Common Name.",
        "type": "string"
      }, {
        "code": "answer-list",
        "uri": "http://loinc.org/property/answer-list",
        "description": "An answer list associated with this LOINC code (if there are matching answer lists defined).",
        "type": "Coding"
      }, {
        "code": "MAP_TO",
        "uri": "http://loinc.org/property/MAP_TO",
        "description": "A replacement term that is to be used in place of the deprecated or discouraged term.",
        "type": "Coding"
      }, {
        "code": "analyte",
        "uri": "http://loinc.org/property/analyte",
        "description": "First sub-part of the Component, i.e., the part of the Component before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-core",
        "uri": "http://loinc.org/property/analyte-core",
        "description": "The primary part of the analyte without the suffix",
        "type": "Coding"
      }, {
        "code": "analyte-suffix",
        "uri": "http://loinc.org/property/analyte-suffix",
        "description": "The suffix part of the analyte, if present, e.g., Ab or DNA",
        "type": "Coding"
      }, {
        "code": "analyte-numerator",
        "uri": "http://loinc.org/property/analyte-numerator",
        "description": "The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor",
        "type": "Coding"
      }, {
        "code": "analyte-divisor",
        "uri": "http://loinc.org/property/analyte-divisor",
        "description": "The divisor part of the analyte, if present, i.e., after the slash and before the first carat",
        "type": "Coding"
      }, {
        "code": "analyte-divisor-suffix",
        "uri": "http://loinc.org/property/analyte-divisor-suffix",
        "description": "The suffix part of the divisor, if present",
        "type": "Coding"
      }, {
        "code": "challenge",
        "uri": "http://loinc.org/property/challenge",
        "description": "Second sub-part of the Component, i.e., after the first carat",
        "type": "Coding"
      }, {
        "code": "adjustment",
        "uri": "http://loinc.org/property/adjustment",
        "description": "Third sub-part of the Component, i.e., after the second carat",
        "type": "Coding"
      }, {
        "code": "count",
        "uri": "http://loinc.org/property/count",
        "description": "Fourth sub-part of the Component, i.e., after the third carat",
        "type": "Coding"
      }, {
        "code": "time-core",
        "uri": "http://loinc.org/property/time-core",
        "description": "The primary part of the Time",
        "type": "Coding"
      }, {
        "code": "time-modifier",
        "uri": "http://loinc.org/property/time-modifier",
        "description": "The modifier of the Time value, such as mean or max",
        "type": "Coding"
      }, {
        "code": "system-core",
        "uri": "http://loinc.org/property/system-core",
        "description": "The primary part of the System, i.e., without the super system",
        "type": "Coding"
      }, {
        "code": "super-system",
        "uri": "http://loinc.org/property/super-system",
        "description": "The super system part of the System, if present. The super system represents the source of the specimen when the source is someone or something other than the patient whose chart the result will be stored in. For example, fetus is the super system for measurements done on obstetric ultrasounds, because the fetus is being measured and that measurement is being recorded in the patient's (mother's) chart.",
        "type": "Coding"
      }, {
        "code": "analyte-gene",
        "uri": "http://loinc.org/property/analyte-gene",
        "description": "The specific gene represented in the analyte",
        "type": "Coding"
      }, {
        "code": "category",
        "uri": "http://loinc.org/property/category",
        "description": "A single LOINC term can be assigned one or more categories based on both programmatic and manual tagging. Category properties also utilize LOINC Class Parts.",
        "type": "Coding"
      }, {
        "code": "search",
        "uri": "http://loinc.org/property/search",
        "description": "Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-type",
        "uri": "http://loinc.org/property/rad-modality-modality-type",
        "description": "Modality is used to represent the device used to acquire imaging information.",
        "type": "Coding"
      }, {
        "code": "rad-modality-modality-subtype",
        "uri": "http://loinc.org/property/rad-modality-modality-subtype",
        "description": "Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-region-imaged",
        "uri": "http://loinc.org/property/rad-anatomic-location-region-imaged",
        "description": "The Anatomic Location Region Imaged attribute is used in two ways: as a coarse-grained descriptor of the area imaged and a grouper for finding related imaging exams; or, it is used just as a grouper.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-imaging-focus",
        "uri": "http://loinc.org/property/rad-anatomic-location-imaging-focus",
        "description": "The Anatomic Location Imaging Focus is a more fine-grained descriptor of the specific target structure of an imaging exam. In many areas, the focus should be a specific organ.",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality-presence",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality-presence",
        "description": "Radiology Exams that require laterality to be specified in order to be performed are signified with an Anatomic Location Laterality Presence attribute set to 'True'",
        "type": "Coding"
      }, {
        "code": "rad-anatomic-location-laterality",
        "uri": "http://loinc.org/property/rad-anatomic-location-laterality",
        "description": "Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified",
        "type": "Coding"
      }, {
        "code": "rad-view-aggregation",
        "uri": "http://loinc.org/property/rad-view-aggregation",
        "description": "Aggregation describes the extent of the imaging performed, whether in quantitative terms (e.g., '3 or more views') or subjective terms (e.g., 'complete').",
        "type": "Coding"
      }, {
        "code": "rad-view-view-type",
        "uri": "http://loinc.org/property/rad-view-view-type",
        "description": "View type names specific views, such as 'lateral' or 'AP'.",
        "type": "Coding"
      }, {
        "code": "rad-maneuver-maneuver-type",
        "uri": "http://loinc.org/property/rad-maneuver-maneuver-type",
        "description": "Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy.",
        "type": "Coding"
      }, {
        "code": "rad-timing",
        "uri": "http://loinc.org/property/rad-timing",
        "description": "The Timing/Existence property used in conjunction with pharmaceutical and maneuver properties. It specifies whether or not the imaging occurs in the presence of the administered pharmaceutical or a maneuver designed to test some dynamic aspect of anatomy or physiology .",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-substance-given",
        "uri": "http://loinc.org/property/rad-pharmaceutical-substance-given",
        "description": "The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure.",
        "type": "Coding"
      }, {
        "code": "rad-pharmaceutical-route",
        "uri": "http://loinc.org/property/rad-pharmaceutical-route",
        "description": "Route specifies the route of administration of the pharmaceutical.",
        "type": "Coding"
      }, {
        "code": "rad-reason-for-exam",
        "uri": "http://loinc.org/property/rad-reason-for-exam",
        "description": "Reason for exam is used to describe a clinical indication or a purpose for the study.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-presence",
        "uri": "http://loinc.org/property/rad-guidance-for-presence",
        "description": "Guidance for.Presence indicates when a procedure is guided by imaging.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-approach",
        "uri": "http://loinc.org/property/rad-guidance-for-approach",
        "description": "Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-action",
        "uri": "http://loinc.org/property/rad-guidance-for-action",
        "description": "Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation.",
        "type": "Coding"
      }, {
        "code": "rad-guidance-for-object",
        "uri": "http://loinc.org/property/rad-guidance-for-object",
        "description": "Guidance for.Object specifies the target of the action, such as mass, abscess or cyst.",
        "type": "Coding"
      }, {
        "code": "rad-subject",
        "uri": "http://loinc.org/property/rad-subject",
        "description": "Subject is intended for use when there is a need to distinguish between the patient associated with an imaging study, and the target of the study.",
        "type": "Coding"
      }, {
        "code": "document-kind",
        "uri": "http://loinc.org/property/document-kind",
        "description": "Characterizes the general structure of the document at a macro level.",
        "type": "Coding"
      }, {
        "code": "document-role",
        "uri": "http://loinc.org/property/document-role",
        "description": "Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty.",
        "type": "Coding"
      }, {
        "code": "document-setting",
        "uri": "http://loinc.org/property/document-setting",
        "description": "Setting is a modest extension of CMS’s coarse definition of care settings, such as outpatient, hospital, etc. Setting is not equivalent to location, which typically has more locally defined meanings.",
        "type": "Coding"
      }, {
        "code": "document-subject-matter-domain",
        "uri": "http://loinc.org/property/document-subject-matter-domain",
        "description": "Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc.",
        "type": "Coding"
      }, {
        "code": "document-type-of-service",
        "uri": "http://loinc.org/property/document-type-of-service",
        "description": "Characterizes the kind of service or activity provided to/for the patient (or other subject of the service) that is described in the document.",
        "type": "Coding"
      }, {
        "code": "answers-for",
        "uri": "http://loinc.org/property/answers-for",
        "description": "A LOINC Code for which this answer list is used.",
        "type": "Coding"
      } ]
    },
    "search": {
      "mode": "match"
    }
  } ]
}

Get info on an individual LOINC term, Part, Answer List, or Answer string

Use the $lookup operation to see details on any of the LOINC identifiers. As illustrated in the following examples, you can pass the canonical LOINC URI and code to the CodeSystem endpoint to perform the operation.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=4544-3

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP31755-9

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LL1162-8

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LA6751-7

Focus the request to return just what you want

Add a third parameter, &&property, to the examples above and you can limit the response to only the property—or properties—needed. As shown in the second example below, you can specify more than one property in a single request.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=4544-3&&property=METHOD_TYP

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=4544-3&&property=METHOD_TYP&&property=VersionFirstReleased

CodeSystem versions

Provide a LOINC version identifier (e.g. 2.69) to retrieve previous versions of concepts in LOINC.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP14542-2&version=2.71

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=96595-4&version=2.69

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=96595-4&version=2.70

If you examine the responses from the second and third examples above, you will see its CLASS changed from HEM/BC to CHEM.

The following request returns an error as expected because the code was not present in version 2.71 of LOINC.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=99463-2&version=2.71

Find relationships between LOINC terms and Parts

LOINC terms and Parts have relationships via the LOINC Component Hierarchy by System. These relationships can be found by using the $lookup operation in conjunction with the parent and child properties.

LOINC Parts have a single parent and one or more children.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP14542-2&&property=parent

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP28725-7&&property=parent

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP203649-1&&property=child

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=LP31448-1&&property=child

Because LOINC terms only exist at the leaf-level in the Component Hierarchy by System, they will have a parent but no children.

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=30064-0&&property=parent

https://fhir.loinc.org/CodeSystem/$lookup?system=http://loinc.org&code=79207-7&&property=parent

ValueSet

FHIR's ValueSet resource specifies a set of codes drawn from one or more code systems.

In LOINC's case, we have defined three main types of value sets:

Broadly useful collections
of LOINC terms

Answer Lists

e.g. LL4700-2

LOINC Groups

e.g. LG32763-1

Return the ValueSet definition

The examples below show how to call the ValueSet resource directly to give back the whole resource entry. This returns all of the metadata and definition criteria for a value set, including, for extensional value sets, which terms it includes. For example:

https://fhir.loinc.org/ValueSet/?url=http://loinc.org/vs/LL1162-8

Alternatively, you can specify the same value set as:

https://fhir.loinc.org/ValueSet/LL1162-8

Get the list of terms in the ValueSet

Use the $expand operation to only return the terms in a given value set (called a value set "expansion"), without the value set metadata.

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LL1162-8

Determine if a term is in a ValueSet

Use the $validate-code operation to verify if a particular term is in the given ValueSet. This example will return a valueBoolean of true.

https://fhir.loinc.org/ValueSet/LG33055-1/$validate-code?system=http://loinc.org&code=8867-4

ValueSet versions

You can retrieve the details and members of most ValueSet resources as they existed in previous LOINC versions. The version number is supplied as a suffix to the resource identifiers.

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51018-6-2.70

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51018-6-2.71

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51018-6-2.72

In responses returned by the previous examples, you can see how constituents of the LG51018-6 Group for SARS-CoV-2 serology tests increased from 28 to 29 to 33 members in each subsequent LOINC version. Again, requests without a version suffix will always return the most current version of the ValueSet.

Note that previous versions of intensionally-defined ValueSet resources are not possible due to their rule-based nature. Versioning of some named collections (as opposed to those identified by a LOINC code) referenced below is not yet enabled.

Public health value sets

We have defined several new subsets of LOINC terms related to SARS-CoV-2/COVID-19 testing and reporting. The first three are LOINC Groups, which we are specifically calling out here so that they will be easily accessible, and the fourth is a value set for LOINC terms related to public health case reporting. These terms may be used in other contexts besides the COVID-19 pandemic.

Each value set is given below with:

The URL to return its definition; and
The URL to return its expansion.

Remember, the definition for extensional value sets returns the set of LOINC terms included in that value set.

These FHIR value sets only include published LOINC terms. The full list of released and pre-release LOINC terms related to SARS-CoV-2/COVID-19 is available at https://loinc.org/sars-cov-2-and-covid-19/.

LOINC terms for SARS-CoV-2 laboratory tests

VS type: extensional

SARS-CoV-2 detection (including molecular, antigen, and culture)

http://loinc.org/vs/LG51017-8

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51017-8

SARS-CoV-2 molecular detection

http://loinc.org/vs/LG51019-4

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51019-4

SARS-CoV-2 serology tests

http://loinc.org/vs/LG51018-6

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LG51018-6

LOINC terms related to public health case reporting

VS type: extensional

http://loinc.org/vs/loincs-related-to-public-health-case-reporting

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/loincs-related-to-public-health-case-reporting

General collections of LOINC terms

We have defined several key subsets of LOINC terms as ValueSets because they are useful collections for various purposes.

Each value set is given below with:

The URL to return its definition; and
The URL to return its expansion.

Remember, the definition for extensional value sets returns the set of LOINC terms included in that value set.

LOINC Document Ontology

VS type: extensional

More information on this collection

http://loinc.org/vs/loinc-document-ontology

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/loinc-document-ontology

LOINC Functional Status

VS type: extensional

This value set is currently based on the subset of the Centers for Medicare and Medicaid Services’ Standardized Patient Assessment Data Elements (SPADEs) related to functional status.

http://loinc.org/vs/functional-status

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/functional-status

LOINC/RSNA Radiology Playbook and Playbook Core

VS type: extensional

More information on these collections

Radiology Playbook

http://loinc.org/vs/loinc-rsna-radiology-playbook

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/loinc-rsna-radiology-playbook

Radiology Playbook Core

http://loinc.org/vs/loinc-rsna-radiology-playbook-core

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/loinc-rsna-radiology-playbook-core

Valid HL7 Attachment Requests and Responses

VS type: intensional
See Issue related to expansion of intensionally-defined ValueSets

More information on these subsets

Valid HL7 Attachment Requests

http://loinc.org/vs/valid-hl7-attachment-requests

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/valid-hl7-attachment-requests

Valid HL7 Attachment Responses

http://loinc.org/vs/valid-hl7-attachment-responses

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/valid-hl7-attachment-responses

Valid HL7 Attachment Responses - Implementation Guide Exists

http://loinc.org/vs/valid-hl7-attachment-responses-ig-exists

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/valid-hl7-attachment-responses-ig-exists

Valid HL7 Attachment Responses - No Implementation Guide Exists

http://loinc.org/vs/valid-hl7-attachment-responses-no-ig-exists

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/valid-hl7-attachment-responses-no-ig-exists

Deprecated LOINC Terms

VS type: intensional
See Issue related to expansion of intensionally-defined ValueSets

http://loinc.org/vs/deprecated-loinc-terms

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/deprecated-loinc-terms

Top 20,000

VS type: intensional
Learn more about LOINC code rankings

https://fhir.loinc.org/ValueSet/?url=http://loinc.org/vs/loinc-top-ranked

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/loinc-top-ranked

Top Lab Orders

NEW

VS type: intensional
Learn more about universal lab order codes

https://fhir.loinc.org/ValueSet/?url=http://loinc.org/vs/top-lab-orders

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/top-lab-orders

LOINC Answer Lists as Value Sets

Brief background on answer lists in LOINC

LOINC contains links between many of its observation terms and a set of possible answers that could be used as result values. Within LOINC, we have created a structured representation of these answer lists.

LOINC Answer Lists are assigned a non-semantic identifier with a “LL” prefix and a Luhn/mod-10 check digit. The individual answers (called LOINC Answers) within a list are assigned a non-semantic identifier with a “LA” prefix and a mod-10 check digit. The answer codes LOINC assigns are unique by lexical string (ignoring capitalization), and by intention do not distinguish between strings that may have different meanings depending on their contextual use.

Using LOINC Answer Lists

LOINC Answer Lists represent collections of coded concepts that can be used as response values to LOINC terms. The canonical URI pattern for identifying the value set defined by a LOINC Answer List is: http://loinc.org/vs/{LOINC Answer List code}

Get the list of LOINC Answers in a LOINC Answer List as a FHIR Value Set expansion

https://fhir.loinc.org/ValueSet/$expand?url=http://loinc.org/vs/LL1162-8

Search for all Answer Lists with “Yes” in their name

https://fhir.loinc.org/ValueSet?name:in=Yes

Determine if a LOINC Answer is in an Answer List

https://fhir.loinc.org/ValueSet/LL1162-8/$validate-code?system=http://loinc.org&code=LA15679-6

LOINC Groups as Value Sets

LOINC Groups are a technique for rolling up groups of LOINC terms that could be treated as equivalent or useful for various purposes. For example, you may want to aggregate data for displaying on a flowsheet within an electronic health record (EHR) system, retrieve data for quality measure reporting, or process data for research.

Each LOINC Group is assigned a non-semantic identifier with a “LG” prefix. The LG codes serve as a coded value set identifier. As such, they correspond to a particular “definition” of what should be included in the group. Following best practices, LOINC Groups intend to keep the logical definition stable in meaning over time. However, the members of the group may change as the underlying terminology (LOINC) evolves. For example, new concepts may be added that fulfill a group’s definition and are thus included.

LOINC Group as Value Set

https://fhir.loinc.org/ValueSet/?url=http://loinc.org/vs/LG9568-9

https://fhir.loinc.org/ValueSet/LG9568-9

Confirm a LOINC Code as a member of a Group

https://fhir.loinc.org/ValueSet/LG9568-9/$validate-code?system=http://loinc.org&code=6785-0

ConceptMap

The ConceptMap resource in FHIR defines a mapping from one set of concepts defined in a code system ("source") to one or more concepts defined in other code systems ("target").

We have created the following bidirectional concept maps and will continue to add to these over time.

In the examples below, calling the ConceptMap resource directly gives you back the whole resource entry for the specified set. This will give you all the ConceptMap metadata, the mappings, etc. Each ConceptMap resource is referenced using its canonical URI.

LOINC terms IEEE device codes

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-ieee-11073-10101

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/ieee-11073-10101-to-loinc

LOINC terms RadLex Playbook procedure codes (RPIDs)

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-radlex

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/radlex-to-loinc

LOINC Parts RadLex clinical terms (RIDs)

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-radlex

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/radlex-to-loinc-parts

LOINC Parts RxNorm terms

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-rxnorm

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/rxnorm-to-loinc-parts

LOINC Parts PubChem terms

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-pubchem

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/pubchem-to-loinc-parts

LOINC Parts SNOMED CT terms

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-snomed-ct

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/snomed-ct-to-loinc-parts

LOINC terms PhenX concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-phenx

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/phenx-to-loinc

LOINC terms CMS Long-term Post-acute care (LT-PAC) assessment concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-cms-irf-pai

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/cms-irf-pai-to-loinc

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-cms-lcds

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/cms-lcds-to-loinc

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-cms-mds

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/cms-mds-to-loinc

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-to-cms-oasis

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/cms-oasis-to-loinc

LOINC Parts ChEBI concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-chebi

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/chebi-to-loinc-parts

LOINC Parts NCBI ClinVar concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-ncbi-clinvar

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/ncbi-clinvar-to-loinc-parts

LOINC Parts NCBI Gene concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-ncbi-gene

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/ncbi-gene-to-loinc-parts

LOINC Parts NCBI Taxonomy concepts

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/loinc-parts-to-ncbi-taxonomy

https://fhir.loinc.org/ConceptMap/?url=http://loinc.org/cm/ncbi-taxonomy-to-loinc-parts

Equivalence

Each individual map has an equivalence value that indicates whether the source and target concepts are equivalent or whether one is broader or narrower in meaning than the other. Note that FHIR defines the equivalence as going from the target concept to the source, so if the equivalence value is "narrower", that means the target concept is more specific than the source concept.

For example, LOINC 30657-1 (MR Brain WO contrast) is mapped to RPID479 (MR Head wo IV contrast) with equivalence "equivalent" while the same LOINC term is mapped to RPID593 (MR Head wo IV contrast Pediatric) with equivalence "narrower", because RPID593 is specific for pediatric patients.

https://fhir.loinc.org/ConceptMap/$translate?system=http://loinc.org&code=30657-1

Get the mapping for a particular LOINC Code

Use the $translate operation to find a mapping for a particular source term.

https://fhir.loinc.org/ConceptMap/$translate?system=http://loinc.org&code=11556-8

ConceptMap versions

Similar to versioning of ValueSet resources, you can supply a suffix to the ConceptMap identifier to retrieve past versions.

https://fhir.loinc.org/ConceptMap/loinc-parts-to-rxnorm-2.69

Questionnaire

FHIR's questionnaire resource provides a way to represent a set of questions in a structured format along with associated information such as answer lists, instructions, and skip logic. Starting with the 2.68 release, we implemented LOINC panels using R4 questionnaire resources. Our current deployment renders the LOINC panels as they are currently represented in the database; in addition, we have begun adding features, such as computable skip logic, to a subset of LOINC panels represented as FHIR questionnaires.

Return a LOINC panel as a FHIR questionnaire

The following examples show how you can return a LOINC panel as a FHIR questionnaire using the canonical LOINC URI pattern for questionnaires: http://loinc.org/q/{LOINC #}.

https://fhir.loinc.org/Questionnaire/?url=http://loinc.org/q/89689-4

https://fhir.loinc.org/Questionnaire/89689-4

Using this call will return the full LOINC panel, including all of the Answer lists contained in that panel as value sets, the binding between each LOINC question term and its specific Answer List, and any codes or scores contained in each list. Note the enableWhen values, which represent computable skip logic, in the second example below.

https://fhir.loinc.org/Questionnaire/55757-9

https://fhir.loinc.org/Questionnaire/93245-9

Known Issues

The service maintains a BETA status.
Some previous versions of ConceptMap resources are not yet operational.
Expansion of select parent LOINC Group codes is failing.
Within the CodeSystem resource, some Radiology properties are duplicated on select terms, e.g. 36554-4. The terms for which there are duplicate properties are those that are mapped to multiple RPID codes in the LoincRsnaRadiologyPlaybook.csv file. Each LOINC-RPID mapping has its own set of rows for each of the Radiology attributes (properties) in the .csv file, so when a LOINC is mapped to more than one RPID, there will be multiple rows for each attribute. Because the Radiology properties in the FHIR representation are loaded from the .csv file, the multiple rows per attribute wind up as duplicates.

Please contact us if you identify any issues not mentioned above.

LOINC Terminology Service using HL7® FHIR®

Access LOINC's terminology content through the HL7® FHIR® API

BETA Status

Definitions

FHIR resource

Select FHIR terminology resources

Operation

Select FHIR terminology operations/parameters

You need a LOINC login

Tips on using examples

Related content

Versioning of resources

Translations as designations

CodeSystem

LOINC Codes

LOINC Parts

LOINC Answer Lists

LOINC Answers

All LOINC fields are now represented as Properties

Get the specialized properties available for LOINC as a CodeSystem in FHIR

Get info on an individual LOINC term, Part, Answer List, or Answer string

Focus the request to return just what you want

CodeSystem versions

Find relationships between LOINC terms and Parts

ValueSet

Broadly useful collections of LOINC terms

Answer Lists

LOINC Groups

Return the ValueSet definition

Get the list of terms in the ValueSet

Determine if a term is in a ValueSet

ValueSet versions

Public health value sets

LOINC terms for SARS-CoV-2 laboratory tests

LOINC terms related to public health case reporting

General collections of LOINC terms

LOINC Document Ontology

LOINC Functional Status

LOINC/RSNA Radiology Playbook and Playbook Core

Valid HL7 Attachment Requests and Responses

Deprecated LOINC Terms

Top 20,000

Top Lab Orders

LOINC Answer Lists as Value Sets

Brief background on answer lists in LOINC

Using LOINC Answer Lists

Get the list of LOINC Answers in a LOINC Answer List as a FHIR Value Set expansion

Search for all Answer Lists with “Yes” in their name

Determine if a LOINC Answer is in an Answer List

LOINC Groups as Value Sets

LOINC Group as Value Set

Confirm a LOINC Code as a member of a Group

ConceptMap

LOINC terms IEEE device codes

LOINC terms RadLex Playbook procedure codes (RPIDs)

LOINC Parts RadLex clinical terms (RIDs)

LOINC Parts RxNorm terms

LOINC Parts PubChem terms

LOINC Parts SNOMED CT terms

LOINC terms PhenX concepts

LOINC terms CMS Long-term Post-acute care (LT-PAC) assessment concepts

LOINC Parts ChEBI concepts

LOINC Parts NCBI ClinVar concepts

LOINC Parts NCBI Gene concepts

LOINC Parts NCBI Taxonomy concepts

Equivalence

Get the mapping for a particular LOINC Code

ConceptMap versions

Questionnaire

Return a LOINC panel as a FHIR questionnaire

Known Issues

Broadly useful collections
of LOINC terms