Repositorio de Reportes de Biopsias Oncológicas
0.1.0 - ci-build
Repositorio de Reportes de Biopsias Oncológicas
0.1.0 - ci-build
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.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Minsal-CL/riap/ and changes regularly. See the Directory of published versions
| Official URL: https://interoperabilidad.minsal.cl/fhir/ig/r2bo/ValueSet/r2bo-observaciones-biopsia-VS | Version: 0.1.0 | |||
| Standards status: Informative | Computable Name: ObservacionesBiopsiaVS | |||
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 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 |
||||
Observaciones realizadas durante el informe de biopsia
References
This value set includes codes based on the following rules:
http://snomed.info/sct| Code | Display |
| 399588009 | Pathologic TNM stage grouping |
| 371513001 | Presence of direct invasion by primary malignant neoplasm to nerve |
| 405921002 | Percentage of neoplasm involved by necrosis |
| 371509008 | Status of peritumoral lymphocyte response |
| 444696007 | Status of specimen involvement by multifocal invasion |
| 396631001 | Surgical margin observable |
| 396324006 | Surgical margin involved by neoplasm in excised tissue specimen |
http://loinc.org
| Code | Display |
| 102034-6 | Pathology report microscopic observation in Specimen |
| 74574-5 | Macroscopic observation [Interpretation] in Specimen Narrative |
| 33739-4 | Lymphatic.small vessel.invasion [Identifier] in Specimen by CAP cancer protocols |
| 33740-2 | Venous.large vessel.invasion [Identifier] in Specimen by CAP cancer protocols |
| 21889-1 | Size Tumor |
| 42030-7 | Multiple tumors reported as single primary Cancer |
| 92831-7 | Lymph nodes with metastasis [#] in Cancer specimen |
| 81168-7 | Site of adjacent organ or tissue involvement Cancer specimen |
| 84891-1 | Pathology report post neoadjuvant therapy assessment in Specimen |
| 33737-8 | Distance of tumor from closest margin |
No Expansion for this valueset (Unknown Code System)
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 |