Repositorio de Reportes de Biopsias Oncológicas
0.1.1-draft - STU1

Repositorio de Reportes de Biopsias Oncológicas, published by Unidad de Interoperabilidad - MINSAL. This guide is not an authorized publication; it is the continuous build for version 0.1.1-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Minsal-CL/R2BO/ and changes regularly. See the Directory of published versions

## ValueSet: Set de Valores Categoría TNM Patológico Nodos Regional (Experimental)

Official URL: https://interoperabilidad.minsal.cl/fhir/ig/r2bo/ValueSet/r2bo-tnm-categoria-nodo-regional-patologico-vs | Version: 0.1.1-draft
Standards status: Informative | Computable Name: TNMCategoriaPatologicoNodosRegionalVS
Copyright/Legal: This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement The SNOMED International IPS Terminology is distributed by International Health Terminology Standards Development Organisation, trading as SNOMED International, and is subject the terms of the Creative Commons Attribution 4.0 International Public License. For more information, see SNOMED IPS Terminology The HL7 International IPS implementation guides incorporate SNOMED CT®, used by permission of the International Health Terminology Standards Development Organisation, trading as SNOMED International. SNOMED CT was originally created by the College of American Pathologists. SNOMED CT is a registered trademark of the International Health Terminology Standards Development Organisation, all rights reserved. Implementers of SNOMED CT should review usage terms or directly contact SNOMED International: info@snomed.org

Set de valores utilizados para la categoría TNM patológico Nodos Regional

References

- Perfil de Categoria TNM Nodos Regional

### Logical Definition (CLD)

- Include codes from`http://snomed.info/sct` version Not Stated (use latest from terminology server) where concept descends from 1222590007 (American Joint Committee on Cancer pathological N category allowable value)

### Expansion

Expansion from tx.ontoserver.csiro.au based on SNOMED CT International edition 01-Jul 2025

This value set contains 20 concepts

System | Code | Display (en) | JSON | XML
`http://snomed.info/sct` | 1229947003 | pN0 (AJCC) |  |
`http://snomed.info/sct` | 1229949000 | pN0(i+) (AJCC) |  |
`http://snomed.info/sct` | 1229950000 | pN0(mol+) (AJCC) |  |
`http://snomed.info/sct` | 1229948008 | pN0a (AJCC) |  |
`http://snomed.info/sct` | 1229951001 | pN1 (AJCC) |  |
`http://snomed.info/sct` | 1229954009 | pN1a (AJCC) |  |
`http://snomed.info/sct` | 1229953003 | pN1a(sn) (AJCC) |  |
`http://snomed.info/sct` | 1229955005 | pN1b (AJCC) |  |
`http://snomed.info/sct` | 1229956006 | pN1c (AJCC) |  |
`http://snomed.info/sct` | 1229952008 | pN1mi (AJCC) |  |
`http://snomed.info/sct` | 1229957002 | pN2 (AJCC) |  |
`http://snomed.info/sct` | 1229959004 | pN2a (AJCC) |  |
`http://snomed.info/sct` | 1229960009 | pN2b (AJCC) |  |
`http://snomed.info/sct` | 1229961008 | pN2c (AJCC) |  |
`http://snomed.info/sct` | 1229958007 | pN2mi (AJCC) |  |
`http://snomed.info/sct` | 1229962001 | pN3 (AJCC) |  |
`http://snomed.info/sct` | 1229963006 | pN3a (AJCC) |  |
`http://snomed.info/sct` | 1229964000 | pN3b (AJCC) |  |
`http://snomed.info/sct` | 1229965004 | pN3c (AJCC) |  |
`http://snomed.info/sct` | 1229945006 | pNX (AJCC) |  |

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