Publish-box (todo)
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/knowledge-representation-level
|
Version: 6.0.0-ballot2 | |||
active as of 2019-07-21 | Computable Name: KnowledgeRepresentationLevel | |||
Flags: | OID: 2.16.840.1.113883.4.642.3.3221 |
This value set is used in the following places:
A knowledge representation level, narrative, semi-structured, structured, and executable
Generated Narrative: ValueSet knowledge-representation-level
Last updated: 2024-08-12T16:52:12.437+08:00
Profile: Shareable ValueSet
http://hl7.org/fhir/CodeSystem/knowledge-representation-level
This expansion generated 12 Aug 2024
Generated Narrative: ValueSet
Last updated: 2024-08-12T16:52:12.437+08:00
Profile: Shareable ValueSet
Expansion based on codesystem Knowledge Representation Level v6.0.0-ballot2 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
narrative | http://hl7.org/fhir/CodeSystem/knowledge-representation-level | Narrative | The 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-structured | http://hl7.org/fhir/CodeSystem/knowledge-representation-level | Semi-Structured | The 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. |
structured | http://hl7.org/fhir/CodeSystem/knowledge-representation-level | Structured | The 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. |
executable | http://hl7.org/fhir/CodeSystem/knowledge-representation-level | Executable | The 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:
Lvl | A 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 |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |