CIBMTR Reporting Implementation Guide
0.1.8 - Trial Use 1
CIBMTR Reporting Implementation Guide
0.1.8 - Trial Use 1
This page is part of the CIBMTR Reporting Implementation Guide (v0.1.8: Release Draft) 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
| Official URL: http://fhir.nmdp.org/ig/cibmtr-reporting/ValueSet/platelet-morphology-blood-vs | Version: 0.1.8 | |||
| Draft as of 2025-02-18 | Computable Name: PlateletMorphologyBloodVS | |||
Platelet morphology panel - Blood (58406-0)
References
Generated Narrative: ValueSet platelet-morphology-blood-vs
http://loinc.org| Code | Display |
| 7796-6 | Platelet clump [Presence] in Blood by Light microscopy |
| 18312-9 | Platelet satellitism [Presence] in Blood by Light microscopy |
| 33216-3 | Platelets agranular [Presence] in Blood by Light microscopy |
| 5908-9 | Giant platelets [Presence] in Blood by Light microscopy |
| 32146-3 | Platelets Large [Presence] in Blood by Light microscopy |
| 32208-1 | Platelets Small [Presence] in Blood by Light microscopy |
| 11125-2 | Platelet morphology finding [Identifier] in Blood |
Generated Narrative: ValueSet
Expansion from tx.fhir.org based on Loinc v2.78
This value set contains 7 concepts
| Code | System | Display (en-US) |
| 7796-6 | http://loinc.org | |
| 18312-9 | http://loinc.org | |
| 33216-3 | http://loinc.org | |
| 5908-9 | http://loinc.org | |
| 32146-3 | http://loinc.org | |
| 32208-1 | http://loinc.org | |
| 11125-2 | http://loinc.org |
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 |