HL7 Terminology (THO)
5.0.0 - Publication International flag

This page is part of the HL7 Terminology (v5.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

: x_LabProcessClassCodes - TTL Representation

Active as of 2014-03-26

Raw ttl | Download


@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

 a fhir:ValueSet;
  fhir:nodeRole fhir:treeRoot;
  fhir:Resource.id [ fhir:value "v3-xLabProcessClassCodes"];
  fhir:Resource.language [ fhir:value "en"];
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "extensions" ];
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-ACSN\">ACSN</a></td><td>accession</td><td>A unit of work, a grouper of work items as defined by the system performing that work. Typically some laboratory order fulfillers communicate references to accessions in their communications regarding laboratory orders. Often one or more specimens are related to an accession such that in some environments the accession number is taken as an identifier for a specimen (group).</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-CONTREG\">CONTREG</a></td><td>container registration</td><td>An Act where a container is registered either via an automated sensor, such as a barcode reader, or by manual receipt</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-OBS\">OBS</a></td><td>observation</td><td>**Description:**An act that is intended to result in new information about a subject. The main difference between Observations and other Acts is that Observations have a value attribute. The **code** attribute of Observation and the **value** attribute of Observation must be considered in combination to determine the semantics of the observation.<br/><br/>**Discussion:**<br/><br/>Structurally, many observations are name-value-pairs, where the Observation.code (inherited from Act) is the name and the Observation.value is the value of the property. Such a construct is also known as a variable (a named feature that can assume a value) hence, the Observation class is always used to hold generic name-value-pairs or variables, even though the variable valuation may not be the result of an elaborate observation method. It may be a simple answer to a question or it may be an assertion or setting of a parameter.<br/><br/>As with all Act statements, Observation statements describe what was done, and in the case of Observations, this includes a description of what was actually observed (results or answers); and those results or answers are part of the observation and not split off into other objects.<br/><br/>The method of action is asserted by the Observation classCode or its subclasses at the least granular level, by the Observation.code attribute value at the medium level of granularity, and by the attribute value of observation.methodCode when a finer level of granularity is required. The method in whole or in part may also appear in the attribute value of Observation.value when using coded data types to express the value of the attribute. Relevant aspects of methodology may also be restated in value when the results themselves imply or state a methodology.<br/><br/>An observation may consist of component observations each having their own Observation.code and Observation.value. In this case, the composite observation may not have an Observation.value for itself. For instance, a white blood cell count consists of the sub-observations for the counts of the various granulocytes, lymphocytes and other normal or abnormal blood cells (e.g., blasts). The overall white blood cell count Observation itself may therefore not have a value by itself (even though it could have one, e.g., the sum total of white blood cells). Thus, as long as an Act is essentially an Act of recognizing and noting information about a subject, it is an Observation, regardless of whether it has a simple value by itself or whether it has sub-observations.<br/><br/>Even though observations are professional acts (see Act) and as such are intentional actions, this does not require that every possible outcome of an observation be pondered in advance of it being actually made. For instance, differential white blood cell counts (WBC) rarely show blasts, but if they do, this is part of the WBC observation even though blasts might not be predefined in the structure of a normal WBC.<br/><br/>Clinical documents commonly have Subjective and Objective findings, both of which are kinds of Observations. In addition, clinical documents commonly contain Assessments, which are also kinds of Observations. Thus, the establishment of a diagnosis is an Observation.<br/><br/>**Examples:**<br/><br/> *  Recording the results of a Family History Assessment<br/> *  Laboratory test and associated result<br/> *  Physical exam test and associated result<br/> *  Device temperature<br/> *  Soil lead level</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-PROC\">PROC</a></td><td>procedure</td><td>An Act whose immediate and primary outcome (post-condition) is the alteration of the physical condition of the subject.<br/><br/>*Examples:* : Procedures may involve the disruption of some body surface (e.g. an incision in a surgical procedure), but they also include conservative procedures such as reduction of a luxated join, chiropractic treatment, massage, balneotherapy, acupuncture, shiatsu, etc. Outside of clinical medicine, procedures may be such things as alteration of environments (e.g. straightening rivers, draining swamps, building dams) or the repair or change of machinery etc.</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-SPCTRT\">SPCTRT</a></td><td>specimen treatment</td><td>A procedure or treatment performed on a specimen to prepare it for analysis</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-SPECCOLLECT\">SPECCOLLECT</a></td><td>Specimen Collection</td><td>A procedure for obtaining a specimen from a source entity.</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-STORE\">STORE</a></td><td>storage</td><td>The act of putting something away for safe keeping. The &quot;something&quot; may be physical object such as a specimen, or information, such as observations regarding a specimen.</td></tr><tr><td><a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-TRNS\">TRNS</a></td><td>transportation</td><td>Transportation is the moving of a payload (people or material) from a location of origin to a destination location. Thus, any transport service has the three target instances of type payload, origin, and destination, besides the targets that are generally used for any service (i.e., performer, device, etc.)</td></tr></table></li></ul></div>"
  ];
  fhir:DomainResource.extension [
     fhir:index 0;
     fhir:Element.extension [
       fhir:index 0;
       fhir:Extension.url [ fhir:value "name" ];
       fhir:Extension.valueString [ fhir:value "Name:Class" ]     ], [
       fhir:index 1;
       fhir:Extension.url [ fhir:value "value" ];
       fhir:Extension.valueString [ fhir:value "LabProcess" ]     ];
     fhir:Extension.url [ fhir:value "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp" ]
  ];
  fhir:ValueSet.url [ fhir:value "http://terminology.hl7.org/ValueSet/v3-xLabProcessClassCodes"];
  fhir:ValueSet.identifier [
     fhir:index 0;
     fhir:Identifier.system [ fhir:value "urn:ietf:rfc:3986" ];
     fhir:Identifier.value [ fhir:value "urn:oid:2.16.840.1.113883.1.11.19657" ]
  ];
  fhir:ValueSet.version [ fhir:value "2.0.0"];
  fhir:ValueSet.name [ fhir:value "XLabProcessClassCodes"];
  fhir:ValueSet.title [ fhir:value "x_LabProcessClassCodes"];
  fhir:ValueSet.status [ fhir:value "active"];
  fhir:ValueSet.experimental [ fhir:value "false"^^xsd:boolean];
  fhir:ValueSet.date [ fhir:value "2014-03-26"^^xsd:date];
  fhir:ValueSet.description [ fhir:value "***No description***"];
  fhir:ValueSet.compose [
     fhir:ValueSet.compose.include [
       fhir:index 0;
       fhir:ValueSet.compose.include.system [ fhir:value "http://terminology.hl7.org/CodeSystem/v3-ActClass" ];
       fhir:ValueSet.compose.include.concept [
         fhir:index 0;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "ACSN" ]       ], [
         fhir:index 1;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "CONTREG" ]       ], [
         fhir:index 2;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "OBS" ]       ], [
         fhir:index 3;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "PROC" ]       ], [
         fhir:index 4;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "SPCTRT" ]       ], [
         fhir:index 5;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "SPECCOLLECT" ]       ], [
         fhir:index 6;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "STORE" ]       ], [
         fhir:index 7;
         fhir:ValueSet.compose.include.concept.code [ fhir:value "TRNS" ]       ]     ]
  ].

# - ontology header ------------------------------------------------------------

 a owl:Ontology;
  owl:imports fhir:fhir.ttl.