LOINC – IVD Test Code (LIVD) Mapping, published by HL7 International - Orders and Observations Work Group. This is not an authorized publication; it is the continuous build for version 0.3.0). This version is based on the current content of https://github.com/HL7/livd/ and changes regularly. See the Directory of published versions
Summary
Defining URL: | http://hl7.org/fhir/uv/livd/ValueSet/livd-bundle-type |
Version: | 0.1.0 |
Name: | LivdBundleTypeVS |
Title: | Allowed types of bundles for the LIVD catalog |
Status: | Draft as of 7/28/19 |
Definition: | Allowed types of bundles for the LIVD catalog |
Source Resource: | XML / JSON / Turtle |
References
http://hl7.org/fhir/bundle-type
Code | Display | Definition |
collection | Collection | The bundle is a set of resources collected into a single package for ease of distribution that imposes no processing obligations or behavioral rules beyond persistence. |
transaction | Transaction | The bundle is a transaction - intended to be processed by a server as an atomic commit. |
This value set contains 2 concepts
Expansion based on BundleType v4.0.1 (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/bundle-type
Code | Display | Definition |
collection | Collection | The bundle is a set of resources collected into a single package for ease of distribution that imposes no processing obligations or behavioral rules beyond persistence. |
transaction | Transaction | The bundle is a transaction - intended to be processed by a server as an atomic commit. |
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 |
Source | 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 |