SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

name

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="loinc" />
  
  <url value="http://loinc.org" />
  
  <identifier>
    <system value="urn:ietf:rfc:3986" />
    <value value="urn:oid:2.16.840.1.113883.6.1" />
  </identifier>
  
  
  <name value="LOINC" />
  <title value="LOINC Code System github.com" />
  <status value="active" />
  <experimental value="false" />
  <publisher value="Regenstrief Institute, Inc." />
  <contact>
    <telecom>
      <system value="url" />
      <value value="http://loinc.org" />
    </telecom>
  </contact>
  
  <description value="LOINC is a freely available international standard for tests, measurements, and observations" />
  <copyright value="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 value="false" />
  <valueSet value="http://loinc.org/vs" />
  
  
  <hierarchyMeaning value="is-a" />
  <compositional value="false" />
  
  <versionNeeded value="false" />
  
  <content value="not-present" />
  
  
  <filter>
    <code value="parent" />
    <description value="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="=" />
    <value value="A Part code" />
  </filter>
  <filter>
    <code value="child" />
    <description value="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="=" />
    <value value="A comma separated list of Part or LOINC codes" />
  </filter>
  <filter>
    <code value="copyright" />
    <description value="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="=" />
    <value value="LOINC | 3rdParty" />
  </filter>
  
  
  <property>
    <code value="parent" />
    <uri value="http://hl7.org/fhir/concept-properties#parent" />
    <description value="A parent code in the Component Hierarchy by System" />
    <type value="code" />
  </property>
  <property>
    <code value="child" />
    <uri value="http://hl7.org/fhir/concept-properties#child" />
    <description value="A child code in the Component Hierarchy by System" />
    <type value="code" />
  </property>
  
  <property>
    <code value="COMPONENT" />
    <uri value="http://loinc.org/property/COMPONENT" />
    <description value="First major axis-component or analyte: Analyte Name, Analyte sub-class, Challenge" />
    <type value="Coding" />
  </property>
  <property>
    <code value="PROPERTY" />
    <uri value="http://loinc.org/property/PROPERTY" />
    <description value="Second major axis-property observed: Kind of Property (also called kind of quantity)" />
    <type value="Coding" />
  </property>
  <property>
    <code value="TIME_ASPCT" />
    <uri value="http://loinc.org/property/TIME_ASPCT" />
    <description value="Third major axis-timing of the measurement: Time Aspect (Point or moment in time vs. time interval)" />
    <type value="Coding" />
  </property>
  <property>
    <code value="SYSTEM" />
    <uri value="http://loinc.org/property/SYSTEM" />
    <description value="Fourth major axis-type of specimen or system: System (Sample) Type" />
    <type value="Coding" />
  </property>
  <property>
    <code value="SCALE_TYP" />
    <uri value="http://loinc.org/property/SCALE_TYP" />
    <description value="Fifth major axis-scale of measurement: Type of Scale" />
    <type value="Coding" />
  </property>
  <property>
    <code value="METHOD_TYP" />
    <uri value="http://loinc.org/property/METHOD_TYP" />
    <description value="Sixth major axis-method of measurement: Type of Method" />
    <type value="Coding" />
  </property>
  <property>
    <code value="CLASS" />
    <uri value="http://loinc.org/property/CLASS" />
    <description value="An arbitrary classification of terms for grouping related observations together" />
    <type value="Coding" />
  </property>
  <property>
    <code value="VersionLastChanged" />
    <uri value="http://loinc.org/property/VersionLastChanged" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="CHNG_TYPE" />
    <uri value="http://loinc.org/property/CHNG_TYPE" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="DefinitionDescription" />
    <uri value="http://loinc.org/property/DefinitionDescription" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="STATUS" />
    <uri value="http://loinc.org/property/STATUS" />
    <description value="Status of the term. Within LOINC, codes with STATUS=DEPRECATED are considered inactive. Current values: ACTIVE, TRIAL, DISCOURAGED, and DEPRECATED" />
    <type value="string" />
  </property>
  <property>
    <code value="CONSUMER_NAME" />
    <uri value="http://loinc.org/property/CONSUMER_NAME" />
    <description value="An experimental (beta) consumer friendly name for this item. The intent is to provide a test name that health care consumers will recognize." />
    <type value="string" />
  </property>
  <property>
    <code value="CLASSTYPE" />
    <uri value="http://loinc.org/property/CLASSTYPE" />
    <description value="1=Laboratory class; 2=Clinical class; 3=Claims attachments; 4=Surveys" />
    <type value="string" />
  </property>
  <property>
    <code value="FORMULA" />
    <uri value="http://loinc.org/property/FORMULA" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="EXMPL_ANSWERS" />
    <uri value="http://lostringinc.org/property/EXMPL_ANSWERS" />
    <description value="For some tests and measurements, we have supplied examples of valid answers, such as “1:64”, “negative @ 1:16”, or “55”." />
    <type value="string" />
  </property>
  <property>
    <code value="SURVEY_QUEST_TEXT" />
    <uri value="http://loinc.org/property/SURVEY_QUEST_TEXT" />
    <description value="Verbatim question from the survey instrument" />
    <type value="string" />
  </property>
  <property>
    <code value="SURVEY_QUEST_SRC" />
    <uri value="http://loinc.org/property/SURVEY_QUEST_SRC" />
    <description value="Exact name of the survey instrument and the item/question number" />
    <type value="string" />
  </property>
  <property>
    <code value="UNITSREQUIRED" />
    <uri value="http://loinc.org/property/UNITSREQUIRED" />
    <description value="Y/N field that indicates that units are required when this LOINC is included as an OBX segment in a HIPAA attachment" />
    <type value="string" />
  </property>
  <property>
    <code value="RELATEDNAMES2" />
    <uri value="http://loinc.org/property/RELATEDNAMES2" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="SHORTNAME" />
    <uri value="http://loinc.org/property/SHORTNAME" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="ORDER_OBS" />
    <uri value="http://loinc.org/property/ORDER_OBS" />
    <description value="Provides users with an idea of the intended use of the term by categorizing it as an order only, observation only, or both" />
    <type value="string" />
  </property>
  <property>
    <code value="HL7_FIELD_SUBFIELD_ID" />
    <uri value="http://loinc.org/property/HL7_FIELD_SUBFIELD_ID" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="EXTERNAL_COPYRIGHT_NOTICE" />
    <uri value="http://loinc.org/property/EXTERNAL_COPYRIGHT_NOTICE" />
    <description value="External copyright holders copyright notice for this LOINC code" />
    <type value="string" />
  </property>
  <property>
    <code value="EXAMPLE_UNITS" />
    <uri value="http://loinc.org/property/EXAMPLE_UNITS" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="LONG_COMMON_NAME" />
    <uri value="http://loinc.org/property/LONG_COMMON_NAME" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="EXAMPLE_UCUM_UNITS" />
    <uri value="http://loinc.org/property/EXAMPLE_UCUM_UNITS" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="STATUS_REASON" />
    <uri value="http://loinc.org/property/STATUS_REASON" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="STATUS_TEXT" />
    <uri value="http://loinc.org/property/STATUS_TEXT" />
    <description value="Explanation of concept status in narrative text. This field will be Null for ACTIVE concepts, and optionally populated for terms in other status." />
    <type value="string" />
  </property>
  <property>
    <code value="CHANGE_REASON_PUBLIC" />
    <uri value="http://loinc.org/property/CHANGE_REASON_PUBLIC" />
    <description value="Detailed explanation about special changes to the term over time." />
    <type value="string" />
  </property>
  <property>
    <code value="COMMON_TEST_RANK" />
    <uri value="http://loinc.org/property/COMMON_TEST_RANK" />
    <description value="Ranking of approximately 2000 common tests performed by laboratories in USA." />
    <type value="string" />
  </property>
  <property>
    <code value="COMMON_ORDER_RANK" />
    <uri value="http://loinc.org/property/COMMON_ORDER_RANK" />
    <description value="Ranking of approximately 300 common orders performed by laboratories in USA." />
    <type value="string" />
  </property>
  <property>
    <code value="HL7_ATTACHMENT_STRUCTURE" />
    <uri value="http://loinc.org/property/HL7_ATTACHMENT_STRUCTURE" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="EXTERNAL_COPYRIGHT_LINK" />
    <uri value="http://loinc.org/property/EXTERNAL_COPYRIGHT_LINK" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="PanelType" />
    <uri value="http://loinc.org/property/PanelType" />
    <description value="For LOINC terms that are panels, this attribute classifies them as a 'Convenience group', 'Organizer', or 'Panel'" />
    <type value="string" />
  </property>
  <property>
    <code value="AskAtOrderEntry" />
    <uri value="http://loinc.org/property/AskAtOrderEntry" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="AssociatedObservations" />
    <uri value="http://loinc.org/property/AssociatedObservations" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="VersionFirstReleased" />
    <uri value="http://loinc.org/property/VersionFirstReleased" />
    <description value="This is the LOINC version number in which this LOINC term was first published." />
    <type value="string" />
  </property>
  <property>
    <code value="ValidHL7AttachmentRequest" />
    <uri value="http://loinc.org/property/ValidHL7AttachmentRequest" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="DisplayName" />
    <uri value="http://loinc.org/property/DisplayName" />
    <description value="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 value="string" />
  </property>
  <property>
    <code value="answer-list" />
    <uri value="http://loinc.org/property/answer-list" />
    <description value="An answer list associated with this LOINC code (if there are matching answer lists defined)." />
    <type value="Coding" />
  </property>
  <property>
    <code value="MAP_TO" />
    <uri value="http://loinc.org/property/MAP_TO" />
    <description value="A replacement term that is to be used in place of the deprecated or discouraged term." />
    <type value="Coding" />
  </property>
  
  <property>
    <code value="analyte" />
    <uri value="http://loinc.org/property/analyte" />
    <description value="First sub-part of the Component, i.e., the part of the Component before the first carat" />
    <type value="Coding" />
  </property>
  <property>
    <code value="analyte-core" />
    <uri value="http://loinc.org/property/analyte-core" />
    <description value="The primary part of the analyte without the suffix" />
    <type value="Coding" />
  </property>
  <property>
    <code value="analyte-suffix" />
    <uri value="http://loinc.org/property/analyte-suffix" />
    <description value="The suffix part of the analyte, if present, e.g., Ab or DNA" />
    <type value="Coding" />
  </property>
  <property>
    <code value="analyte-numerator" />
    <uri value="http://loinc.org/property/analyte-numerator" />
    <description value="The numerator part of the analyte, i.e., everything before the slash in analytes that contain a divisor" />
    <type value="Coding" />
  </property>
  <property>
    <code value="analyte-divisor" />
    <uri value="http://loinc.org/property/analyte-divisor" />
    <description value="The divisor part of the analyte, if present, i.e., after the slash and before the first carat" />
    <type value="Coding" />
  </property>
  <property>
    <code value="analyte-divisor-suffix" />
    <uri value="http://loinc.org/property/analyte-divisor-suffix" />
    <description value="The suffix part of the divisor, if present" />
    <type value="Coding" />
  </property>
  <property>
    <code value="challenge" />
    <uri value="http://loinc.org/property/challenge" />
    <description value="Second sub-part of the Component, i.e., after the first carat" />
    <type value="Coding" />
  </property>
  <property>
    <code value="adjustment" />
    <uri value="http://loinc.org/property/adjustment" />
    <description value="Third sub-part of the Component, i.e., after the second carat" />
    <type value="Coding" />
  </property>
  <property>
    <code value="count" />
    <uri value="http://loinc.org/property/count" />
    <description value="Fourth sub-part of the Component, i.e., after the third carat" />
    <type value="Coding" />
  </property>
  <property>
    <code value="time-core" />
    <uri value="http://loinc.org/property/time-core" />
    <description value="The primary part of the Time" />
    <type value="Coding" />
  </property>
  <property>
    <code value="time-modifier" />
    <uri value="http://loinc.org/property/time-modifier" />
    <description value="The modifier of the Time value, such as mean or max" />
    <type value="Coding" />
  </property>
  <property>
    <code value="system-core" />
    <uri value="http://loinc.org/property/system-core" />
    <description value="The primary part of the System, i.e., without the super system" />
    <type value="Coding" />
  </property>
  <property>
    <code value="super-system" />
    <uri value="http://loinc.org/property/super-system" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="analyte-gene" />
    <uri value="http://loinc.org/property/analyte-gene" />
    <description value="The specific gene represented in the analyte" />
    <type value="Coding" />
  </property>
  <property>
    <code value="category" />
    <uri value="http://loinc.org/property/category" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="search" />
    <uri value="http://loinc.org/property/search" />
    <description value="Synonyms, fragments, and other Parts that are linked to a term to enable more encompassing search results." />
    <type value="Coding" />
  </property>
  
  <property>
    <code value="rad-modality-modality-type" />
    <uri value="http://loinc.org/property/rad-modality-modality-type" />
    <description value="Modality is used to represent the device used to acquire imaging information." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-modality-modality-subtype" />
    <uri value="http://loinc.org/property/rad-modality-modality-subtype" />
    <description value="Modality subtype may be optionally included to signify a particularly common or evocative configuration of the modality." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-anatomic-location-region-imaged" />
    <uri value="http://loinc.org/property/rad-anatomic-location-region-imaged" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="rad-anatomic-location-imaging-focus" />
    <uri value="http://loinc.org/property/rad-anatomic-location-imaging-focus" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="rad-anatomic-location-laterality-presence" />
    <uri value="http://loinc.org/property/rad-anatomic-location-laterality-presence" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="rad-anatomic-location-laterality" />
    <uri value="http://loinc.org/property/rad-anatomic-location-laterality" />
    <description value="Radiology exam Laterality is specified as one of: Left, Right, Bilateral, Unilateral, Unspecified" />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-view-aggregation" />
    <uri value="http://loinc.org/property/rad-view-aggregation" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="rad-view-view-type" />
    <uri value="http://loinc.org/property/rad-view-view-type" />
    <description value="View type names specific views, such as 'lateral' or 'AP'." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-maneuver-maneuver-type" />
    <uri value="http://loinc.org/property/rad-maneuver-maneuver-type" />
    <description value="Maneuver type indicates an action taken with the goal of elucidating or testing a dynamic aspect of the anatomy." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-timing" />
    <uri value="http://loinc.org/property/rad-timing" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="rad-pharmaceutical-substance-given" />
    <uri value="http://loinc.org/property/rad-pharmaceutical-substance-given" />
    <description value="The Pharmaceutical Substance Given specifies administered contrast agents, radiopharmaceuticals, medications, or other clinically important agents and challenges during the imaging procedure." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-pharmaceutical-route" />
    <uri value="http://loinc.org/property/rad-pharmaceutical-route" />
    <description value="Route specifies the route of administration of the pharmaceutical." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-reason-for-exam" />
    <uri value="http://loinc.org/property/rad-reason-for-exam" />
    <description value="Reason for exam is used to describe a clinical indication or a purpose for the study." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-guidance-for-presence" />
    <uri value="http://loinc.org/property/rad-guidance-for-presence" />
    <description value="Guidance for.Presence indicates when a procedure is guided by imaging." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-guidance-for-approach" />
    <uri value="http://loinc.org/property/rad-guidance-for-approach" />
    <description value="Guidance for.Approach refers to the primary route of access used, such as percutaneous, transcatheter, or transhepatic." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-guidance-for-action" />
    <uri value="http://loinc.org/property/rad-guidance-for-action" />
    <description value="Guidance for.Action indicates the intervention performed, such as biopsy, aspiration, or ablation." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-guidance-for-object" />
    <uri value="http://loinc.org/property/rad-guidance-for-object" />
    <description value="Guidance for.Object specifies the target of the action, such as mass, abscess or cyst." />
    <type value="Coding" />
  </property>
  <property>
    <code value="rad-subject" />
    <uri value="http://loinc.org/property/rad-subject" />
    <description value="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 value="Coding" />
  </property>
  
  <property>
    <code value="document-kind" />
    <uri value="http://loinc.org/property/document-kind" />
    <description value="Characterizes the general structure of the document at a macro level." />
    <type value="Coding" />
  </property>
  <property>
    <code value="document-role" />
    <uri value="http://loinc.org/property/document-role" />
    <description value="Characterizes the training or professional level of the author of the document, but does not break down to specialty or subspecialty." />
    <type value="Coding" />
  </property>
  <property>
    <code value="document-setting" />
    <uri value="http://loinc.org/property/document-setting" />
    <description value="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 value="Coding" />
  </property>
  <property>
    <code value="document-subject-matter-domain" />
    <uri value="http://loinc.org/property/document-subject-matter-domain" />
    <description value="Characterizes the clinical domain that is the subject of the document. For example, Internal Medicine, Neurology, Physical Therapy, etc." />
    <type value="Coding" />
  </property>
  <property>
    <code value="document-type-of-service" />
    <uri value="http://loinc.org/property/document-type-of-service" />
    <description value="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 value="Coding" />
  </property>
  
  <property>
    <code value="answers-for" />
    <uri value="http://loinc.org/property/answers-for" />
    <description value="A LOINC Code for which this answer list is used." />
    <type value="Coding" />
  </property>
  
</CodeSystem>

name : LOINC

{

}

<!-- 
    If a version is specified: <version value="2.70"/>
     -->
<!-- 
    If a specific version is specified, the name should carry this information (e.g. LOINC_270).
     -->
<name value="LOINC" />