1 Introducción
1.1 Generalidades
La terminología SNOMED CT provee un lenguaje común y un medio consistente para indizar, almacenar, recuperar y agregar datos clínicos de diferentes especialidades y ámbitos de atención de la salud.
SNOMED International mantiene el diseño técnico y la arquitectura de la terminología, y el contenido de su núcleo (que incluye las tablas de conceptos, de descripciones, de relaciones y de historial, así como referencias cruzadas a la CIE) y la documentación técnica relacionada.
1.2 Propósito
Este documento presenta una breve descripción de los cambios realizados en el contenido de la Edición Internacional de SNOMED Clinical Terms® (SCT) de abril de 2018.
También incluye anotaciones técnicas que detallan algunos problemas conocidos del contenido o aspectos técnicos con causas identificadas pero cuya solución aún no se ha implementado.
Este documento está disponible junto con la Edición en Castellano correspondiente a abril de 2018.
1.3 Alcance
Este documento está escrito para los fines mencionados anteriormente y no incluye detalles sobre las especificaciones técnicas para SNOMED CT ni abarca cada cambio realizado durante la publicación
1.4 A quién se dirige este documento
Este documento está dirigido a los Centros Nacionales, Centros Colaboradores de la OMS-FCI, proveedores de historias clínicas electrónicas, desarrolladores de terminologías y administradores que deseen conocer los cambios incorporados a la Edición en Castellano de SNOMED CT de abril de 2018.
2 Actividad de desarrollo de contenido
2.1 Resumen
La mejora continua de la calidad y del contenido existente se basa en las solicitudes recibidas a través del Sistema de Presentación de Solicitudes (SPS). Se inició una revisión de los patrones precoordinados que frenan el progreso de los tickets incluidos en el SPS y continuará durante todo el año 2018.
También se está llevando a cabo una revisión de las solicitudes que actualmente se encuentran en el estado "In Inception" en la herramienta SPS y, cuando es factible avanzar una solicitud antes de resolver el problema planteado se identifica la solicitud para avanzarla en el proceso. Con este trabajo (y la revisión de los patrones precoordinados) la cantidad de solicitudes con estado "In Inception" ha disminuido en más de 1000.La tarea continuará durante 2018.
La Edición Internacional de enero de 2018 continuó el trabajo impulsado por las contribuciones del proyecto de Terminología Médica Convergente de Kaiser Permanente (CMT), la Agencia Global Medical Device Nomenclature Agency (GMDNA, Nomenclatura Global de Dispositivos Médicos), la Edición Beta de la CIE-11 de la Organización Mundial de la Salud (OMS) y la Clasificación Internacional de Prácticas de Enfermería (ICNP®) para agregar nuevo contenido a SNOMED CT.
Además, proyectos prioritarios identificados por los miembros dieron lugar a mejoras en la jerarquía de anatomía, mientras que otros cambios igualmente impulsados por proyectos se reflejaron en numerosos agregados y mejoras al contenido existente, que se detallan más adelante.
A partir de la edición internacional de enero de 2018, ya no se permitirá especificar como motivo de inactivación del contenido "LIMITADO/ERA_UN/UNA". El conjunto de referencias (refset) de la asociación ERA UN(A) ya no se actualizará a partir de esa fecha.
Antecedentes
En 2015, Grupo Asesor Editorial propuso inactivar la relación 159083000 |ERA UN(A) (atributo)| y dejar de actualizar el 900000000000528000 |conjunto de referencias de asociación ERA UN/UNA (metadato fundacional)|.
Desde que se formularon estas recomendaciones se creó una propuesta formal para que el mediante un abordaje técnico se actualizara la terminología por lotes y se envió un aviso de la inactivación propuesta a la Comunidad de Práctica.
La implementación de los cambios se pospuso de acuerdo con los comentarios sobre la utilidad para la implementación y el impacto potencial para los clientes que aún utilizaban RF1.
El tema se discutió nuevamente en la reunión de octubre de 2017 del Grupo Asesor Editorial en Bratislava. Debido a que los requisitos y problemas potenciales pueden deducirse extrayendo tal información del formato de publicación RF2, se recomendó tomar la decisión después de la publicación de enero de 2018
2.2 Mejora en la calidad del contenido
En total, en la Edición en Castellano se crearon 4979 conceptos y 23.892 descripciones nuevas
Estadística de SCT | Nuevos conceptos agregados |
---|---|
Concepto de SNOMED CT (SNOMED RT+CTV3) | 4979 |
Estructura corporal (estructura corporal) | 5994 |
Hallazgo clínico (hallazgo) | 2005 |
Evento (evento) | 12 |
Entidad observable (entidad observable) | 52 |
Organismo (organismo) | 256 |
Producto farmacéutico / biológico (producto) | 10 |
Objeto físico (objeto físico) | 171 |
Procedimiento (procedimiento) | 911 |
Calificador (calificador) | 420 |
Elemento de registro (elemento de registro) | 115 |
Componente del modelo de SNOMED CT (metadato) | 29 |
Situación con contexto explícito (situación) | 91 |
Contexto social (contexto social) | 10 |
Concepto especial (concepto especial) | 35 |
Estadificaciones y escalas (escala de estadificación) | 13 |
Sustancia (sustancia) | 278 |
Se realizaron 38050 cambios al contenido existente
Estadística de mejoras a los conceptos existentes en SCT | Cantidad |
---|---|
Cambio en el estado de definición del concepto de Primitivo a Suficientemente definido | 796 |
Cambio en la definición inferida del concepto | 15635 |
Cambio en la definición en la forma definida del concepto | 7597 |
Cambio en las descripciones | 1284 |
Conceptos inactivados | 781 |
Descripciones inactivadas | 11943 |
Conceptos reactivados | 14 |
Cantidad total de cambios | 38050 |
2.2.1 Anatomía
Nuevos conceptos anatómicos: 571
- 462 conceptos de estructuras corporales con lateralidad y casi 1000 nuevos hallazgos, trastornos y procedimientos con referencias a estructuras corporales con lateralidad. Actualmente hay más de 5.000 conceptos con lateralidad en SNOMED CT.
- 30 nuevos conceptos relacionados con 736503009 |estructura de membrana mucosa de cavidad nasal o seno paranasal (estructura corporal)| y sus descendientes y refinamiento de las relaciones jerárquicas existentes.
- Nuevos conceptos para valores de trasplante cardíaco y estructura de la columna vertebral o la médula espinal para apoyar el modelado de conceptos del contenido de CIE-11.
Revisión y actualización de relaciones ES UN(A) para 1.255 conceptos de estructura de la piel, de acuerdo con el nuevo modelo anatómico:
- Se identificaron y agregaron 329 nuevas relaciones ES UN(A)
- se inactivaron 136 relaciones ES UN(A) redundantes o incorrectas.
Actualizaciones de los conjuntos de referencias SEP (por Structure, Entire, Part) y estructuras corporales lateralizables:
- 42 cambios en el conjunto de referencias SE
- 4 cambios en el conjunto de referencias SP
- 42 nuevos miembros para el conjunto de referencias de estructuras corporales lateralizables y 10 inactivaciones
2. El conjunto de referencias de estructuras corporales lateralizables se actualizó en la herramienta de conjuntos de referencia de SNOMED Internacional como se detalla a continuación:
- Se agregaron 3728 nuevos miembros y se inactivaron 5 para la Edición Internacional de julio de 2017
2.2.2 Hallazgo clínico
Nuevos conceptos para hallazgos clínicos y trastornos: 2005.
Se completó el trabajo en los siguientes Proyectos de Contenido:
- IHTSDO-418 - 84017003 | bursitis (trastorno)
- IHTSDO-772 - Los hallazgos / trastornos sospechados deberían ser situaciones
- IHTSDO-412 - Complicación intraoperatoria
Se inció el trabajo con los siguientes Proyectos de Contenido:
- IHTSDO-451 - Tiene manifestación definitoria
- IHTSDO-703 - Inactivación de conceptos con 'uniateral'
- IHTSDO-614 - Remodelado de la jerarquía 441457006 |quiste (trastorno)|
Otras mejoras en la calidad del contenido:
- Remodelado y cambio a suficientemente definido de 63491006 |claudicación intermitente (hallazgo)| y sus subtipos
- Revisión y remodelado de 128200000 |síndrome de dolor regional complejo (trastorno)| y sus subtipos
- Se agregaron 7 nuevos conceptos de hallazgos de laboratorio y se realizaron 30 cambios a conceptos de laboratorio existentes
- Revisión del contenido de lesión traumática de la médula espinal - muchos conceptos eran primitivos y se representaban como una lista plana debajo de 26738009 |lesión traumática de la médula espinal sin lesión ósea (trastorno)|. Se revisó esta subjerarquía y se remodelaron 85 conceptos. La mayoría se definió sobre la base de lesiones completas o incompletas y de los distintos niveles. Estos cambios también tuvieron en cuenta los problemas de duplicaciones informados.
- Remodelado de 3238004 |pericarditis (trastorno)| y sus subtipos con padres primitivos y se requirieron cambios en los grupos de relaciones para obtener una mayor coherencia. Se remodelaron alrededor de 100 conceptos.
2.2.3 Terminología Médica Convergente (CMT)
Nuevos conceptos de CMT: 766
Agregados en 3 dominios
- CMT Neurología
- CMT Musculoesquelético
- CMT Radiología
2.2.4 Jerarquía de procedimientos
Nuevos conceptos de la jerarquía de procedimientos: 911
Se agregaron aproximadamente 363 nuevos conceptos de diagnóstico por imágenes, incluyendo
- RM 53
- TC 38
- Radiología general 15
- Fluoroscopia 73
- Procedimientos con guía de estudios por imágenes (diversas modalidades) 102
- Ecografía 82
Se completó el trabajo en los siguientes Proyecctos de Contenido:
- IHTSDO-111 - Revisión de la jerarquía 23968004 |colectomía (procedimiento)| con inactivación de contenido duplicado, remodelado de conceptos con padres primitivos y cambios en los grupos de relaciones en los casos necesarios.
- IHRSDO-691 - Remodelado del contenido de 243185007 |apoyo vital avanzado (procedimiento)| y sus subtupos.
Otras mejoras en la calidad del contenido:
- Remodelado y cambio a completamente definido de 180081001 |corrección de deformidad congénita de la mano (procedimiento)| y sus descendientes.
- Se arreglaron violaciones de las reglas de MRCM en 156 procedimientos de evaluación y se retiraron entidades observables como valores de Atributo del componente.
- Inactivación en la Edición Internacional de conceptos específicos del dominio correspondiente a acceso a los niveles de atención
2.2.5 Proyectos de colaboración / armonización
2.2.5.1 Orphanet
Como resultado de la colaboración con Orphanet (http://www.orpha.net/consor/cgi-bin/index.php) se crearon 12 nuevos conceptos en SNOMED CT para representar enfermedades raras en la jerarquía de trastornos.
2.2.5.2 Plan de armonización con CIE-11
Se agregaron 1100 conceptos equivalentes a los códigos de Estadística de Mortalidad y Morbilidad de CIE-11 (CIE-11-EMM); se realizan revisiones y adiciones continuas basadas en actualizaciones de CIE-11-EMM.
2.2.5.3 LOINC
Se crearon 105 nuevos conceptos en SNOMED CT para el Proyecto de Colaboración entre LOINC y SNOMED CT.
2.2.5.4 Clasificación Internacional para Prácticas de Enfermería (ICNP®)
Se crearon 74 nuevos conceptos de SNOMED CT como requisito para la Tabla de Equivalencias de ICNP-SNOMED CT.
2.2.5.5 Agencia Global Medical Device Nomenclature (GMDNA, Agencia de la Nomenclatura Global de Dispositivos Médicos)
Se crearon 165 nuevos conceptos en la jerarquía de objetos físicos para apoyar el acuerdo de colaboración con GMDN.
2.2.6 Anomalías morfológicas
Se agregaron 22 nuevos conceptos.
Se realizaron 8 actualizaciones de las referencias cruzadas a CIE-O en la edición de enero 2018.
2.2.7 Entidades observables
Nuevos conceptos agregados: 52
Mejoras en la calidad del contenido:
- Se inactivó 704318007 |tipo de propiedad (atributo)| y se reemplazó por 370130000 |propiedad (atributo)| en 162 conceptos modelados de entidades observables que previamente utilizaban 704318007 |tipo de propiedad (atributo)| . Se actualizaron las reglas relacionadas de MRCM y la Guía Editorial.
2.2.8 Organismos
Nuevos conceptos agregados: 236.
Se realizaron cambios a 29 conceptos existentes en la jerarquía de organismos.
2.2.9 Producto farmacéutico /biológico
Proyecto Modelo de Fármacos
Para mayores detalles sobre los cambios planeados en esta área, véase la sección Drug Model Working Group Directory (Directorio de Grupo de Trabajo del Modelo de Medicamentos). Recuerde que para acceder a este proyecto es posible que deba registrarse para la cuenta de usuario de Confluence.
Resumen de cambios
Nuevas jerarquías |
|
---|---|
Nuevos identificadores semánticos |
|
Nuevos tipos de atributos |
|
Producto medicinal (PM) | Se actualizaron ≈ 1100 conceptos existentes de acuerdo con los nuevos lineamientos terminológicos y/o para el modelado
|
Forma farmacéutica de producto medicinal (FPM) |
|
Medicamento clínico (MC) | Se actualizaron ≈ 3000 conceptos existentes, cambiando "producto que contiene X" por "producto que contiene solamente X"
|
Conceptos nuevos o actualizados para apoyar el desarrollo futuro de conjuntos de referencias cruzadas simples | Para el conjunto de referencias cruzadas simples de SNOMED CT a EDQM:
Para el conjunto de referencias cruzadas simples de CNOMED CT a UCUM:
|
Mantenimiento de contenido |
|
2.2.10 Extensión veterinaria
- Se trasladaron 2 conceptos a la Extensión veterinaria.
2.2.11 Situación con contexto explícito
Cantidad de conceptos agregados a la jerarquía de Situación: 91
Trabajo completado en los siguientes Proyectos de contenido:
- artf222723 - 19 nuevos conceptos en la jerarquía de situación para reemplazar conceptos inactivados en la jerarquía de eventos 398033008 |Muerte de familiar (evento)|.
Comenzó el trabajo con los siguientes Proyectos de contenido:
- IHTSDO-703 - Comenzó la inactivación de conceptos con 'unilateral', reemplazándolos por conceptos con lateralidad que no estaban presentes en la terminología. Este trabajo continuará durante 2018.
2.2.12 Elemento de registro
Nuevos conceptos agregados: 82. Este número incluye 5 nuevos conceptos para 'plan de atención' que reemplazarán a conceptos inactivados en la jerarquía de calificadores.
2.2.13 Espécimen
Nuevos conceptos agregados: 30.
2.2.14 Sustancias
Se incluyeron los siguientes cambios en la Edición Internacional de enero de 2018:
Nuevas jerarquías |
|
---|---|
Nuevos apéndices semánticos |
|
Nuevos tipos de atributos |
|
Creación o actualización de la documentación:
- Guía editorial para el modelado y la denominación de la jerarquía Sustancia.
- Guía editorial para la modelado y la denominación de la jerarquía Disposición.
La actualización del contenido incluye:
- Se incluyeron aproximadamente 250 nuevos conceptos en la jerarquía Disposición como descendientes de 726711005 |disposición (disposición)|
- Actualización de la denominación y el modelado de aproximadamente 200 conceptos existentes que representan agrupadores de disposiciones, transformándolos en completamente definidos y con eliminación de descendientes en la forma definida. Como resultado se remodelaron aproximadamente 9000 descendientes con nuevos padres en la forma definida.
- Se agregó el nuevo atributo Tiene disposición para aproximadamente 4200 conceptos
- Se completó la revisión de conceptos como resultado de un análisis de situación para identificar conceptos faltantes que representaban hidratos y se agregaron 14 conceptos nuevos (Nota: en la edición de julio de 2017 se agregaron 87 conceptos nuevos). Se rechazaron tres conceptos (por no corresponder al campo de aplicación o por contenido duplicado o existente)
Planes de Publicación - Jerarquía de Sustancias
Para mayores detalles sobre los cambios planeados en esta área, véase el Proyecto de Sustancias. Recuerde que para acceder a este proyecto es posible que deba registrarse para la cuenta de usuario de Confluence.
2.3. Mejora interna en la calidad del contenido
2.3.1 Indicador de relevancia del uso de mayúsculas y minúsculas
Para cumplir con la especificación de RF2 se realizó un cambio masivo del valor de la relevancia del uso de mayúsculas o minúsculas en más de 1400 descripciones.
2.3.2 Mejoras en el perfil lógico
Se realizaron cambios de contenido para apoyar las mejoras en el perfil lógico.
El nuevo tipo de referencias cruzadas a expresiones de OWL tendrá los conjuntos de referencias de axiomas OWL y el conjunto de refeencias de la ontología OWL.
Se agregaron los nuevos atributos |atributo de objeto del modelo conceptual (atributo)| y |atributo de datos del modelo conceptual (atributo)| para establecer una distinción clara entre los atributos de un objeto y los atributos de los datos.
Todos los atributos existentes debajo de |atributo del modelo conceptual| se colocaron debajo de |atributo de objeto del modelo conceptual|, las propiedades de datos en las extensiones nacionales deberán moverse debajo del nuevo atributo |propiedad de dato del modelo conceptual|.
- Puede consultarse la propuesta detallada en https://goo.gl/pFqajg.
- El documento de especificaciones para conjuntos de referencias de la ontología OWL (borrador) se encuentra en https://goo.gl/Er3n7b
- La especificación del Perfil Lógico de SNOMED CT (borrador) se encuentra en https://goo.gl/Hkw3Zd
2.3.3 Conjunto de referencias de odontografías
Se agregaron 63 nuevos conceptos de Odontología.
La primera versión de producción del Conjunto de Referencias de Odontografías se publicó en octubre de 2017.
2.3.4 Modelo conceptual (MRCM)
Se realizaron 17 nuevos cambios o actualizaciones en los conjuntos de referencias de MRCM y en la plataforma de edición.
La mayoría de los cambios eran necesarios para apoyar el desarrollo del modelo conceptual para fármacos y entidades observables.
2.4 Productos derivados de SNOMED CT
2.4.1 Referencias cruzadas a CIE-10
Las referencias cruzadas de SNOMED CT a la Clasificación Estadística Internacional de Enfermedades y Problemas Relacionados con la Salud Versión 2016 (© Organización Mundial de la Salud 1994) (Referencias cruzadas de SNOMED CT a CIE-10) se incluye en la Edición Internacional de SNOMED CT a modo de referencia. Las referencias cruzadas de SNOMED CT a CIE-10 se crearon para apoyar las necesidades de datos epidemiológicos, estadísticos y de notificación administrativa de los países miembros de la IHTSDO y los Centros Colaboradores de la OMS.
Las Referencias cruzadas de SNOMED CT a CIE-10 se publican en el formato de publicación 2 (RF2) solamente. Se encuentran en el fichero der2_iisssccRefset_ExtendedMapFull_INT_20170131.txt, en la carpeta Map incluida en la carpeta Refset, en cada una de las tres carpetas Release Type de RF2.
Las Referencias cruzadas de SNOMED CT a CIE-10 se publican como 447562003 |conjunto de referencias cruzadas complejas a la Clasificación Internacional de Enfermedades, décima revisión (metadato fundacional)|.
2.4.1.1 Resumen de la actividad de desarrollo de contenido
Las referencias cruzadas son un conjunto de relaciones originadas en conceptos de SNOMED CT hacia códigos de la clasificación CIE-10. Los dominios de SNOMED CT incluidos como origen se limitan a los subtipos de 404684003 |hallazgo clínico (hallazgo)|, 272379006 |evento (evento)| y 243796009 |situación con contexto explícito (situación)|. Los códigos de destino de la clasificación corresponden a la edición de 2016 de CIE-10.
2.4.1.2 Contenido referenciado para la Edición Internacional de enero de 2018
Se actualizaron las referencias provistas para la Edición Internacional de enero de 2018, que ahora representan una versión completa de las referencias cruzadas de la Edición Internacional de SNOMED CT a CIE-10 versión 2016.
- Se agregaron 2207 nuevos conceptos
Agradeceremos los comentarios sobre cualquier problema detectado por los usuarios durante la utilización de las referencias cruzadas, informado a través de mapping@ihtsdo.org
3 Notas técnicas
3.1 Problemas conocidos
Los problemas conocidos son aquellos de índole técnica o relacionados con el contenido cuyas causas se comprenden y su solución se ha discutido y acordado, pero aún no se ha implementado. Esto último puede deberse a diversas razones, desde falta de suficientes recursos para resolverlos en el ciclo de edición actual, hasta el riesgo de impacto en la estabilidad de SNOMED CT si la solución se implementara en esa etapa del ciclo de vida del producto.
Para la Edición Internacional de enero de 2018 se identificaron los siguientes problemas conocidos y se acordó resolverlos en el próximo ciclo de edición (a publicarse en julio de 2018):
Clave | Resumen | Descripción |
---|---|---|
ISRS-8 | Additional, non-defining relationships | "Part-of" relationships are not currently maintained - they were originally defining relationships, which were changed to "additional" in 2005 and left in the relationship table. In 2008, when stated relationships became part of the distributed files, the stated "part-of" relationships were not included because they were non defining and were not available. Therefore, only inferred “part-of” relationships were distributed until 2005, after which they became non-defining. The Anatomy remodelling, which resolves this issue, is due for completion in future editing cycles. KNOWN ISSUE: An interim solution has been implemented, through the inclusion of the SE and SP refsets, which also to enable us to further improve our Quality Assurance processes. Please see the following page for details of the new Refsets: SEP maps and refset |
ISRS-206 | CaseSignificance changes that have yet to be implemented | A small percentage of the records updated for the caseSignficance changes have been identified as not having been implemented for July 2017 as expected. Due to their relatively low impact we are proposing to retain these as Known Issues for the January 2018 release, and resolve them as part of future editing cycles. KNOWN ISSUE: The SNOMED International Content Team have confirmed that deferring these fixes to later editing cycles is the correct approach. These will therefore be fixed in future editing cycles. |
ISRS-298 | Clinical finding 404684003 only approved defining attributes used | There are 3308 instance of 363705008|Has definitional manifestation| being used. - KNOWN ISSUE: These are restricted to inferred relationships only, and are already identified for resolution by SNOMED International Content Team in future editing cycles. ADHA confirmed that this is acceptable and so will whitelist the issues in their tests until the fixes are complete. |
ISRS-319 | Minor issues in the MRCM Domain file | Minor issues have been identified in the MRCM Domain file, as follows:
KNOWN ISSUE: The July 2018 International Edition will include updates to the MRCM Domain reference set file that will resolve the above issues. If you are using the MRCM release files, please contact the SNOMED International Product Support team (eps@snomed.org) for advice on ways to resolve or mitigate any short-term impact that these issues may have on your specific use case. |
3.2 Resolved Issues
Resolved issues are Known Issues which were not fixed as part of the previous release lifecycle, but which have now been resolved in the latest release - in this case the January 2018 International Edition. They can also be issues found during the Alpha and Beta testing of the current release, which were resolved before the final deployment of the associated Member release. Finally they can be issues which were reported or found during the testing phase, but which have been closed without any action taken.
The Resolved Issues for the Snomed CT January 2018 International edition can be found here:
Clave | Resumen | Descripción | Resuelta | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ISRS-146 | Potentially remove the SNOMED to OWL conversion script from the International Edition | As SNOMED International may soon open-source this file, we may then remove it from the International Edition release package. RESOLUTION: This was discussed with the Release AG and agreed to be removed - it is therefore now being published as a separate file in the MLDS repository. | 2017-may-11 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-156 | Text definition set as the en-GB preferred term of a concept (July 2017) | This is a duplicate of ISRS-153, created to ensure that we track and test the fix for the International Edition. RESOLUTION: RVF assertions added as planned to cover these scenarios. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-169 | 46 active core descriptions that have no acceptability in any dialect | The description id is first, with the concept id in the square brackets. 3313707012[718744009]: Revised Children's Anxiety and Depression Scale obsession compulsion subscale is active with no Acceptability map (since 20170131). RESOLUTION: A previous Known Issue from the July 2017 International Edition, as these were historical issues with no perceived clinical impact, and as such were designated as low priority by the SNOMED International Content Team. They were therefore fixed in the next editing cycle, and will now be released in the January 2018 International Edition. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-192 | Concepts not using the expected attribute | Four concepts using the 363705008 | HAS DEFINITIONAL MANIFESTATION | attribute, that according to our checks shouldn’t – our test restricts the domain to 64572001|Disease (disorder)| 15748521000119101 Tightness of bilateral gastrocnemius muscles (finding) RESOLUTION: Stated Relationships for the above 4 concepts have had HAS DEFINITIONAL MANIFESTATION (363705008) inactivated in the January 2018 International Edition release | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-209 | Need termServer to prevent re-basing of Release branches | This is to prevent the issues we've experienced in past releases, whereby the release branch (taken at time of versioning) has been accidentally re-based by the content team against the MAIN branch, thus polluting it with new content for the next release cycle. RESOLUTION: We have therefore updated the SCA to allow us to set a flag at branching time to ensure that this is not even an option. | 2017-dic-06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-212 | MRCM Cardinality constraint failure - domain of all 272741003 |Laterality| relationships should be a descendant or self of a member of the 91723000 |Lateralizable body structure reference set| | The concept model has an 'optional' rule that the domain (ie sourceConcept) of all 272741003 |Laterality| relationships should be a descendant or self of a member of the 91723000 |Lateralizable body structure reference set| (see row 4 of 'Attribute domain (edit)' and row 19 of 'Domain (edit)' sheet). There are 13 concepts (see below) that are lateralized (ie the source of a |Laterality| relationship) which are not a descendant or self of a member of |Lateralizable body structure reference set|. This optional rule is intended to raise a warning, to allow the appropriate concepts to be added to the |Lateralizable body structure reference set|. This rule is optional so we need to discuss and agree whether or not to fix/address any lateralized body structures that are not in this refset. 27441005|Structure of right aorticopulmonary cushion (body structure)| RESOLUTION: The failures of this "optional" rule are Warnings only, and therefore not critical to the use of the Lateralizable Body Structure refset. As such, they have been resolved by the SNOMED International content team during the January 2018 editing cycle, as part of the planned refinement of the editorial rules for the representation of lateralities for embryonic structures and lateral half structures.
| 2017-oct-12 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-218 | Inactive concepts with descriptions of status 0 (RF1) | All concepts should have a fully-specified name of appropriate status. There are 10 inactive International concepts that have come through the RF2 to RF1 conversion with their attached descriptions still as status 0. Highly likely that this is an RF2 to RF1 conversion issue rather that a problem in the base RF2 data. RESOLUTION: Firstly, the RF2 to RF1 conversion process has been refined to assign "Status 8" to the descriptions even if an inactivation indicator has not been set. Secondly, an RVF improvement ticket has been opened to identify these cases, allowing them to be resolved early in the cycle in future. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-220 | Metadata concepts without IS_A relationships (RF1) | All concepts except the Root must be children in the IS_A hierarchy. Three odd metadata concepts have crept into the release without any kind of IS_A relationship attached. These may in fact be supporting items from the International authoring environment and not even true RF2! 733929006 "General concept axiom (metadata)" 734146004 "OWL ontology namespace (metadata)" 734147008 "OWL ontology header (metadata)" Additionally, two new concepts have been created which should have been specified in the model module, not the core module: 734866006 0 Concept attribute (foundation metadata concept) XUy1X 1 RESOLUTION: RF2 to RF1 Conversion Utility refined in order to bring it in line with current RF2 definitions of metadata concepts. Modules for the relevant RF2 concepts have also been corrected accordingly in the final January 2018 Member Release package. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-224 | Re-use of Relationship ID's (RF1) | No changes are allowed to released relationships, except for the Relationship Group or Refinability fields. Is this a bug in the RF2 to RF1 conversion? Seems to be re-using relationship IDs at random from one release to the next. Will Investigate further, this is just a heads up to the fact that we found 442 fails of this rule. RESOLUTION: this has been resolved in the RF2 to RF1 conversion utility as part of the January 2018 Editing cycle.
| 2017-dic-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-233 | Historical issues related to MRCM Cardinality validation | RESOLUTION: the MRCM validation tool has been updated to report issues found in current authoring cycle and published contents separately.
| 2017-nov-08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-257 | Add new refsetDescriptor records to Jan 2018 International Edition | For the Jan 2018 International Edition, we need to add multiple new refsetDescriptor records (for 705111002 |Map correlation and origin type reference set| and 705109006 |Code). These should be similar to this (only with the International ModuleID instead of LOINC!): 906cb361-895c-4f9f-b8f1-1716843770c0 20170731 1 715515008 900000000000456007 705111002 449608002 900000000000461009 0 These rows represent the refset patterns used by the LOINC reference sets, and belong in the international edition, so that they can be used for other purposes (besides just for the LOINC refsets). RESOLUTION: Confirmed SRS and RVF had no issues with the additional records, so this ticket can be closed down without any action required.
| 2017-dic-01 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-260 | Content having different moduleID's than the related concepts | As part of the US Edition testing, several records were found where the components had been assigned different moduleID's to the concepts to which they were connected. For both Stated and Inferred relationship files: Concept: Concept: +*For description file:*+ Concept: Concept: Concept: Concept: RESOLUTION: ModuleID's on the Relevant concepts/descriptions updated accordingly. | 2017-ago-29 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-270 | RVF Assertion failure: 19423070-7118-45bd-98ba-6d0dc18bc619 | assertionUuid: "19423070-7118-45bd-98ba-6d0dc18bc619", conceptId: "723618002", conceptId: "71516007", conceptId: "723616003", conceptId: "723617007", RESOLUTION: Synonyms added as required. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-286 | Stated IS_A relationship and semantic tag | Concept found incidentally after close of editing and usual validation and QA. 205802006|Oculo-palato-digital syndrome (disorder)| The error did not show up in existing reports. Also earlier in release cycle found 116224001|Complication of procedure (disorder)| with IS_A relationship to 263718001|Complication (attribute)| An MRCM rule could be designed to pick these types of errors up, existing MRCM rules only check attributes other than (IS_A) are applied to correct domains. Refinement to QA rules in SCA requested and reprioritised to highest priority RESOLUTION: Stated Relationship parent 263934009 (IS_A relationship ID 7333028021) removed for Concept ID 205802006, and replaced with new stated parent 128430005 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-287 | Promote LOINC metdata into the Jan 2018 International Edition release | Several metadata concepts were accidentally not included in the July 2017 LOINC content editing cycle, and so missed the cut for the July 2017 International release. We therefore added them in manually to the July 2017 LOINC Release - however they should reside in the International Edition, and we therefore need to promote them into the Jan 2018 International Edition. Please see the linked LOINC-357 ticket for full details. RESOLUTION: LOINC metadata concepts, plus refsetDescriptor records added to the January 2018 International Edition as planned. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-288 | RVF Assertion failure: 89ceaf00-79b9-11e1-b0c4-0800200c9a66 | assertionUuid: "89ceaf00-79b9-11e1-b0c4-0800200c9a66", RESOLUTION: Born inactive relationship resolved. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-289 | RVF Assertion failure: b88b9f46-4c33-4d8e-b9ab-ddb87aef3068 | assertionUuid: "b88b9f46-4c33-4d8e-b9ab-ddb87aef3068", RESOLUTION: Inactive state resolved in final Production release. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-290 | RVF Assertion failure: c3249e80-84f0-11e1-b0c4-0800200c9a66 | assertionText: "Terms that contain en-us specific words are in the en-us language refset.", RESOLUTION: This assertion is for warning purposes only, and in this case no action is required for the January 2018 International Edition. | 2017-nov-22 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-291 | RVF Assertion failure: cc9c5340-84f0-11e1-b0c4-0800200c9a66 | assertionUuid: "cc9c5340-84f0-11e1-b0c4-0800200c9a66", assertionText: "Terms that contain en-gb specific words are in the en-gb language refset.", RESOLUTION: This assertion is for warning purposes only, and in this case no action is required for the January 2018 International Edition. | 2017-nov-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-292 | RVF Assertion failure: 0cc708af-6816-4370-91be-dba8da99d227 | assertionUuid: "0cc708af-6816-4370-91be-dba8da99d227", RESOLUTION: This is an expected result of the content fix, and therefore no action is required for the January 2018 International Edition. | 2017-nov-23 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-293 | RVF Assertion failure: 2aa0bea1-b1fa-4543-b277-b4392a6f864d | assertionUuid: "2aa0bea1-b1fa-4543-b277-b4392a6f864d", | 2017-nov-23 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-294 | MRCM refset failures | Validation of the January 2018 Alpha release content, using the MRCM refsets has passed. However, validation of the new MRCM refsets themselves has failed, with errors that need to be resolved before the validation of the content can be run again... RESOLUTION: MRCM refsets repaired and MRCM validation run successfully. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-295 | Changes to content after validation report review | RESOLUTION: After review of content changes in attached validation report, a small number were escalated to principle terminologist for review, 3 changes were made in this task RFJ-3. 1. Changed stated parent for 723830005|Keratosis follicularis, dwarfism, cerebral atrophy syndrome(disorder) to remove autosomal dominant parent 2. Changed stated parent for 205802006|Oculo-palato-digital syndrome (disorder)| to remove qualifier value as IS_A - this is logged separately https://jira.ihtsdotools.org/browse/ISRS-286 3. Reinstated synonym that was inactivated in error on 48611009|Keratosis follicularis (disorder)| | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-296 | 2 duplicate Association Reference records | The UKTC found one issue in the Association Reference set, a duplication with all fields except for the ID:
This was identified during the RF2 to RF1 conversion process - the rest of the RF1 conversion has passed their load testing. RESOLUTION: The first record was removed (c9973797-b81c-4ec9-b816-707d8fa96e01) and the second record was retained (c9d735f4-de2f-4362-934e-8963bd553b04). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-297 | Duplicate active references in the Anatomy structure and entire refset | The second entry is thought to be unnecessary:
RESOLUTION: The second record was removed (6dc07e8a-2f70-4eb2-a7f3-7194a996fb32) and the first record was retained (1fd6713a-d6a3-4de5-b33f-dd85cfb075e3). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-299 | Possible dual lineage - 411115002|Drug-device combination product (product)| | ADHA have got this coming up in a dual lineage check, but it looks OK… (they can’t access the daily build at the moment, so please verify if this is a valid issue or not). RESOLVED: ADHA confirmed no issue - tests refactored to prevent false positives. Ticket has therefore been closed down with no action required. | 2017-nov-29 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-300 | 123005000 | PART OF | issues | Invalid Range concept -
Incorrect Domain - 70 relationships do not have a domain that is subtype of Anatomical structure (body structure). Specifics available upon request. RESOLUTION: SNOMED International Content Team confirmed that these issues will be resolved as part of the overall Anatomy model refactoring, due to be completed within the next 3 years. The relevant validation tests will be whitelisted until this Anatomy remodelling is complete. | 2017-dic-01 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-301 | Lateralizable body structure reference set issues | The following concepts do not appear to be lateralizable. I think I reported these in October, but in any case. No new instances.
RESOLUTION: Relevant concepts inactivated in the Lateralizable Body Structure reference set. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-302 | Case Sensitivity issues |
Descriptions available on request (can attach to a ticket). RESOLUTION: Case significance changed for all relevant records. Rules to be continually refined in 2018 to prevent future issues of a similar nature. | 2017-dic-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-303 | ICD-O simple map issues |
· 18 Topography codes are not mapped to 442083009|Anatomical or acquired body structure (body structure)|. (Most of these already identified in previous above)
RESOLUTION: All 68 members inactivated in the Simple Map snapshot accordingly | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-304 | MRCM attribute domain international reference set | attributeCardinality 35e812ae-cfae-4e6f-a86c-95d7fc2d8b28 363705008|Has definitional manifestation|
dfd2d19e-eb7f-4d3e-9ae5-65e36af00d42 736518005 |Has state of matter (attribute)|
These cardinalities are unique across the entire refset. If they are valid, I’ll update the checks. RESOLUTION: SNOMED International Content Team confirmed that no action is required for this, as the explanation was acceptable to the users. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-305 | MRCM attribute range international reference set validation | rangeConstraint is immutable – the rangeConstraint value has changed for two entries
This may be valid as the specs currently indicate the field is mutable. Was changed in May 2017. Please confirm if correct. RESOLUTION: SNOMED CT Product support team confirmed that this is valid, and therefore no action is required. The rangeConstraint was intentionally made mutable in the |MRCM attribute range reference set| to avoid churn of UUIDs when the range of an attribute changes. With respect to the specifications including a "Mutable" column (rather than an "Immutable" column) ... this was changed consistently across all our specifications to improve the readability of this information. | 2017-dic-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-307 | RefsetDescriptor query - Attribute description not found within correct hierarchy | Attribute description values 410662002 and 900000000000444006 are not descended from "Reference set attribute". The following records are affected:-
RESOLUTION: Both records updated accordingly: c4de4be5-6d39-4ae8-8974-ebb1aadf0f93 20180131 1 900000000000012004 900000000000456007 705111002 734866006 900000000000461009 2 cf88d18f-d05a-407a-bea8-cd46fc79accc 20180131 1 900000000000012004 900000000000456007 705109006 734867002 900000000000461009 3 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-308 | Concept has no active FSN within its module | The following concepts belong to module 900000000000012004, but their fully-specified names in the descriptions table belong to 900000000000207008:
RESOLUTION: ModuleID's updated on relevant concepts, plus on the related Relationship records. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-309 | AttributeValue refset - Concept is mapped to wrong inactivation value | This refers to concepts in the RF1 release with status 5 (Erroneous) which are mapped to valueid 723277005 ("Nonconformance to editorial policy component") in the Concept inactivation indicator refset (900000000000489007). Ordinarily we would exect to see them mapped to "Erroneous component" (900000000000485001). See attached list. RESOLUTION: Reporters confirmed that this ticket can be closed down with no action required, as the issue reported was a result of a local conversion process, and therefore has no impact on the RF2 Release package. | 2017-dic-01 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-310 | AttributeValue refset - Description is mapped to wrong inactivation value | Similar to the concepts with incorrect values in A number of descriptions are mapped to values other than those suggested by their RF1 statuses. See attached report. RESOLUTION: Reporters confirmed that this ticket can be closed down with no action required, as the issue reported was a result of a local conversion process, and therefore has no impact on the RF2 Release package. | 2017-dic-01 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-311 | Fix validation failure 48118153-d32a-4d1c-bfbc-23ed953e9991 | {"testCategory": "file-centric-validation", { "conceptId": "24891006", "detail": "Concept:482041016 has multiple description ids for the same term:Sodium amidotrizoate" }} RESOLUTION: Erroneous changes to Description snapshot reverted, so records once again are as follows:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-313 | RVF Assertion failure: d9f8a8d6-2c02-11e7-b0e7-3c15c2c6e32e | assertionText: "The FSN term should be unique in active content when case sensitivity is ignored.", RESOLVED: SNOMED CT Content team confirmed that these variations are valid, and this ticket can therefore be closed down without any action required | 2017-dic-08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-314 | RVF Assertion failure: 0cc708af-6816-4370-91be-dba8da99d227 | assertionUuid: "0cc708af-6816-4370-91be-dba8da99d227", | 2017-dic-15 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-320 | Erroneous description identified for concept 1086561000119100 | An erroneous preferred term has been identified on concept: 1086561000119100|Hemorrhage of duodenum co-occurrent and due to diverticulosis (disorder)| This duplicates the preferred term on concept: 1086571000119106|Hemorrhage of ileum co-occurrent and due to diverticulosis (disorder)| RESOLUTION: Removed 2 invalid descriptions (3512606011 + 3512607019) due to status of erroneous (not inactivated, completely removed as otherwise these would have been born inactive as they were new to the January 2018 International Edition), and replaced them with 2 new descriptions (3658075016 + 3083724012) | 2018-ene-29 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ISRS-322 | Erroneous description identified for concept 259720006 | An erroneous preferred term has been identified on concept: 259720006|Substance with white blood cell enzyme mechanism of action (substance)| RESOLUTION: Description 3520664018 inactivated with a status of erroneous, and Description 3658178016 added as a new description (preferred term)
| 2018-ene-29 |
3.2 Problemas resueltos
Los problemas resueltos son problemas conocidos que no se habían solucionado en la etapa previa del ciclo de vida del producto, pero se resolvieron en la última publicación – en este caso, la Edición Internacional de julio de 2017. También se incluyen en esta sección problemas detectados durante las pruebas alfa y beta de la publicación actual, que se resolvieron antes de la publicación para los miembros asociados. Por último, podrían incluirse problemas informados o hallados durante la fase de prueba, pero que se cerraron sin haber realizado ninguna acción.
Los problemas resueltos para la Edición Internacional de julio de 2017 pueden encontrarse aquí:
Clave | Resumen | Descripción | Resuelta | |||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ISRS-46 | MOVED_TO status acceptability (RF1) | Ten RF1 descriptions for active concepts are status 10 (MOVED_TO), alongside descriptions with active status: RESOLUTION: SNOMED International Content team have inactivated all of the descriptions in question with reason "moved elsewhere" | 2016-nov-21 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-50 | Open RVF failures from the Production build | The following failures occurred after we added new RVF assertions in to cover issues found during the Alpha/Beta feedback period. 0cc708af-6816-4370-91be-dba8da99d227 "Description: id=60213011 is in the delta file, but no actual changes made since the previous release." 4478a896-2724-4417-8bce-8986ecc53c4e "Concept: id=10082001 is in the delta file, but no actual changes made since the previous release." 35680574-3ac6-4b68-9efe-de88b677eb35 "Association refset id=0e23f0c4-3dfa-5278-b35f-03e2cda41a7e is in the delta file, but no actual changes made since the previous release." cab60a2f-4239-4933-91d6-dc910a8ac08b "Stated relationship: id=3862464027 is in the delta file, but no actual changes made since the previous release." These failures can be safely ignored for this release, as they are simply highlighting the results of the manual fixes that we had to implement as part of the Alpha/Beta feedback period, in order to resolve some teething issues with the SCA. They therefore simply need to be verified after the final release has been deployed, in order to ensure that, as expected, they have not re-occurred. RESOLUTION: Remaining failures were resolved as planned. | 2017-may-15 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-102 | Two concepts in scope from the ICD-11 perspective that aren’t mapped | There are 2 concepts that after new type of validation have been shown to not have any equivalent ICD-10 maps: ID Preferred Name 722302009 Glycogen storage disease type II infantile onset (disorder) 722343009 Glycogen storage disease type II late onset (disorder) This was not reported until very late in the January 2017 release cycle. It was therefore discussed with the relevant Stakeholders, and the potential risk of impact involved in implementing a change to the content at this late stage in the release cycle was decided to be far greater than the perceived benefit of adding in just two map records. This will therefore be resolved in the July 2017 editing cycle, in order to preserve the quality of the January 2017 International edition. RESOLUTION: SNOMED International Mapping Team have now mapped both concepts in the July 2017 editing cycle, and so these will be included in the July 2017 International Edition release. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-149 | Removal of the SNOMED Identifier refset from the International Edition package as per the planned deprecation | As per the planned deprecation of antecedent SNOMED works (https://confluence.ihtsdotools.org/download/attachments/12779613/Antecedent%20SNOMED%20versions_External%20Newsletter%20Q1_v1.0.docx?version=1&modificationDate=1438866649000&api=v2), the SNOMED CT Identifier refset will be removed from the International Edition package as of the July 2017 International Edition. RESOLUTION: SNOMED CT Identifier refset removed from the July 2017 International Edition as planned. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-150 | Refinement of ISRS-117 - Active "WAS A" historical associations that have not been updated when the target concepts are inactivated | The resolution for - This now needs to be further refined in order to ensure that the historical audit trail remains intact. RESOLUTION: The 64 cases found in the current release with these issues have now been resolved in the July 2017 International Edition. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-153 | Text definition set as the en-GB preferred term of a concept | The following issue was reported during the July 2017 International edition editing cycle: For concept 722183007 | Embolization of hepatic artery using selective internal radiation therapy (procedure) |, two descriptions were created, one for en-GB and one for en-US, due to the difference in spelling. 3331000018 is the en-GB textDefinition, and has been assigned a descriptionType of "preferred synonym", instead of "preferred definition". RESOLUTION: The SNOMED International content team have updated the descriptionType in question, as part of the current cycle of content changes. It will therefore be published as part of the July 2017 International Edition. The Release Validation Framework will also be updated to include a validation check to capture any similar issues going forward. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-166 | Inactive Historical Associations discovered with invalid targetComponentID's | The following Historical Associations have had invalid inactive records added in the previous release cycle: RESOLUTION: Historical Association records fixed in time for the July 2017 International Edition. | 2017-may-12 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-167 | Delete born inactive stated relationships found in the dailybuild validation report | Born inactive stated relationships need to be deleted before alpha release. RESOLUTION: Born inactive Stated Relationship records were removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-170 | Potential MRCM Validation failure - domain=Domain{domainConstraint='<< 404684003 |Clinical finding (finding)|' | The following 2 records appears to contravene the Domain constraint, as follows: 42752001=Due to (attribute) applied to 268460000=Contraceptive device (physical object) Relationship_snapshot records: RESOLUTION: The relevant Relationships have been removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-171 | RVF Assertion failure: c3249e80-84f0-11e1-b0c4-0800200c9a66 | "assertionUuid": "c3249e80-84f0-11e1-b0c4-0800200c9a66", , { "conceptId": "444612005", "detail": "DESCRIPTION: id=2872859011: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: acanthamoeba" }, { "conceptId": "247894000", "detail": "DESCRIPTION: id=370105019: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: aggrandisement" }, { "conceptId": "391747009", "detail": "DESCRIPTION: id=1485745018: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: aluminium" }, { "conceptId": "391749007", "detail": "DESCRIPTION: id=1485746017: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: aluminium" }, { "conceptId": "392682000", "detail": "DESCRIPTION: id=1486658017: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaemia" }, { "conceptId": "393572004", "detail": "DESCRIPTION: id=1487426012: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaemia" }, { "conceptId": "393640005", "detail": "DESCRIPTION: id=1487494015: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaemia" }, { "conceptId": "469433000", "detail": "DESCRIPTION: id=2942363019: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaesthesia" }, { "conceptId": "701275000", "detail": "DESCRIPTION: id=2992662016: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaesthesia" }, { "conceptId": "393358009", "detail": "DESCRIPTION: id=1487234016: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaesthetics" }, { "conceptId": "394308008", "detail": "DESCRIPTION: id=1488063014: Synonym is prefered in US Language refset but refers to a word that has en-gb spelling: anaesthetics" }, RESOLUTION: This is just a warning and not an error and so no action is required. | 2017-may-20 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-172 | RVF Assertion failure: cc9c5340-84f0-11e1-b0c4-0800200c9a66 | "assertionUuid": "cc9c5340-84f0-11e1-b0c4-0800200c9a66", , { "conceptId": "426248008", "detail": "DESCRIPTION: id=2675183013: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: aleukemic" }, { "conceptId": "22695001", "detail": "DESCRIPTION: id=2763854012: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: aleukemic" }, { "conceptId": "35750002", "detail": "DESCRIPTION: id=2765156010: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: aleukemic" }, { "conceptId": "70321000119108", "detail": "DESCRIPTION: id=2989886018: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: aluminum" }, { "conceptId": "2468001", "detail": "DESCRIPTION: id=5221017: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: analyzer" }, { "conceptId": "8615009", "detail": "DESCRIPTION: id=15217012: Synonym is preferred in the GB Language refset but refers to a word that has en-us spelling: analyzer" }, RESOLUTION: This is just a warning and not an error and so no action is required. | 2017-may-20 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-173 | RVF Assertion failure: d9f8a8d6-2c02-11e7-b0e7-3c15c2c6e32e | "assertionUuid": "d9f8a8d6-2c02-11e7-b0e7-3c15c2c6e32e", , { "conceptId": "37300006", "detail": "FSN=Blood group antibody h (substance) concept=37300006: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "3807007", "detail": "FSN=Blood group antigen c (substance) concept=3807007: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "38194003", "detail": "FSN=Weak e phenotype (finding) concept=38194003: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "45969000", "detail": "FSN=Blood group antibody i (substance) concept=45969000: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "45992000", "detail": "FSN=Blood group antigen s (substance) concept=45992000: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "47662005", "detail": "FSN=Blood group antigen h (substance) concept=47662005: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "61271006", "detail": "FSN=Blood group antibody s (substance) concept=61271006: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "62523009", "detail": "FSN=Blood group antibody e (substance) concept=62523009: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "64259001", "detail": "FSN=Blood group antigen e (substance) concept=64259001: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "64846003", "detail": "FSN=Blood group antigen i (substance) concept=64846003: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "81835007", "detail": "FSN=Weak c phenotype (finding) concept=81835007: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "8362009", "detail": "FSN=Blood group antibody c (substance) concept=8362009: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "88341002", "detail": "FSN=Blood group antibody k (substance) concept=88341002: FSN term is not unique in description snapshot when case is ignored" }, { "conceptId": "406002002", "detail": "FSN=cde haplotype (finding) concept=406002002: FSN term is not unique in description snapshot when case is ignored" }RESOLUTION: These have been confirmed by the SNOMED International Content Team to be false positives, which can therefore be safely ignored. | 2017-may-23 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-174 | The first letter of the FSN should be capitalized.RVF Assertion failure: dd0d0406-7481-444a-9f04-b6fc7db49039 | "assertionUuid": "dd0d0406-7481-444a-9f04-b6fc7db49039", { "conceptId": "198030008", "detail": "DESC: id=582480013:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "228961005", "detail": "DESC: id=616608018:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "228969007", "detail": "DESC: id=616618011:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "228979009", "detail": "DESC: id=616629010:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "258259005", "detail": "DESC: id=649653011:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "258889007", "detail": "DESC: id=650356013:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "259011007", "detail": "DESC: id=650492013:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "259047008", "detail": "DESC: id=650532013:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "259048003", "detail": "DESC: id=650533015:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "259049006", "detail": "DESC: id=650534014:First letter of the active FSN of active concept not capitalized." } , { "conceptId": "259060002", "detail": "DESC: id=650546013:First letter of the active FSN of active concept not capitalized." }
RESOLUTION: Invalid descriptions inactivated, and valid descriptions added in for July 2017 with capitalised first words. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-175 | RVF Assertion failure: f7117eb0-7cd6-11e1-b0c4-0800200c9a66 | "assertionUuid": "f7117eb0-7cd6-11e1-b0c4-0800200c9a66", , { "conceptId": "88731002", "detail": "MEMBER: id=800637ed-978e-4dfa-be08-4e01bf5ad2c1:Historical refset member is active, but refers to an active concept." }, { "conceptId": "278772006", "detail": "MEMBER: id=800b7f78-fd36-4a42-b900-73aa4ab11a75:Historical refset member is active, but refers to an active concept." }, { "conceptId": "58287003", "detail": "MEMBER: id=80214885-ea37-4768-ae39-b985e0f8384b:Historical refset member is active, but refers to an active concept." }, { "conceptId": "299701004", "detail": "MEMBER: id=8024c43a-54bb-4ea3-8555-5af9c8adda76:Historical refset member is active, but refers to an active concept." }, { "conceptId": "84540008", "detail": "MEMBER: id=802c0ca6-beba-4a2b-a3be-93b1a6478451:Historical refset member is active, but refers to an active concept." }, { "conceptId": "279793002", "detail": "MEMBER: id=802e89f1-312f-4027-be34-581724e7b03d:Historical refset member is active, but refers to an active concept." }, { "conceptId": "81661008", "detail": "MEMBER: id=80313789-951a-4633-b550-42e78f380362:Historical refset member is active, but refers to an active concept." }, { "conceptId": "20963009", "detail": "MEMBER: id=803634b8-86f5-4ed1-804b-04a3824d7d9b:Historical refset member is active, but refers to an active concept." }, RESOLUTION: The RVF assertion needs to be updated in order to allow for the new SEP refsets in the Association Reference set. These failures can therefore safely be ignored for now. | 2017-may-22 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-178 | Unexpected ICD-0 inactivation records in the termServer simpleMap export | In the SimpleMap Delta we exported from the mapping file, it contained 95 new activations for ICD-0. However, in the final SimpleMap files in the release package, we're getting 105 records referencing ICD-0, including the following 10 inactivations that we've traced back to the simpleMap file exported from the termServer: > 20170731 0 900000000000207008 446608001 128507001 C49.2 The mapping team are unaware of why these should have ben updated, and so we need to prove whether or not they are valid changes. RESOLUTION: SNOMED International Content Team confirmed that these were expected changes, and Mapping Team confirmed everything as expected, therefore no action required. | 2017-jun-01 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-179 | RVF Assertion failure: 89ceaf00-79b9-11e1-b0c4-0800200c9a66 | "assertionUuid": "89ceaf00-79b9-11e1-b0c4-0800200c9a66", { "conceptId": "733529001", "detail": "Stated relationship: id=7002472022 is inactive in the current release but no active state found in the previous snapshot." } , { "conceptId": "733528009", "detail": "Stated relationship: id=7002479029 is inactive in the current release but no active state found in the previous snapshot." } ],
RESOLUTION: Relevant born inactive Stated Relationships removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-180 | RVF Assertion failure: eff30fb0-7856-11e1-b0c4-0800200c9a66 | "assertionUuid": "eff30fb0-7856-11e1-b0c4-0800200c9a66", , { "conceptId": "3499616017", "detail": "Language Refset: id=c1e2364a-9413-4e70-aaa1-9abe62165a2b is inactive but no active state found in previous release." }, { "conceptId": "3499619012", "detail": "Language Refset: id=e97fc6fd-68de-451b-b7c2-fdab05db4d00 is inactive but no active state found in previous release." }, { "conceptId": "3499617014", "detail": "Language Refset: id=f3814870-ee80-459d-bdb6-310688626fa5 is inactive but no active state found in previous release." }, { "conceptId": "3499617014", "detail": "Language Refset: id=fd8a80da-a79a-4f9f-bf93-378657935e85 is inactive but no active state found in previous release." }, { "conceptId": "3499618016", "detail": "Language Refset: id=1575a4c0-b70f-4267-81cf-47f44dfad066 is inactive but no active state found in previous release." }, { "conceptId": "3499618016", "detail": "Language Refset: id=2168b9f2-6ab3-4911-b14d-01d20c08e3d7 is inactive but no active state found in previous release." }, { "conceptId": "3499619012", "detail": "Language Refset: id=65ae52bb-ed7f-4df1-8d5a-55388ffb223b is inactive but no active state found in previous release." }], RESOLUTION: This is just a warning and not an error and so no action is required. | 2017-may-24 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-181 | RVF Assertion failure: 2b193a88-8dab-4d19-b995-b556ed59398d | "assertionUuid": "2b193a88-8dab-4d19-b995-b556ed59398d", , { "conceptId": "733528009", "detail": "DESCRIPTION: id=3499617014 is inactive but no active state found in the previous snapshot." }, { "conceptId": "733529001", "detail": "DESCRIPTION: id=3499618016 is inactive but no active state found in the previous snapshot." }, { "conceptId": "733529001", "detail": "DESCRIPTION: id=3499619012 is inactive but no active state found in the previous snapshot." }], RESOLUTION: These warnings are due to a system defect - WRP-3146 ticket has been raised to resolve. These can therefore be safely ignored for this release. | 2017-may-24 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-182 | MRCM validation failure on concepts having invalid attribute 424876005(Surgical approach) | The following concepts are reported by the MRCM validation to have inappropriate attributes:
Inferred view: Stated view: Note: MRCM rule states that 424876005(Surgical approach) applies to Domain 387713003 (Surgical procedure) RESOLUTION: Concepts re-modelled accordingly in time for the July 2017 International Edition. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-183 | RF2 to RF1 conversion issue | The RF2 to RF1 conversion is failing and it appears to be data related - attached log file gives details but it looks like there is an issue calculating the value of a description status in RF1. Whatever is in RF2 is not giving enough information to calculate the RF1 value and it is coming back as null, which fails the query. There are two possible causes from the information in the log file: 1. An un-attached description, i.e. where we had a reference to a concept ID in the descriptions file that was no in the concepts file. Checked this and all is good... 2. Alternative was a value (or values) in the Attribute Value reference set that was not being handled by the conversion code when associated with an inactive description ID. Bingo, we have our culprits, there are two concept IDs used in the valueId field of the Attribute Value reference set that have not been used before. Next checked the actual source code on Github for the RF2 to RF1 conversion routine and found the hard coded list of maps between the valueId and RF1 description status does not have these two values in it. This is the list referenced by the getMagicNumber method. The values at issue are 723277005 ‘Nonconformance to editorial policy component (foundation metadata concept)’ and 723278000 ‘Not semantically equivalent component (foundation metadata concept)’ occurring in reference set 900000000000490003. RESOLUTION: RF2 to RF1 conversion utility has been updated accordingly. | 2017-jun-01 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-184 | SCTID's using Description ID format instead of Concept ID's | Seven Concept ID's were found to be unexpectedly using partition ID's appropriate for Description ID's: · 3446012016 This was found to be a result of these concepts having been loaded in manually through the CRS, which by-passed the standard validation and therefore allowed them to be created in the wrong format in the termServer.
RESOLUTION: Offending concepts were removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-185 | Relationship with invalid typeID | Relationship 6923064024 (sourceId= 724482006) should have a typeId of 363714003|Interprets| This is a result of the Concept having two attributes, one of which should be "363714003|Interprets|" Amended in https://authoring.ihtsdotools.org/#/tasks/task/RFBINTJULA/RFBINTJULA-11/ RESOLUTION: Concept re-modelled accordingly for the July 2017 International Edition. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-186 | Descriptions that could potentially be textDefinitions | The following descriptions look like text definitions: RESOLUTION: Synonyms changed to TextDefinitions, or inactivated as ambiguous as appropriate. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-187 | Born inactive descriptions | Several inactive descriptions have never been published, and so don’t need to be in the release files: 3499616017 2017-07-31 00:00:00.0 0 900000000000207008 733528009 en 900000000000013009 Morphological change in endometrium due to intrauterine contraceptive device 900000000000448009 RESOLVED: Ticket closed as already resolved in | 2017-jun-05 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-188 | Born inactive language reference set records | Several inactive language reference set records have been published as inactive, but never been published before: 85d31301-45a6-4344-a28e-1c357975dd62 2017-07-31 00:00:00.0 0 900000000000207008 900000000000508004 3499616017 900000000000548007 RESOLUTION: Born inactive members already removed in TPFIX-16 | 2017-jun-05 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-189 | RefsetDescriptor queries | There’s a whole bunch of stuff in the Descriptor refset that I’m not sure about, from a content perspective… (not necessarily defects). · looks like descriptor entries have been created for all the “refset patterns”? RESOLUTION: Reporter happy with the level of information provided in the Release Notes to explain all of this, therefore ticket closed accordingly. | 2017-jun-02 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-190 | Attributes using the attribute 371881003|During| | Several attributes using the attribute 371881003|During| - I’ve found some working documents and ECE stuff, but nothing official? Though I saw it mentioned in the MRCM refsets, so I assume it’s now permissible and updated editorial rules will come out in July? (Once confirmed I’ll update our checks) 6967032028 2017-07-31 00:00:00.0 1 900000000000207008 10561000087108 387713003 0 371881003 900000000000011006 900000000000451002 RESOLUTION: Explanation of new attribute added to the Release Notes (section 2.3.5) to ensure those not reading the Editorial Guide updates are made aware of the changes. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-191 | Query on the use of new attributes | There are 17,000 relationships for product concepts that use attributes, not in the documented model. Again, these seem to be in the MRCM – so might be fine. RESOLVED: Requester agreed that the level of information in the Release Notes covered the required updates to NRC systems, and so this ticket was closed without any action required. | 2017-jun-05 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-193 | Concepts using invalid surgical procedure attributes | There’s 6 concepts that use the surgical approach attribute, are not permitted to. They are not “surgical procedures”. These are all embolization procedures, for which we encountered the exact same problem. Part of the problem is that “What is a surgical procedure”. 428563002 Stent assisted embolization of aneurysm using transluminal coil (procedure) - no new changes this release, existing issue, needs review and remodelling - CRS
RESOLUTION: Already resolved as part of the fix for ISRS-182 - this ticket therefore closed with no action required. | 2017-jun-02 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-194 | Redundant entry in the refsetDescriptor file | There’s a redundant entry in the descriptor for the lateralisable refset. bbdcc9fc-5bc6-415a-a5ee-c5adfc569bd5 2017-01-31 00:00:00 1 900000000000207008 900000000000456007 723264001 449608002 900000000000461009 0 RESOLUTION: Redundant record (31919d48-e54b-4993-abe1-9c2fa9568d78) removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-195 | Invalid CTV3 map records | The CTV3 map includes 7 invalid entries (same 7 description Ids described before). id refsetId referencedComponentId RESOLUTION: Seven invalid records removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-196 | Attribute description not found within correct hierarchy | Attribute description not found within correct hierarchy. Attribute descriptions are expected to be subtypes of 900000000000457003 ("Reference set attribute"). The following two records contain values outside this hierarchy:- de0f4894-9aff-4d5c-8702-60eeb33b7a96|410662002|Concept model attribute (attribute) RESOLUTION: Offending refsetDescriptor records removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-197 | refsetDescriptor record with inactive referencedComponentID | Record 662b1db8-4b23-4dd1-8bf6-3964f99fe77e contains an inactive referenced component (447564002). RESOLUTION: The refsetDescriptor record for the reference set 447564002 has now been inactivated accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-198 | Concept has no active FSN within its module | Concept 411116001 is a member of module 900000000000012004 ("SNOMED CT model component module"), while its only active FSN, 3495166019, is in module 900000000000207008 ("SNOMED CT core module"). RESOLUTION: FSN (3495166019) and synonym (3495165015) have both been moved to 900000000000012004 ("SNOMED CT model component module") accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-199 | Concepts have no active synonyms within their modules | These four concepts lack any active synonyms: 326342007 Note that all four of these concepts are inactive. RESOLUTION: SNOMED International Content Team confirmed that these are inactive concepts so therefore adding new synonyms is not the correct approach. Therefore no action is required in this case. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-200 | Changes to caseSignificance ID's | Descriptions which have had their case significance ids altered to 900000000000448009 ("Entire term case insensitive") for this release. RESOLUTION: UKTC confirmed that this issue was with the QA test rather than the content - this is therefore not a valid issue and so has been closed down without action required. | 2017-jun-01 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-201 | Namespace ID required for July 2017 | New namespace added for upcoming October 2017 Spanish Edition release, resolved in TPFIX-25 RESOLUTION: New namespace (734535006) created as planned. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-202 | RVF Assertion failure: eff30fb0-7856-11e1-b0c4-0800200c9a66 | "assertionUuid": "eff30fb0-7856-11e1-b0c4-0800200c9a66", , { "conceptId": "648391000124116", "detail": "Language Refset: id=8146604c-2d6e-4a3f-a25a-191e4f3b0945 is inactive but no active state found in previous release." }, { "conceptId": "648361000124112", "detail": "Language Refset: id=81b10a87-2ab5-41b0-b89f-e2ac70babfd8 is inactive but no active state found in previous release." }, { "conceptId": "638911000124112", "detail": "Language Refset: id=9b7f61d6-04f1-4b89-8ba4-79aa7bb0e401 is inactive but no active state found in previous release." }, { "conceptId": "648571000124112", "detail": "Language Refset: id=bace38c7-afbf-4448-aeeb-84b184f53a4f is inactive but no active state found in previous release." }, { "conceptId": "648501000124118", "detail": "Language Refset: id=ce266e08-6be8-4fad-97ee-b4c53ad5867f is inactive but no active state found in previous release." }, { "conceptId": "638911000124112", "detail": "Language Refset: id=07e5cf11-9088-40cd-97e2-d1c7bf178e3d is inactive but no active state found in previous release." }, { "conceptId": "648571000124112", "detail": "Language Refset: id=21aa1482-1a05-4852-8730-079ff2b37177 is inactive but no active state found in previous release." }, { "conceptId": "648331000124115", "detail": "Language Refset: id=28606ec3-edbc-4f73-953f-098f7fc15708 is inactive but no active state found in previous release." }, { "conceptId": "648361000124112", "detail": "Language Refset: id=3a671dec-8667-49e1-8a65-c867feb76e97 is inactive but no active state found in previous release." }, { "conceptId": "648391000124116", "detail": "Language Refset: id=44adb6e9-5ea0-41fa-8fb9-2f3d59698169 is inactive but no active state found in previous release." }, { "conceptId": "648331000124115", "detail": "Language Refset: id=619326a5-7a54-476e-b52a-d4915fc0d6e3 is inactive but no active state found in previous release." }], RESOLUTION: This is just a warning and not an error and so no action is required. | 2017-jun-02 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-203 | RVF Assertion failure: 2b193a88-8dab-4d19-b995-b556ed59398d | "assertionUuid": "2b193a88-8dab-4d19-b995-b556ed59398d", { "conceptId": "435801000124108", "detail": "DESCRIPTION: id=638911000124112 is inactive but no active state found in the previous snapshot." } , { "conceptId": "439021000124105", "detail": "DESCRIPTION: id=648331000124115 is inactive but no active state found in the previous snapshot." } , { "conceptId": "439031000124108", "detail": "DESCRIPTION: id=648361000124112 is inactive but no active state found in the previous snapshot." } , { "conceptId": "439041000124103", "detail": "DESCRIPTION: id=648391000124116 is inactive but no active state found in the previous snapshot." } , { "conceptId": "439081000124109", "detail": "DESCRIPTION: id=648501000124118 is inactive but no active state found in the previous snapshot." } , { "conceptId": "439101000124101", "detail": "DESCRIPTION: id=648571000124112 is inactive but no active state found in the previous snapshot." } RESOLUTION: The six born inactive Descriptions above have been removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-204 | RVF Assertion failure: 4478a896-2724-4417-8bce-8986ecc53c4e | "assertionUuid": "4478a896-2724-4417-8bce-8986ecc53c4e", { "conceptId": "448396008", "detail": "Concept: id=448396008 is in the detla file, but no actual changes made since the previous release." } RESOLUTION: Concept removed from the Delta file accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-205 | New record in Concept delta for existing component with no changes | Concept 448396008 experienced issues with the branch problem during the Alpha feedback period - when it was fixed in the Alpha the termServer believed it to be new an so added another active record to the delta, thus corrupting the Full and Snapshot files. RESOLUTION: Resolved as part of ISRS-204 | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-207 | One description has a full stop at the end | There’s still one description that might be text definition? Though it’s the presence of a period/full stop at the end of the description (which is unusual) is what’s causing the fail. 718089001 3311128017 2017-07-31 00:00:00 Post extubation acute respiratory failure requiring reintubation. RESOLUTION: Description inactivated, as turned out to be a duplicate. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-208 | AttributeValue Snapshot record is outdated by record in full file | Possibly inconsequential. Members of refset 900000000000490003 ("Description inactivation indicator attribute value reference set") for which a more recent record in the Full release expresses the same relationship (but with a different id). Note that the members in question are inactive: the QA is objecting to the same relationship appearing with two different ids. RESOLUTION: Four invalid AttributeValue records removed, plus four valid records re-activated for July 2017: Removed: 6937d3ce-9b92-46a5-915c-105ef53a85a3 20170731 1 900000000000207008 900000000000490003 350608017 900000000000495008 Re-activated: ff7de500-472d-5380-930e-b5ddfb184d98 1 900000000000207008 900000000000490003 377741012 900000000000495008
| ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-210 | MRCM Cardinality constraint failure - mandatory 'attributeInGroupCardinality' of 0..1 | The 363714003 |Interprets| attribute has a mandatory 'attributeInGroupCardinality' of 0..1. However, the concept 724758000 |Manic symptoms co-occurrent and due to primary psychotic disorder (disorder)| - with an effectiveTime of 20170731 - has 3 x 363714003 |Interprets| relationships in the same relationship group (Role group 3). This therefore breaks the concept model rule. RESOLUTION: Three extraneous Stated relationships removed and re-classified to resolve the errors. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-211 | MRCM Cardinality constraint failure - concept model states all new precoordinated content must have at most 1 x 363698007 |Finding site| relationship in any relationship group | The concept model states that all NEW precoordinated content must have at most 1 x 363698007 |Finding site| relationship in any relationship group (where relationshipGroup > 0). However, several concepts break this rule. RESOLUTION: The MRCM validation rule was proven to require refinement, in order to restrict it to the Stated view rather than Inferred. This has now been implemented and is now producing just 3 failures. The SNOMED International Content Team have therefore re-modelled the following 3 concepts:
The related born-inactive components created by this re-modelling after Versioning the content have also been removed. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-213 | MRCM Cardinality constraint failure - concept model states all new precoordinated content must have at most 1 x 116676008 |Associated morphology| in any relationship group (where relationshipGroup > 0) | The concept model states that all NEW precoordinated content must have at most 1 x 116676008 |Associated morphology| in any relationship group (where relationshipGroup > 0). However several concepts appeared to contravene this rule: RESOLUTION: The MRCM validation rule was proven to require refinement, in order to restrict it to the Stated view rather than Inferred. This has now been implemented and is now producing no failures. This ticket has therefore been closed down with no action required. | 2017-jun-20 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-214 | MRCM Domain constraint failure - | The domain of 405815000 |Procedure device| is << 71388002 |Procedure|. However, there are 3 concepts, which are << 363787002 |Observable entity|, which have an attribute that is a descendant of |Procedure device| (namely 424226004 |Using device|). This is valid, from a content perspective - however the MRCM rules are incorrect. The reason for this is that domain constraints are inherited by an attribute's children. And since 424226004 |Using device| has recently been added to the |Observable entity| domain, this should have also been added to the domain of the parent attribute (ie 405815000 |Procedure device|. RESOLUTION: 1 new row (row 103) has been added to the 'Attribute domain' refset for the Member Release. This has also updated the 'attributeRule' value in row 57 of 'Attribute range' refset. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-215 | Duplicate description found | 734059009 Intraductal papillary neoplasm with high-grade intraepithelial neoplasia (morphologic abnormality) 3482536011 20170731 1 900000000000207008 734059009 en 900000000000003001 Intraductal papillary neoplasm with high-grade intraepithelial neoplasia (morphologic abnormality) 900000000000448009
734133009 Intraductal papillary neoplasm with high grade intraepithelial neoplasia (morphologic abnormality) 3483018012 20170731 1 900000000000207008 734133009 en 900000000000003001 Intraductal papillary neoplasm with high grade intraepithelial neoplasia (morphologic abnormality) 900000000000448009
RESOLUTION: SNOMED International Content team have resolved this for the July 2017 Member release, by removing duplicate Concept 734059009. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-216 | Fix RVF assertion error 89ceaf00-79b9-11e1-b0c4-0800200c9a66 | testCategory: "release-type-validation", Delete the following 3 born inactive stated relationships: id effectivetime active moduleid sourceid destinationid relationshipgroup typeid characteristictypeid modifierid Note: This is the result of ISRS-210 fixes. RESOLUTION: 3 Born inactive Stated Relationships removed for the July 2017 Member release. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-217 | Potential equivalency | A change in the mapping history of 121161000000105 | Chickenpox vaccination. Unsure of the main cause of this but looks like it needs to be reviewed by SNOMED International. It is marked as a duplicate to 68525005 | Varicella vaccination (procedure) this has now been made duplicate to 722215002 | Administration of herpes zoster vaccine. However, I think this is incorrect and should be mapped to one of its child concepts 571611000119101 | Administration of varicella live vaccine (procedure). Researching this, the herpes zoster vaccine is a slightly different vaccine to the varicella vaccine. RESOLUTION: SNOMED International Content team have resolved this for the July 2017 Member release, by amending the mapping to 571611000119101
| ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-219 | Delete born inactive stated relationships after ISRS-211 fix | RVF failed several Stated Relationships which have been born inactive in July 2017: "assertionText": "All stated relationships inactivated in current release must have been active in the previous release.", "failureCount": 12, "firstNInstances": [{"conceptId": "15665361000119106","detail": "Stated relationship: id=6807693029 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665361000119106","detail": "Stated relationship: id=6807695020 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665361000119106","detail": "Stated relationship: id=6807696021 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665321000119101","detail": "Stated relationship: id=6807707026 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665321000119101","detail": "Stated relationship: id=6807709028 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665321000119101","detail": "Stated relationship: id=6807710022 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807712025 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807714029 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807715028 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807716027 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807718026 is inactive in the current release but no active state found in the previous snapshot."},{"conceptId": "15665401000119102","detail": "Stated relationship: id=6807719023 is inactive in the current release but no active state found in the previous snapshot."} RESOLUTION: All born inactive Stated relationships removed from the July 2017 International Edition accordingly.
| ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-221 | Retired concepts must have a historical relationship of the appropriate type (RF1) | Retired concepts must have a historical relationship of the appropriate type (unless their concept status is 1 or 3) RESOLUTION: The majority of these issues were proven by the SNOMED International Content team to be valid, with the root cause being invalid QA routines. One historical association (for concept 192203002) was proven to be invalid, and has now been amended accordingly for the July 2017 Member release. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-222 | Concepts with multiple historical relationships (RF1) | Concepts may not have more than one historical relationship (except MAY_BE_As, MOVED_TOs OR WAS_As). The following concepts have all come through RF2 to RF1 conversion with more than the expected number of historical relationships attached to them:
This may be another RF2 to RF1 conversion issue, rather than any problem with the RF2 source. RESOLUTION: All concepts changed to have AssociationReference refsetId equal to "POSSIBLY EQUIVALENT TO", and their AttributeValue valueId equal to "AMBIGUOUS" | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-223 | Active concepts with invalid historical relationships (RF1) | Historical relationships must belong to concepts of appropriate status. Three active concepts have come through conversion with odd historical relationships attached:
These may be odd entries in the RF2 reference sets or another group of RF2 to RF1 conversion issues. RESOLUTION: Concepts inactivated, plus historical associations corrected. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-226 | Concepts not inheriting the necessary attribute from the parent concept | Children of concepts with the "Has active ingredient" attribute must also have that attribute. The following concepts are not inheriting the necessary attribute from the parent concept:
RESOLUTION: UKTC confirmed that after further investigation this issue was specific to the UK extension, and therefore requires no action for the International Edition. Issue therefore closed without action. | 2017-jun-21 | |||||||||||||||||||||||||||||||||||||||||||||
ISRS-227 | Unknown FSN postfix values occurring as children of other FSN postfix values | Postfix metamodel rule: Only known FSN postfix values may occur as children of other FSN postfix values. The table below gives the issues from the International content. In the details column the child is the first code and the parent the second.
RESOLUTION: All relevant descriptions and Stated Relationship amended as per the noted in the table above.
| ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-228 | Delete 9 born inactive historical associations | RVF failure: "assertionText": "New inactive states follow active states in the ASSOCIATION REFSET snapshot file.", "failureCount": 9, "firstNInstances": [{"conceptId": "157379003","detail": "ASSOC RS: id=a0e20ebe-a5dc-4cb6-a226-a3b4441b0dc8 is inactive but no active state found in the previous release."},{"conceptId": "157379003","detail": "ASSOC RS: id=c03e2672-3d0e-4e5a-b61e-d43021b90810 is inactive but no active state found in the previous release."},{"conceptId": "287103000","detail": "ASSOC RS: id=d4f62913-bdbb-467c-811f-0f8250a7661d is inactive but no active state found in the previous release."},{"conceptId": "157379003","detail": "ASSOC RS: id=df96b92e-76b1-42f3-aa6f-01e3a9a8c0eb is inactive but no active state found in the previous release."},{"conceptId": "413138007","detail": "ASSOC RS: id=e806ed49-531d-41ed-bebf-2ec69995b0aa is inactive but no active state found in the previous release."},{"conceptId": "287103000","detail": "ASSOC RS: id=fc1cc179-f30c-49f7-b1c2-954955c78c2c is inactive but no active state found in the previous release."},{"conceptId": "397967003","detail": "ASSOC RS: id=006bbe0f-3d34-4ca8-9b94-bf97d44ca4a1 is inactive but no active state found in the previous release."},{"conceptId": "397967003","detail": "ASSOC RS: id=58121ca7-6b7d-4c9a-916f-d6d70df9b7c5 is inactive but no active state found in the previous release."},{"conceptId": "287103000","detail": "ASSOC RS: id=65d450af-36ef-47e5-a29b-fd0c82a27a0b is inactive but no active state found in the previous release."} RESOLUTION: The relevant Association refset components removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-229 | Fix assertion (1852b9d6-38cf-11e7-8b36-3c15c2c6e32e) validation issue | RVF failure: "assertionText": "Previously published historical association components should not be modified.", "failureCount": 1, "firstNInstances": [ {"conceptId": "413138007","detail": "Association refset id=84eb1cc8-23b9-5112-8ad1-9a075becd413 has historical association components changed since the previous release."}], RESOLUTION: Association Reference record fixed as folllows: id effectiveTime active moduleId refsetId referencedComponentId targetComponentId | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-230 | MRCM regression failure - attribute group contains multiple records for the same attribute | According to the attribute group rule there should not be more than one attribute per group as it is [0..1] group. This one only exists in the stated relationship but not in the inferred view: id effectivetime active moduleid sourceid destinationid relationshipgroup typeid characteristictypeid modifierid [4428858023|tel:(442)%20885-8023] 20090131 1 900000000000207008 438595008 417992006 1 118168003 900000000000010007 900000000000451002 7111885023 20170731 1 900000000000207008 438595008 367643001 1 118168003 900000000000010007 900000000000451002 RESOLUTION: Stated Relationship inactivated as follows, to leave only 1 relationships in the group: 4428858023 20170731 0 900000000000207008 438595008 417992006 1 118168003 900000000000010007 900000000000451002 | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-231 | 3 MRCM failures for multiple Stated Relationship records per group | The following 3 born inactive Stated Relationship records have failed the MRCM tests: id effectivetime active moduleid sourceid destinationid relationshipgroup typeid characteristictypeid modifierid RESOLUTION: The three Stated Relationship records in question were removed by the SNOMED International Content team. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-254 | Issue found with new Stated Relationship | SNOMED International’s continuous Content quality review identified a change within the terminology that requires wider consideration - namely the addition of the following Stated Relationship: 6842860029 20170731 1 900000000000207008 80400009 3898006 0 116680003 900000000000010007 900000000000451002 RESOLUTION: This Stated relationship and the related Inferred relationships have therefore been removed pending further review, to ensure that the impact of this change within the hierarchy is fully communicated with appropriate consultation with the wider community of practice. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-255 | RVF Assertion failure: 89ceaf00-79b9-11e1-b0c4-0800200c9a66 | "assertionUuid": "89ceaf00-79b9-11e1-b0c4-0800200c9a66", "assertionText": "All stated relationships inactivated in current release must have been active in the previous release.", "failureCount": 1, "firstNInstances": [{"conceptId": "80400009","detail": "Stated relationship: id=6842860029 is inactive in the current release but no active state found in the previous snapshot."} RESOLUTION: Born Inactive record was removed accordingly. | ||||||||||||||||||||||||||||||||||||||||||||||
ISRS-256 | Unexpected control characters in TextDefinition records | The following textDefinition records have been found to have unexpected control characters contained within the text (just before the number of degrees in each case): 3476134011 20170731 1 900000000000207008 733525007 en 900000000000550004 Left anterior fascicular block is characterized by all of the following: Left-axis deviation with frontal QRS axis between 45° and 90°; Q wave in lead aVL; rS in inferior leads; QRS duration is 120 ms. 900000000000017005 RESOLUTION: The 3 textDefinition records have been updated accordingly, to remove the special characters. |
3.3 Actualizaciones técnicas
3.3.1 Convención para la denominación conjunto de referencias de Asociaciones
Para la Edición Internacional de enero de 2018 se mejoró la convención para denominar el archivo de referencias a Asociaciones.
ya no se lo denominará con esta convención:
'der2_cRefset_AssociationReferenceSnapshot_INT_[date].txt'
Se lo ha denominado:
'der2_cRefset_AssociationSnapshot_INT_[date].txt'
Por lo tanto, los tres archivos incluidos en la Edición Internacional de enero de 2018 se denominan:
- der2_cRefset_AssociationDelta_INT_20180131.txt
- der2_cRefset_AssociationFull_INT_20180131.txt
- der2_cRefset_AssociationSnapshot_INT_20180131.txt
3.3.2 Convención para la denominación del paquete de RF2
Con el fin de diferenciar entre las distintas versiones del paquete de publicación Producción, el cuarto elemento de la convención para la denominación ahora especificara "MEMBER" para publicaciones de los miembros y "PRODUCTION" para las publicaciones finales públicas.
Por lo tanto, la publicación para miembros realizada el 31 de diciembre de 2017 para la Edición Internacional de enero de 2018 se denominará:
SnomedCT_InternationalRF2_MEMBER_20180131T120000Z.zip
Mientras que la edición Pública realizada el 31 de enero de 2018 para la Edición Internacional de enero de 2018 se denominará:
SnomedCT_InternationalRF2_PRODUCTION_20180131T120000Z.zip
3.3.7 Formato del paquete de RF2
Para referencia futura, la convención para el paquete de ficheros RF2 establece que contiene todos los ficheros relevantes, independientemente de que incluyan registros en cada publicación en particular. Por lo tanto, el paquete contiene una mezcla de archivos, con filas tanto de encabezado como de contenido, y también ficheros que intencionalmente están en blanco (cuyo contenido sólo incluye un registro de encabezado). El motivo para no eliminar estos ficheros del paquete es establecer una distinción clara entre
- ...ficheros obsoletos (y que por lo tanto han sido retirados del paquete por completo), debido a que el contenido ya no es relevante para RF2 en esta publicación o en publicaciones futuras y
- ...ficheros que sólo no contienen datos en esta publicación en particular (y que por lo tanto se incluyen en el paquete pero quedan en blanco sólo con la fila de encabezado), pero que aún son relevantes para RF2 y podrían contener datos en publicaciones futuras.
Esto permite que los usuarios distingan fácilmente entre los ficheros que han sido que se han eliminado adrede o no, ya que de lo contrario si los ficheros mencionados en la opción 2 fueran excluidos del paquete esto podría interpretarse como un error y no como una falta de contenido intencional en esa edición.
3.3.8 Visibilidad temprana de un cambio inminente en la Edición Internacional de julio de 2018
Véase la siguiente página para consultar los detalles de los próximos cambios planeados para la edición de julio de 2018 y posteriores: Early Visibility - Planned improvements to upcoming SNOMED International Release packages.
Aprobaciones
Versión final | Fecha | Aprobado por | Comentarios |
---|---|---|---|
Descargar el .pdf aquí:
Borrador del Historial de Cambios
Versión | Fecha | Editor | Comentarios |
---|---|---|---|
0.1 | 20171108 | Andrew Atkinson | Primer borrador para revisión y comentarios |
0.1 | 20171115 | Lesley MacNeil | Se apregó a Paul Amos para Aprobación en ausencia de Jim Case - También se señala a MBR que debe notificar por anticipado la nueva política de uso de WAS A |
1.0 | 20171120 | Andrew Atkinson | Se completaron las actualizaciones técnicas finales |
1.1 | 20180129 | Andrew Atkinson | Actualización de los últimos paquetes de edición para los Miembros |