LOINC – IVD Test Code (LIVD) Mapping 0.2.0 - STU Ballot 1

This page is part of the Loinc/IVD Mapping FHIR IG (v0.2.0: STU 1 (FHIR R4) Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Value Set /ValueSet/livd-bundle-type

Summary

Defining URL:http://hl7.org/fhir/uv/livd/ValueSet/livd-bundle-type
Version:0.2.0
Name:LivdBundleTypeVS
Definition:

Allowed types of bundles for the LIVD catalog

Source Resource:XML / JSON / Turtle

Content Logical Definition

Allowed types of bundles for the LIVD catalog

Allowed types of bundles for the LIVD catalog

This value set includes codes from the following code systems:

  • Include these codes as defined in http://hl7.org/fhir/bundle-type
    CodeDisplay
    collectionCollectionThe 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.
    transactionTransactionThe bundle is a transaction - intended to be processed by a server as an atomic commit.

 

Expansion

This value set contains 2 concepts

Expansion based on http://hl7.org/fhir/bundle-type version 4.0.0

All codes from system http://hl7.org/fhir/bundle-type

CodeDisplayDefinition
collectionCollectionThe 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.
transactionTransactionThe 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