| Official URL: https://fhir.kbv.de/ValueSet/KBV_VS_MIO_LAB_Observation_Status | Version: 1.0.0-update | |||
| Draft as of 2026-06-19 | Computable Name: KBV_VS_MIO_LAB_Observation_Status | |||
Copyright/Legal: Im folgenden Profil können Codes aus den Codesystemen Snomed, Loinc oder Ucum enthalten sein, die dem folgenden Urheberrecht unterliegen: This material includes SNOMED Clinical Terms® (SNOMED CT®) which is used by permission of SNOMED International. All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists. SNOMED and SNOMED CT are registered trademarks of SNOMED International. Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license. 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. This product includes all or a portion of the UCUM table, UCUM codes, and UCUM definitions or is derived from it, subject to a license from Regenstrief Institute, Inc. and The UCUM Organization. Your use of the UCUM table, UCUM codes, UCUM definitions also is subject to this license, a copy of which is available at http://unitsofmeasure.org. The current complete UCUM table, UCUM Specification are available for download at http://unitsofmeasure.org. The UCUM table and UCUM codes are copyright © 1995-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. THE UCUM TABLE (IN ALL FORMATS), UCUM DEFINITIONS, AND SPECIFICATION ARE PROVIDED “AS IS.” ANY EXPRESS OR IMPLIED WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. |
||||
Dieses Valueset enthält die Codes zur Beschreibung von Status Laboruntersuchung.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/observation-status version 📍4.0.1| Code | Display | Definition |
| registered | Registered | The existence of the observation is registered, but there is no result yet available. |
| preliminary | Preliminary | This is an initial or interim observation: data may be incomplete or unverified. |
| final | Final | The observation is complete and there are no further actions needed. Additional information such "released", "signed", etc would be represented using [Provenance](provenance.html) which provides not only the act but also the actors and dates and other related data. These act states would be associated with an observation status of `preliminary` until they are all completed and then a status of `final` would be applied. |
| amended | Amended | Subsequent to being Final, the observation has been modified subsequent. This includes updates/new information and corrections. |
| corrected | Corrected | Subsequent to being Final, the observation has been modified to correct an error in the test result. |
| cancelled | Cancelled | The observation is unavailable because the measurement was not started or not completed (also sometimes called "aborted"). |
| entered-in-error | Entered in Error | The observation has been withdrawn following previous final release. This electronic record should never have existed, though it is possible that real-world decisions were based on it. (If real-world activity has occurred, the status should be "cancelled" rather than "entered-in-error".). |
Expansion performed internally based on codesystem ObservationStatus v4.0.1 (CodeSystem)
This value set contains 7 concepts
| System | Code | Display (de) | Definition | JSON | XML |
http://hl7.org/fhir/observation-status | registered | The existence of the observation is registered, but there is no result yet available. | |||
http://hl7.org/fhir/observation-status | preliminary | This is an initial or interim observation: data may be incomplete or unverified. | |||
http://hl7.org/fhir/observation-status | final | The observation is complete and there are no further actions needed. Additional information such "released", "signed", etc would be represented using Provenance which provides not only the act but also the actors and dates and other related data. These act states would be associated with an observation status of | |||
http://hl7.org/fhir/observation-status | amended | Subsequent to being Final, the observation has been modified subsequent. This includes updates/new information and corrections. | |||
http://hl7.org/fhir/observation-status | corrected | Subsequent to being Final, the observation has been modified to correct an error in the test result. | |||
http://hl7.org/fhir/observation-status | cancelled | The observation is unavailable because the measurement was not started or not completed (also sometimes called "aborted"). | |||
http://hl7.org/fhir/observation-status | entered-in-error | The observation has been withdrawn following previous final release. This electronic record should never have existed, though it is possible that real-world decisions were based on it. (If real-world activity has occurred, the status should be "cancelled" rather than "entered-in-error".). |
Additional Designations
| Code | Other Display (null) |
| registered | Registered |
| preliminary | Preliminary |
| final | Final |
| amended | Amended |
| corrected | Corrected |
| cancelled | Cancelled |
| entered-in-error | Entered in Error |
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 |