MyHealth@Eu Laboratory Report
0.0.1 - qa-preview 150

MyHealth@Eu Laboratory Report - Local Development build (v0.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

ValueSet: eHDSI Laboratory Study Types with exceptions

Official URL: http://fhir.ehdsi.eu/laboratory/ValueSet/eHDSILabStudyTypeWithExceptions Version: 0.0.1
Standards status: Draft Maturity Level: 1 Computable Name: EHDSILabStudyTypeWithExceptions

Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, 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

eHDSI Laboratory Study Types. Notes: Note 1: 26436-6 (Laboratory studies) enables issuing a report putting together observations from multiple specialties (disciplines) in the same text block, allowing delivery of a global interpretation comment at the end of the text block that will be rendered at the end of the report. Note 2: Mycology and parasitology, as well as bacteriology, are part of the 18725-2 (Microbiology studies (set)) studies. Note 3: Virology MAY be included in 18725-2 (MICROBIOLOGY STUDIES) or 18727-8 (SEROLOGY STUDIES) or split between both study types, depending upon the Content Creator Actor’s choice. It includes also exceptional values.

References

Logical Definition (CLD)

Generated Narrative: ValueSet eHDSILabStudyTypeWithExceptions

This value set includes codes based on the following rules:

 

Expansion

Generated Narrative: ValueSet

This value set contains 10 concepts

CodeSystemDisplayDefinition
  OTHhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorother

**Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).

Usage Notes: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.

With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.

  UNChttp://terminology.hl7.org/CodeSystem/v3-NullFlavorun-encoded

Description: The actual value has not yet been encoded within the approved value domain.

Example: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.

Usage Notes: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.

Data type properties such as original text and translations may be present when this null flavor is included.

  UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorunknown

**Description:**A proper value is applicable, but not known.

Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:

  1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown')
  2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
  18717-9http://loinc.orgBlood bank studies (set)
  18719-5http://loinc.orgChemistry studies (set)
  18722-9http://loinc.orgFertility studies (set)
  18723-7http://loinc.orgHematology studies (set)
  18725-2http://loinc.orgMicrobiology studies (set)
  18728-6http://loinc.orgToxicology studies (set)
  26436-6http://loinc.orgLaboratory studies (set)

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