This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Orders and Observations Work Group | Maturity Level: 1 | Draft | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/bodystructure-laterality
|
Version: 6.0.0-ballot2 | |||
draft as of 2024-11-11 | Computable Name: BodystructureLaterality | |||
Flags: Experimental | OID: |
This value set is used in the following places:
SNOMED-CT concepts modifying the laterality of the anatomic location
Generated Narrative: ValueSet bodystructure-laterality
Last updated: 2024-11-11T07:23:23.182Z
Profile: Shareable ValueSet
http://snomed.info/sct
Code | Display |
7771000 | Left (qualifier value) |
24028007 | Right (qualifier value) |
51440002 | Bilateral |
This expansion generated 11 Nov 2024
Generated Narrative: ValueSet
Last updated: 2024-11-11T07:23:23.182Z
Profile: Shareable ValueSet
Expansion based on SNOMED CT International edition 01-Aug 2024
This value set contains 3 concepts
Code | System | Display | http://terminology.hl7.org/CodeSystem/designation-usage#display |
7771000 | http://snomed.info/sct | Left | Left (qualifier value) |
24028007 | http://snomed.info/sct | Right | Right (qualifier value) |
51440002 | http://snomed.info/sct | Right and left | Bilateral |
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 |