Why does server return much more data on LOINC than SNOMED?

[joeflack4]

Overview

I noticed a difference in the response I got. @ShahimEssaid I'm assuming you probably have a good idea why?

SNOMED

Request: http://20.119.216.32:8000/r4/CodeSystem?name=SNOMED%20CT

Response:

{
  "resourceType": "Bundle",
  "id": "78dc86e5-bf70-4dfc-8cca-ce78e2d57c3f",
  "meta": {
    "lastUpdated": "2022-10-04T23:33:57.835+00:00"
  },
  "type": "searchset",
  "total": 1,
  "link": [
    {
      "relation": "self",
      "url": "http://20.119.216.32:8000/r4/CodeSystem?name=SNOMED%20CT"
    }
  ],
  "entry": [
    {
      "fullUrl": "http://20.119.216.32:8000/r4/CodeSystem/1",
      "resource": {
        "resourceType": "CodeSystem",
        "id": "1",
        "meta": {
          "versionId": "1",
          "lastUpdated": "2022-07-15T06:19:31.848+00:00",
          "source": "#0VAGusSzll8p4nYB"
        },
        "url": "http://snomed.info/sct",
        "name": "SNOMED CT",
        "status": "active",
        "content": "not-present"
      },
      "search": {
        "mode": "match"
      }
    }
  ]
}

LOINC

Request: http://20.119.216.32:8000/r4/CodeSystem?system=http%3A%2F%2Floinc.org

Response:

{
  "resourceType": "Bundle",
  "id": "a78f8268-6829-4985-9966-e7e0cb9d2296",
  "meta": {
    "lastUpdated": "2022-10-04T23:27:13.411+00:00"
  },
  "type": "searchset",
  "total": 1,
  "link": [
    {
      "relation": "self",
      "url": "http://20.119.216.32:8000/r4/CodeSystem?system=http%3A%2F%2Floinc.org"
    }
  ],
  "entry": [
    {
      "fullUrl": "http://20.119.216.32:8000/r4/CodeSystem/loinc",
      "resource": {
        "resourceType": "CodeSystem",
        "id": "loinc",
        "fhir_comments": [
          "\nLOINC is a freely available international standard for tests, measurements, and observations. It is a well maintained, version independent code system.\n\nUse of LOINC is governed by the LOINC License: https://loinc.org/license/\n\nThis CodeSystem resource describes 'LOINC' independent of any particular version. There are notes about changes for version specific LOINC code system resources.\n\nNote that the following set of codes are defined by the LOINC code systems:\n - the main LOINC codes\n - the LOINC Answer codes (LA) and the LOINC Answer list codes (LL)\n - the LOINC Part codes (LP) in the Multiaxial Hierarchy\n - the LOINC Part codes (LP) for the properties\n    Note: there are license restrictions on the use of LOINC Part codes\n - the LOINC Group codes (LG)\n    Note: presently the LOINC Group codes are used to identify these roll-up groups as ValueSets, but are not yet loaded as codes in the CodeSystem\n\nServers may generate variants of this for the LOINC version(s) and features they support.\n\n"
        ],
        "meta": {
          "versionId": "1",
          "lastUpdated": "2022-07-15T06:21:04.607+00:00",
          "source": "#Nl3W8zlWPJlvwgAj"
        },
        "url": "http://loinc.org",
        "_url": {
          "fhir_comments": [
            "\n    This url is unchanged for all versions of LOINC. There can only be one correct Code System resource for each value of the version attribute (at least, only one per server).\n    "
          ]
        },
        "identifier": [
          {
            "fhir_comments": [
              " the HL7 v3 OID assigned to LOINC "
            ],
            "system": "urn:ietf:rfc:3986",
            "value": "urn:oid:2.16.840.1.113883.6.1"
          }
        ],
        "name": "LOINC",
        "_name": {
          "fhir_comments": [
            "\n    If a version is specified: <version value=\"2.70\"/>\n    ",
            "\n    If a specific version is specified, the name should carry this information (e.g. LOINC_270).\n    "
          ]
        },
        "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",
        "_description": {
          "fhir_comments": [
            "\n\t<date value=2022-02/>\n\t"
          ]
        },
        "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",
        "_hierarchyMeaning": {
          "fhir_comments": [
            "\n\t To reference a version-specific resource, append the version number such as:\n\t <valueSet value=\"http://loinc.org/vs/LG38848-4-2.72\"/>\n\t Where \"-2.72\" indicates LOINC version 2.72 of the LOINC Group code LG38848-4.\n  ",
            "\n\t  It's at the discretion of servers whether to present fragments of LOINC hierarchically or not, when using the code system resource. But, if they are hierarchical, the Hierarchy SHALL be based on the is-a relationship that is derived from the LOINC Multiaxial Hierarchy.\n\t"
          ]
        },
        "compositional": false,
        "versionNeeded": false,
        "_versionNeeded": {
          "fhir_comments": [
            " no compositional grammar in LOINC "
          ]
        },
        "content": "not-present",
        "_content": {
          "fhir_comments": [
            "\n\tThis canonical definition of LOINC does not include the LOINC content, which is distributed separately for portability.\n\n\tServers may choose to include fragments of LOINC for illustration purposes.\n "
          ]
        },
        "filter": [
          {
            "fhir_comments": [
              "\n\t  <count value=\"65000\"/>\n\t  If working with a specific version, you could nominate a count of the total number of concepts (including the answers, Hierarchy, etc.). In this canonical definition we do not.\n\t",
              "\n\t  FILTERS\n\t  Generally defined filters for specifying value sets\n\t  In LOINC, all the properties can also be used as filters, but they are not defined explicitly as filters.\n\t  Parent/child properties are as defined by FHIR. Note that at this time the LOINC code system resource does not support ancestor/descendant relationships.\n\n\t  For illustration purposes, consider this slice of the LOINC Multiaxial Hierarchy when reading the descriptions below:\n\n\t  Laboratory [LP29693-6]\n        Microbiology and Antimicrobial susceptibility [LP343406-7]\n            Microbiology [LP7819-8]\n                Microorganism [LP14559-6]\n                    Virus [LP14855-8]\n                        Zika virus [LP200137-0]\n                            Zika virus RNA | XXX [LP203271-4]\n                                Zika virus RNA | XXX | Microbiology [LP379670-5]\n                                    Zika virus RNA [Presence] in Unspecified specimen by Probe and target amplification method [79190-5]\n\n\t  Language Note: The filters defined here are specified using the default LOINC language - English (US). Requests are meant to be specified and interpreted on the English version. The return can be in a specified language (if supported by the server). But note that not all filters/properties have language translations available.\n\t  "
            ],
            "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": [
          {
            "fhir_comments": [
              "\n\tPROPERTIES\n\tThere are 4 kinds of properties that apply to all LOINC codes:\n\t  1. FHIR: display, designation; these are not described here since they are inherent in the specification\n\t  2. Infrastructural: defined by FHIR, but documented here for the LOINC Multiaxial Hierarchy\n\t  3. Primary LOINC properties: defined by the main LOINC table\n\t  4. Secondary LOINC properties: defined by the LoincPartLink table\n\tAdditionally, there are 2 kinds of properties specific to Document ontology and Radiology codes, respectively:\n\t  1. LOINC/RSNA Radiology Playbook properties\n\t  2. Document Ontology properties\n\t",
              "\n\tInfrastructural properties - inherited from FHIR, but documented here for the LOINC Multiaxial Hierarchy.\n\t"
            ],
            "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"
          },
          {
            "fhir_comments": [
              "\n\t  Primary LOINC properties.\n\t  These apply to the main LOINC codes, but not the Multiaxial Hierarchy, Answer lists, or the Part codes.\n\t  Notes:\n\t\t In the LOINC code system resource, the display element = LONG_COMMON_NAME\n\t\t Many properties are specified as type \"Coding\", which allows use of LOINC Part codes (LP-) and the display text. LOINC Parts and their associations to LOINC terms are published in the LOINC Part File.\n\t\t The properties defined here follow the guidance of the LOINC Users' Guide, which states that they should be expressed with the LOINC attributes contained in the LOINC Table. Properties that are not defined in the LOINC Table use FHIR-styled names.\n\t"
            ],
            "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"
          },
          {
            "fhir_comments": [
              "\n\t\tSecondary LOINC properties.\n\t\tThese properties also apply to the main LOINC codes, but not the Multiaxial Hierarchy, Answer lists, or the Part codes.\n\t\tNotes:\n\t\t  These properties are defined in the LoincPartLink table.\n\t "
            ],
            "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"
          },
          {
            "fhir_comments": [
              "\n\tLOINC/RSNA Radiology Playbook properties. These apply only to terms in the LOINC/RSNA Radiology Playbook File.\n\t\t  Notes:\n\t\t\tProperties are specified as type \"Coding\", which are represented by LOINC Part codes (LP-) and their display names.\n\t\t\tThe attribute names here use FHIR styled names rather than their original LOINC style names because the original names contain periods.\n\t"
            ],
            "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"
          },
          {
            "fhir_comments": [
              "\n\tDocument Ontology properties.\n\tThese apply only to terms in the LOINC Document Ontology File\n\t\t  Notes\n\t\t\tProperties are specified as type \"Coding\", which are represented by LOINC Part codes (LP-) and their display names.\n\t\t\tThe attribute names here use FHIR styled names rather than their original LOINC style names because those contain periods.\n\t "
            ],
            "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"
          },
          {
            "fhir_comments": [
              " Answer list related properties ",
              " Note for future consideration. These are properties of LA codes in the context of a particular list. Not global properties.\n\t<property>\n\t  <code value=\"sequence\"/>\n\t  <uri value=\"http://loinc.org/property/sequence\"/>\n\t  <description value=\"Sequence Number of a answer in a set of answers (LA- codes only)\"/>\n\t  <type value=\"integer\"/>\n\t</property>\n\t<property>\n\t  <code value=\"score\"/>\n\t  <uri value=\"http://loinc.org/property/score\"/>\n\t  <description value=\"Score assigned to an answer (LA- codes only)\"/>\n\t  <type value=\"integer\"/>\n\t</property>\n\t "
            ],
            "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"
      }
    }
  ]
}

[chrisroederucdenver]

another angle to this issue would be how do you verify that all of what you need from a vocabulary is available. If you focus just on the terms/concepts, what gets loaded and how can we verify they are all there? Hard core would be to read either the code that builds the json that gets loaded (assuming), or the resulting json and use ConceptSystem$validate to verify they're in there. I'm sort of suggesting this could be red-herring metadata.

[ShahimEssaid]

Just a quick response for now. The server doesn't know more about LOINC. It's just returning the resource you searched for. For LOINC, the HAPI LOINC loading module generates a CodeSystem resource that has a lot more info. See here for the hard-coded loaders and what they might do when using the CLI to load a native release file: https://github.com/hapifhir/hapi-fhir/tree/master/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term https://github.com/hapifhir/hapi-fhir/tree/master/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/loinc

[joeflack4]

Thanks, Shahim. I was thinking that might be the case, but didn't yet know for sure.

[joeflack4]

I wonder if we will be requested to provide something more detailed for SNOMED but my guess is that it would not be a very high priority.

[joeflack4]

Gonna close this as not planned but perhaps this will come up again at some point.