Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG, published by HL7 International / Clinical Interoperability Council. This is not an authorized publication; it is the continuous build for version 1.0.0. This version is based on the current content of https://github.com/HL7/fhir-registry-protocols-ig/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/registry-protocols/ValueSet/ValvularStenosis | Version: 1.0.0 | |||
Active as of 2023-11-14 | Computable Name: ValvularStenosis | |||
Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc |
Loinc codes for Valvular Stenosis
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://loinc.org
Code | Display |
77916-5 | Mitral valve Stenosis degree by US |
78183-1 | Pulmonic valve Stenosis degree by US |
77912-4 | Aortic valve Stenosis degree by US |
This value set contains 3 concepts
Expansion based on:
Code | System | Display |
77916-5 | http://loinc.org | Mitral valve Stenosis degree by US |
78183-1 | http://loinc.org | Pulmonic valve Stenosis degree by US |
77912-4 | http://loinc.org | Aortic valve Stenosis degree by US |
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 |