HL7 Terminology (THO)
3.1.5 - Continuous Process Integration ( ci build ) World
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 3.1.5). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
|Active as of 2014-03-26|
@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-ActClassObservation"]; fhir:Resource.language [ fhir:value "en"]; fhir:DomainResource.text [ fhir:Narrative.status [ fhir:value "generated" ]; fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><ul><li>Include codes from <a href=\"CodeSystem-v3-ActClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a> where concept is-a <a href=\"CodeSystem-v3-ActClass.html#v3-ActClass-OBS\">OBS</a></li></ul></div>" ]; fhir:ValueSet.url [ fhir:value "http://terminology.hl7.org/ValueSet/v3-ActClassObservation"]; 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.1138126.96.36.19929" ] ]; fhir:ValueSet.version [ fhir:value "2.0.0"]; fhir:ValueSet.name [ fhir:value "ActClassObservation"]; fhir:ValueSet.title [ fhir:value "ActClassObservation"]; fhir:ValueSet.status [ fhir:value "active"]; fhir:ValueSet.date [ fhir:value "2014-03-26"^^xsd:date]; fhir:ValueSet.description [ fhir:value "**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.\r\n\r\n**Discussion:**\r\n\r\nStructurally, 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.\r\n\r\nAs 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.\r\n\r\nThe 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.\r\n\r\nAn 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.\r\n\r\nEven 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.\r\n\r\nClinical 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.\r\n\r\n**Examples:**\r\n\r\n * Recording the results of a Family History Assessment\r\n * Laboratory test and associated result\r\n * Physical exam test and associated result\r\n * Device temperature\r\n * Soil lead level"]; fhir:ValueSet.immutable [ fhir:value "true"^^xsd:boolean]; 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.filter [ fhir:index 0; fhir:ValueSet.compose.include.filter.property [ fhir:value "concept" ]; fhir:ValueSet.compose.include.filter.op [ fhir:value "is-a" ]; fhir:ValueSet.compose.include.filter.value [ fhir:value "OBS" ] ] ] ]. # - ontology header ------------------------------------------------------------ a owl:Ontology; owl:imports fhir:fhir.ttl.