HL7 Terminology (THO)
5.4.0 - Publication International flag

This page is part of the HL7 Terminology (v5.4.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: hl7VS-natureOfServiceTestObservation

Official URL: http://terminology.hl7.org/ValueSet/v2-0174 Version: 2.0.0
Active as of 2019-12-01 Responsible: Health Level Seven International Computable Name: Hl7VSNatureOfServiceTestObservation
Other Identifiers: id: Uniform Resource Identifier (URI)#urn:oid:2.16.840.1.113883.21.102

Copyright/Legal: This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license

Concepts specifying an identification of a test battery, an entire functional procedure or study, a single test value (observation), multiple test batteries or functional procedures as an orderable unit (profile), or a single test value (observation) calculated from other independent observations, typically used as an indicator for Master Files.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 5 concepts

Expansion based on codesystem natureOfServiceTestObservation v2.0.0 (CodeSystem)

CodeSystemDisplayDefinition
  Phttp://terminology.hl7.org/CodeSystem/v2-0174Profile or battery consisting of many independent atomic observations (e.g., SMA12, electrolytes), usually done at one instrument on one specimen

Profile or battery consisting of many independent atomic observations (e.g., SMA12, electrolytes), usually done at one instrument on one specimen

  Fhttp://terminology.hl7.org/CodeSystem/v2-0174Functional procedure that may consist of one or more interrelated measures (e.g., glucose tolerance test, creatinine clearance), usually done at different times and/or on different specimens

Functional procedure that may consist of one or more interrelated measures (e.g., glucose tolerance test, creatinine clearance), usually done at different times and/or on different specimens

  Ahttp://terminology.hl7.org/CodeSystem/v2-0174Atomic service/test/observation (test code or treatment code)

Atomic service/test/observation (test code or treatment code)

  Shttp://terminology.hl7.org/CodeSystem/v2-0174Superset-a set of batteries or procedures ordered under a single code unit but processed as separate batteries (e.g., routines = CBC, UA, electrolytes)<p>This set indicates that the code being described is used to order multiple service/test/observation b

Superset—a set of batteries or procedures ordered under a single code unit but processed as separate batteries (e.g., routines = CBC, UA, electrolytes) This set indicates that the code being described is used to order multiple service/test/observation batteries. For example, a client who routinely orders a CBC, a differential, and a thyroxine as an outpatient profile might use a single, special code to order all three test batteries, instead of having to submit three separate order codes.

  Chttp://terminology.hl7.org/CodeSystem/v2-0174Single observation calculated via a rule or formula from other independent observations (e.g., Alveolar-arterial ratio, cardiac output)

Single observation calculated via a rule or formula from other independent observations (e.g., Alveolar-arterial ratio, cardiac output)

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.