eHealth Infrastructure
3.3.0 - release Denmark flag

This page is part of the FUT Infrastructure (v3.3.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: Library Type (Experimental)

Official URL: http://ehealth.sundhed.dk/vs/library-type Version: 3.3.0
Active as of 2019-08-27 Computable Name: LibraryType

http://terminology.hl7.org/CodeSystem/library-type + automated-processing

References

Logical Definition (CLD)

Generated Narrative: ValueSet ehealth-library-type

This value set includes codes based on the following rules:

 

Expansion

Generated Narrative: ValueSet

This value set contains 5 concepts

CodeSystemDisplayDefinition
  logic-libraryhttp://terminology.hl7.org/CodeSystem/library-typeLogic Library

The resource is a shareable library of formalized knowledge.

  model-definitionhttp://terminology.hl7.org/CodeSystem/library-typeModel Definition

The resource is a definition of an information model.

  asset-collectionhttp://terminology.hl7.org/CodeSystem/library-typeAsset Collection

The resource is a collection of knowledge assets.

  module-definitionhttp://terminology.hl7.org/CodeSystem/library-typeModule Definition

The resource defines the dependencies, parameters, and data requirements for a particular module or evaluation context.

  automated-processinghttp://ehealth.sundhed.dk/cs/library-typeAutomated Processing

The resource defines an evaluation context for automated processing

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