Release 5 Draft Ballot

This page is part of the FHIR Specification (v4.6.0: R5 Draft Ballot - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.4.1.629 Value Set http://hl7.org/fhir/ValueSet/knowledge-representation-level

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined at http://www.hl7.org/Special/committees/dss/index.cfm .

Summary

Defining URL:http://hl7.org/fhir/ValueSet/knowledge-representation-level
Version:4.6.0
Name:knowledgeRepresentationLevel
Title:Knowledge Representation Level
Definition:

A knowledge representation level, narrative, semi-structured, structured, and executable

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.0 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.629.1 Content Logical Definition

 

4.4.1.629.2 Expansion

This expansion generated 15 Apr 2021

This value set contains 4 concepts

Expansion based on Knowledge Representation Level v4.6.0 (CodeSystem)

All codes from system http://hl7.org/fhir/CodeSystem/knowledge-representation-level

CodeDisplayDefinition
narrativeNarrativeThe knowledge is expressed as narrative text, affording broad shareability, but limited computability. The knowledge is typically expressed independent of delivery method (modality), technology platform, and implementation site. Knowledge at this level is typically authored by guideline developers for a broad range of purposes including communication of policy, synthesis of evidence, and dissemination of best-practices.
semi-structuredSemi-StructuredThe knowledge is expressed as organized text, often accompanied by diagrams such as flow charts and decision tables, affording broad shareability and moderate computability. The knowledge is typically expressed independent of delivery method (modality), technology platform, and implementation site. Knowledge at this level is typically authored by clinical domain experts for the purpose of communication the description of recommendations for implementation in various modalities.
structuredStructuredThe knowledge is expressed in a structured way that is interpretable by computer, including being coded using standard terminologies and specifications for the representation of structured content, affording broad shareability and high computability. The knowledge is typically expressed independent of delivery method (modality), technology platform, and implementation site. Knowledge at this level is typically authored by knowledge engineersto enable precise communication and validation of the recommendations.
executableExecutableThe knowledge is expressed in a way that is coded and interpretable by CDS systems using a variety of formats, affording direct executability, but potentially limited shareability. The knowledge is typically expressed focusing on a specific delivery method (modality), technology platform, and implementation environment. Knowledge at this level is typically built and developed by implementers working in specific technology platforms, for the purpose of implementation at a specific site, though affordances such as computable mappings and configuration capabilities can broaden the usability of the knowledge artifact.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code