FLUTE Cross-border Prostate Cancer Data Standard Guide
0.1.0 - ci-build
FLUTE Cross-border Prostate Cancer Data Standard Guide, published by Flute Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/flute/ and changes regularly. See the Directory of published versions
| Official URL: http://hl7.eu/fhir/ig/flute/ValueSet/VS-GleasonGrade | Version: 0.1.0 | |||
| Draft as of 2025-11-05 | Computable Name: VS_GleasonGrade | |||
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 |
||||
Gleason Grade for Prostate Cancer
References
Expansion from tx.fhir.org based on Loinc v2.81
This value set contains 5 concepts
| System | Code | Display (en) | JSON | XML |
http://loinc.org | LA30794-4 | ISUP Grade (Grade Group) 1 (Gleason score <=6) | ||
http://loinc.org | LA30795-1 | ISUP Grade (Grade Group) 2 (Gleason score 3+4=7) | ||
http://loinc.org | LA30796-9 | ISUP Grade (Grade Group) 3 (Gleason score 4+3=7) | ||
http://loinc.org | LA30797-7 | ISUP Grade (Grade Group) 4 (Gleason score 8) | ||
http://loinc.org | LA30798-5 | ISUP Grade (Group Group) 5 (Gleason score 9-10) |
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 |