0.9.0 - ci-build
VigiCanPY - Local Development build (v0.9.0). See the Directory of published versions
Active as of 2023-07-19 |
Definitions for the ModeloLogicoRegistroCaso logical model.
Guidance on how to interpret the contents of this table can be found here.
1. ModeloLogicoRegistroCaso | |
Definition | Modelo Lógico de Registro de Caso - Corresponde a la Interaccion 01-Registrar Caso |
Control | 0..? |
2. ModeloLogicoRegistroCaso.establecimiento | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
3. ModeloLogicoRegistroCaso.establecimiento.establecimientoCodigo | |
Definition | Codigo del Establecimiento Generador de la Ficha |
Control | 1..1 |
Binding | The codes SHALL be taken from Establecimientos PY (set) |
Type | Coding |
4. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento | |
Definition | Servicio o Departamento del Establecimiento de Salud |
Control | 1..1 |
Binding | The codes SHALL be taken from Servicio o Departamento (set) |
Type | Coding |
5. ModeloLogicoRegistroCaso.ficha | |
Definition | Datos de la Ficha |
Control | 1..1 |
Type | BackboneElement |
6. ModeloLogicoRegistroCaso.ficha.numeroLocalRegistro | |
Definition | Numero asignado por el sistema generador del caso |
Control | 0..1 |
Type | Identifier |
7. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro | |
Definition | En caso de alta, lo asigna el sistema receptor |
Control | 0..1 |
Type | Identifier |
8. ModeloLogicoRegistroCaso.ficha.fechaNotificacion | |
Definition | Fecha en la que el Establecimiento de Salud notifica al registro |
Control | 0..1 |
Type | dateTime |
9. ModeloLogicoRegistroCaso.paciente | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
10. ModeloLogicoRegistroCaso.paciente.tipoDocumento | |
Definition | Tipo de identificación del paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipo de Documento (set) |
Type | Coding |
11. ModeloLogicoRegistroCaso.paciente.numeroDocumento | |
Definition | Numero de documento del paciente |
Control | 1..1 |
Type | string |
12. ModeloLogicoRegistroCaso.paciente.primerNombre | |
Definition | Primer Nombre del Paciente |
Control | 1..1 |
Type | string |
13. ModeloLogicoRegistroCaso.paciente.segundoNombre | |
Definition | Segundo Nombre del Paciente |
Control | 0..1 |
Type | string |
14. ModeloLogicoRegistroCaso.paciente.primerApellido | |
Definition | Primer Apellido del Paciente |
Control | 1..1 |
Type | string |
15. ModeloLogicoRegistroCaso.paciente.segundoAPellido | |
Definition | Segundo Apellido del Paciente |
Control | 0..1 |
Type | string |
16. ModeloLogicoRegistroCaso.paciente.nombreSocial | |
Definition | Nombre Social del Paciente |
Control | 0..1 |
Type | string |
17. ModeloLogicoRegistroCaso.paciente.fechaNacimiento | |
Definition | Fecha de Nacimiento |
Control | 1..1 |
Type | dateTime |
18. ModeloLogicoRegistroCaso.paciente.nacionalidad | |
Definition | Codigo de Nacionalidad del Paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
19. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica | |
Definition | Aplica Pueblo Indigena |
Control | 1..1 |
Type | boolean |
20. ModeloLogicoRegistroCaso.paciente.puebloIndigena | |
Definition | Codigo de Pueblo Indigena - solo si aplica |
Control | 0..1 |
Binding | The codes SHALL be taken from Pueblos Indigenas Paraguay (set) |
Type | Coding |
21. ModeloLogicoRegistroCaso.paciente.sexo | |
Definition | Sexo del Paciente |
Control | 1..1 |
Type | code |
22. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais | |
Definition | Lugar de Nacimiento - Pais |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
23. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento | |
Definition | Lugar de Nacimiento - Departamento - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
24. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad | |
Definition | Lugar de Nacimiento - Ciudad - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
25. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento | |
Definition | Lugar de Residencia Habitual - Departamento |
Control | 1..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
26. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito | |
Definition | Lugar de Residencia Habitual - Distrito/Ciudad |
Control | 1..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
27. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio | |
Definition | Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento |
Control | 1..1 |
Binding | The codes SHALL be taken from Barrios Paraguay (set) |
Type | Coding |
28. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea | |
Definition | Lugar de Residencia Habitual - Tipo de Area |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipos de Area Paraguay (set) |
Type | Coding |
29. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion | |
Definition | Lugar de Residencia Habitual - Dirección |
Control | 1..1 |
Type | string |
30. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa | |
Definition | Lugar de Residencia Habitual - Numero de Casa |
Control | 1..1 |
Type | string |
31. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono | |
Definition | Lugar de Residencia Habitual - Telefono |
Control | 1..1 |
Type | ContactPoint |
32. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto | |
Definition | Lugar de Residencia Habitual - Numero de Contacto |
Control | 1..1 |
Type | ContactPoint |
33. ModeloLogicoRegistroCaso.tumor | |
Definition | Informacion sobre el Tumor |
Control | 1..1 |
Type | BackboneElement |
34. ModeloLogicoRegistroCaso.tumor.fechaDiagnostico | |
Definition | Fecha de Diagnóstico |
Control | 1..1 |
Type | dateTime |
35. ModeloLogicoRegistroCaso.tumor.edadDiagnostico | |
Definition | Edad al Diagnóstico |
Control | 1..1 |
Type | Age |
36. ModeloLogicoRegistroCaso.tumor.baseDiagnostico | |
Definition | Método de diagnóstico más exacto utilizado. |
Control | 1..1 |
Binding | The codes SHALL be taken from Base Diagnostica de Tumor (set) |
Type | Coding |
37. ModeloLogicoRegistroCaso.tumor.textoDiagnostico | |
Definition | Texto libre para descripción del tumor |
Control | 1..1 |
Type | string |
38. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria | |
Definition | Localización anatómica del tumor (topografía) |
Control | 1..1 |
Binding | The codes SHALL be taken from Localizacion Primaria de Tumor (set) |
Type | Coding |
39. ModeloLogicoRegistroCaso.tumor.morfologia | |
Definition | Tipo histológico del tumor. Codificación y tipo |
Control | 1..1 |
Binding | The codes SHALL be taken from Morfologia de Tumor (set) |
Type | Coding |
40. ModeloLogicoRegistroCaso.tumor.comportamientoTumor | |
Definition | Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O |
Control | 1..1 |
Binding | The codes SHALL be taken from Comportamiento de Tumor (set) |
Type | Coding |
41. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica | |
Definition | Indica el grado de diferenciación histològica del tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Grado de Diferenciacion Histologica (set) |
Type | Coding |
42. ModeloLogicoRegistroCaso.tumor.lateralidad | |
Definition | Lateralidad del Tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Lateralidad (set) |
Type | Coding |
43. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT | |
Definition | Estadío Tumor Primario (T) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Tumor Primario -T- (set) |
Type | Coding |
44. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN | |
Definition | Estadío Nodos Regionales (N) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Nodos Regionales -N- (set) |
Type | Coding |
45. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM | |
Definition | Estadío Presencia Metástasis (M) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Presencia Metastasis -M- (set) |
Type | Coding |
46. ModeloLogicoRegistroCaso.notificante | |
Definition | Informacion sobre Profesional que Notifica |
Control | 1..1 |
Type | BackboneElement |
47. ModeloLogicoRegistroCaso.notificante.identificacionProfesional | |
Definition | Número de Identificación del Profesional que realiza la notificación |
Control | 1..1 |
Type | Identifier |
48. ModeloLogicoRegistroCaso.notificante.especialidadProfesional | |
Definition | Especialidad del profesional que realiza la notificación |
Control | 1..1 |
Binding | The codes SHALL be taken from Especialidades de Profesionales (set) |
Type | Coding |
49. ModeloLogicoRegistroCaso.notificante.apellidoProfesional | |
Definition | Apellido del profesional que realiza la notificación |
Control | 1..1 |
Type | string |
50. ModeloLogicoRegistroCaso.notificante.nombreProfesional | |
Definition | Nombre del profesional que realiza la notificación |
Control | 1..1 |
Type | string |
Guidance on how to interpret the contents of this table can be found here.
1. ModeloLogicoRegistroCaso | |
Definition | Modelo Lógico de Registro de Caso - Corresponde a la Interaccion 01-Registrar Caso Base definition for all elements in a resource. |
Control | 0..* This element is affected by the following invariants: ele-1 |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
2. ModeloLogicoRegistroCaso.establecimiento | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
3. ModeloLogicoRegistroCaso.establecimiento.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
4. ModeloLogicoRegistroCaso.establecimiento.establecimientoCodigo | |
Definition | Codigo del Establecimiento Generador de la Ficha |
Control | 1..1 |
Binding | The codes SHALL be taken from Establecimientos PY (set) |
Type | Coding |
5. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento | |
Definition | Servicio o Departamento del Establecimiento de Salud |
Control | 1..1 |
Binding | The codes SHALL be taken from Servicio o Departamento (set) |
Type | Coding |
6. ModeloLogicoRegistroCaso.ficha | |
Definition | Datos de la Ficha |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
7. ModeloLogicoRegistroCaso.ficha.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
8. ModeloLogicoRegistroCaso.ficha.numeroLocalRegistro | |
Definition | Numero asignado por el sistema generador del caso |
Control | 0..1 |
Type | Identifier |
9. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro | |
Definition | En caso de alta, lo asigna el sistema receptor |
Control | 0..1 |
Type | Identifier |
10. ModeloLogicoRegistroCaso.ficha.fechaNotificacion | |
Definition | Fecha en la que el Establecimiento de Salud notifica al registro |
Control | 0..1 |
Type | dateTime |
11. ModeloLogicoRegistroCaso.paciente | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
12. ModeloLogicoRegistroCaso.paciente.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
13. ModeloLogicoRegistroCaso.paciente.tipoDocumento | |
Definition | Tipo de identificación del paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipo de Documento (set) |
Type | Coding |
14. ModeloLogicoRegistroCaso.paciente.numeroDocumento | |
Definition | Numero de documento del paciente |
Control | 1..1 |
Type | string |
15. ModeloLogicoRegistroCaso.paciente.primerNombre | |
Definition | Primer Nombre del Paciente |
Control | 1..1 |
Type | string |
16. ModeloLogicoRegistroCaso.paciente.segundoNombre | |
Definition | Segundo Nombre del Paciente |
Control | 0..1 |
Type | string |
17. ModeloLogicoRegistroCaso.paciente.primerApellido | |
Definition | Primer Apellido del Paciente |
Control | 1..1 |
Type | string |
18. ModeloLogicoRegistroCaso.paciente.segundoAPellido | |
Definition | Segundo Apellido del Paciente |
Control | 0..1 |
Type | string |
19. ModeloLogicoRegistroCaso.paciente.nombreSocial | |
Definition | Nombre Social del Paciente |
Control | 0..1 |
Type | string |
20. ModeloLogicoRegistroCaso.paciente.fechaNacimiento | |
Definition | Fecha de Nacimiento |
Control | 1..1 |
Type | dateTime |
21. ModeloLogicoRegistroCaso.paciente.nacionalidad | |
Definition | Codigo de Nacionalidad del Paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
22. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica | |
Definition | Aplica Pueblo Indigena |
Control | 1..1 |
Type | boolean |
23. ModeloLogicoRegistroCaso.paciente.puebloIndigena | |
Definition | Codigo de Pueblo Indigena - solo si aplica |
Control | 0..1 |
Binding | The codes SHALL be taken from Pueblos Indigenas Paraguay (set) |
Type | Coding |
24. ModeloLogicoRegistroCaso.paciente.sexo | |
Definition | Sexo del Paciente |
Control | 1..1 |
Type | code |
25. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais | |
Definition | Lugar de Nacimiento - Pais |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
26. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento | |
Definition | Lugar de Nacimiento - Departamento - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
27. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad | |
Definition | Lugar de Nacimiento - Ciudad - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
28. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento | |
Definition | Lugar de Residencia Habitual - Departamento |
Control | 1..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
29. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito | |
Definition | Lugar de Residencia Habitual - Distrito/Ciudad |
Control | 1..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
30. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio | |
Definition | Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento |
Control | 1..1 |
Binding | The codes SHALL be taken from Barrios Paraguay (set) |
Type | Coding |
31. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea | |
Definition | Lugar de Residencia Habitual - Tipo de Area |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipos de Area Paraguay (set) |
Type | Coding |
32. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion | |
Definition | Lugar de Residencia Habitual - Dirección |
Control | 1..1 |
Type | string |
33. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa | |
Definition | Lugar de Residencia Habitual - Numero de Casa |
Control | 1..1 |
Type | string |
34. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono | |
Definition | Lugar de Residencia Habitual - Telefono |
Control | 1..1 |
Type | ContactPoint |
35. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto | |
Definition | Lugar de Residencia Habitual - Numero de Contacto |
Control | 1..1 |
Type | ContactPoint |
36. ModeloLogicoRegistroCaso.tumor | |
Definition | Informacion sobre el Tumor |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
37. ModeloLogicoRegistroCaso.tumor.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
38. ModeloLogicoRegistroCaso.tumor.fechaDiagnostico | |
Definition | Fecha de Diagnóstico |
Control | 1..1 |
Type | dateTime |
39. ModeloLogicoRegistroCaso.tumor.edadDiagnostico | |
Definition | Edad al Diagnóstico |
Control | 1..1 |
Type | Age |
40. ModeloLogicoRegistroCaso.tumor.baseDiagnostico | |
Definition | Método de diagnóstico más exacto utilizado. |
Control | 1..1 |
Binding | The codes SHALL be taken from Base Diagnostica de Tumor (set) |
Type | Coding |
41. ModeloLogicoRegistroCaso.tumor.textoDiagnostico | |
Definition | Texto libre para descripción del tumor |
Control | 1..1 |
Type | string |
42. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria | |
Definition | Localización anatómica del tumor (topografía) |
Control | 1..1 |
Binding | The codes SHALL be taken from Localizacion Primaria de Tumor (set) |
Type | Coding |
43. ModeloLogicoRegistroCaso.tumor.morfologia | |
Definition | Tipo histológico del tumor. Codificación y tipo |
Control | 1..1 |
Binding | The codes SHALL be taken from Morfologia de Tumor (set) |
Type | Coding |
44. ModeloLogicoRegistroCaso.tumor.comportamientoTumor | |
Definition | Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O |
Control | 1..1 |
Binding | The codes SHALL be taken from Comportamiento de Tumor (set) |
Type | Coding |
45. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica | |
Definition | Indica el grado de diferenciación histològica del tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Grado de Diferenciacion Histologica (set) |
Type | Coding |
46. ModeloLogicoRegistroCaso.tumor.lateralidad | |
Definition | Lateralidad del Tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Lateralidad (set) |
Type | Coding |
47. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT | |
Definition | Estadío Tumor Primario (T) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Tumor Primario -T- (set) |
Type | Coding |
48. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN | |
Definition | Estadío Nodos Regionales (N) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Nodos Regionales -N- (set) |
Type | Coding |
49. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM | |
Definition | Estadío Presencia Metástasis (M) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Presencia Metastasis -M- (set) |
Type | Coding |
50. ModeloLogicoRegistroCaso.notificante | |
Definition | Informacion sobre Profesional que Notifica |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
51. ModeloLogicoRegistroCaso.notificante.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
52. ModeloLogicoRegistroCaso.notificante.identificacionProfesional | |
Definition | Número de Identificación del Profesional que realiza la notificación |
Control | 1..1 |
Type | Identifier |
53. ModeloLogicoRegistroCaso.notificante.especialidadProfesional | |
Definition | Especialidad del profesional que realiza la notificación |
Control | 1..1 |
Binding | The codes SHALL be taken from Especialidades de Profesionales (set) |
Type | Coding |
54. ModeloLogicoRegistroCaso.notificante.apellidoProfesional | |
Definition | Apellido del profesional que realiza la notificación |
Control | 1..1 |
Type | string |
55. ModeloLogicoRegistroCaso.notificante.nombreProfesional | |
Definition | Nombre del profesional que realiza la notificación |
Control | 1..1 |
Type | string |
Guidance on how to interpret the contents of this table can be found here.
1. ModeloLogicoRegistroCaso | |
Definition | Modelo Lógico de Registro de Caso - Corresponde a la Interaccion 01-Registrar Caso |
Control | 0..* This element is affected by the following invariants: ele-1 |
2. ModeloLogicoRegistroCaso.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
3. ModeloLogicoRegistroCaso.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
4. ModeloLogicoRegistroCaso.establecimiento | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
5. ModeloLogicoRegistroCaso.establecimiento.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
6. ModeloLogicoRegistroCaso.establecimiento.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.establecimiento.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
7. ModeloLogicoRegistroCaso.establecimiento.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
8. ModeloLogicoRegistroCaso.establecimiento.establecimientoCodigo | |
Definition | Codigo del Establecimiento Generador de la Ficha |
Control | 1..1 |
Binding | The codes SHALL be taken from Establecimientos PY (set) |
Type | Coding |
9. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento | |
Definition | Servicio o Departamento del Establecimiento de Salud |
Control | 1..1 |
Binding | The codes SHALL be taken from Servicio o Departamento (set) |
Type | Coding |
10. ModeloLogicoRegistroCaso.ficha | |
Definition | Datos de la Ficha |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
11. ModeloLogicoRegistroCaso.ficha.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
12. ModeloLogicoRegistroCaso.ficha.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.ficha.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
13. ModeloLogicoRegistroCaso.ficha.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
14. ModeloLogicoRegistroCaso.ficha.numeroLocalRegistro | |
Definition | Numero asignado por el sistema generador del caso |
Control | 0..1 |
Type | Identifier |
15. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro | |
Definition | En caso de alta, lo asigna el sistema receptor |
Control | 0..1 |
Type | Identifier |
16. ModeloLogicoRegistroCaso.ficha.fechaNotificacion | |
Definition | Fecha en la que el Establecimiento de Salud notifica al registro |
Control | 0..1 |
Type | dateTime |
17. ModeloLogicoRegistroCaso.paciente | |
Definition | Datos Generales del Establecimiento |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
18. ModeloLogicoRegistroCaso.paciente.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
19. ModeloLogicoRegistroCaso.paciente.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.paciente.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
20. ModeloLogicoRegistroCaso.paciente.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
21. ModeloLogicoRegistroCaso.paciente.tipoDocumento | |
Definition | Tipo de identificación del paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipo de Documento (set) |
Type | Coding |
22. ModeloLogicoRegistroCaso.paciente.numeroDocumento | |
Definition | Numero de documento del paciente |
Control | 1..1 |
Type | string |
23. ModeloLogicoRegistroCaso.paciente.primerNombre | |
Definition | Primer Nombre del Paciente |
Control | 1..1 |
Type | string |
24. ModeloLogicoRegistroCaso.paciente.segundoNombre | |
Definition | Segundo Nombre del Paciente |
Control | 0..1 |
Type | string |
25. ModeloLogicoRegistroCaso.paciente.primerApellido | |
Definition | Primer Apellido del Paciente |
Control | 1..1 |
Type | string |
26. ModeloLogicoRegistroCaso.paciente.segundoAPellido | |
Definition | Segundo Apellido del Paciente |
Control | 0..1 |
Type | string |
27. ModeloLogicoRegistroCaso.paciente.nombreSocial | |
Definition | Nombre Social del Paciente |
Control | 0..1 |
Type | string |
28. ModeloLogicoRegistroCaso.paciente.fechaNacimiento | |
Definition | Fecha de Nacimiento |
Control | 1..1 |
Type | dateTime |
29. ModeloLogicoRegistroCaso.paciente.nacionalidad | |
Definition | Codigo de Nacionalidad del Paciente |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
30. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica | |
Definition | Aplica Pueblo Indigena |
Control | 1..1 |
Type | boolean |
31. ModeloLogicoRegistroCaso.paciente.puebloIndigena | |
Definition | Codigo de Pueblo Indigena - solo si aplica |
Control | 0..1 |
Binding | The codes SHALL be taken from Pueblos Indigenas Paraguay (set) |
Type | Coding |
32. ModeloLogicoRegistroCaso.paciente.sexo | |
Definition | Sexo del Paciente |
Control | 1..1 |
Type | code |
33. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais | |
Definition | Lugar de Nacimiento - Pais |
Control | 1..1 |
Binding | The codes SHALL be taken from Paises |
Type | Coding |
34. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento | |
Definition | Lugar de Nacimiento - Departamento - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
35. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad | |
Definition | Lugar de Nacimiento - Ciudad - solo si es Nac-PY |
Control | 0..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
36. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento | |
Definition | Lugar de Residencia Habitual - Departamento |
Control | 1..1 |
Binding | The codes SHALL be taken from Departamentos Paraguay (set) |
Type | Coding |
37. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito | |
Definition | Lugar de Residencia Habitual - Distrito/Ciudad |
Control | 1..1 |
Binding | The codes SHALL be taken from Ciudades Paraguay (set) |
Type | Coding |
38. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio | |
Definition | Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento |
Control | 1..1 |
Binding | The codes SHALL be taken from Barrios Paraguay (set) |
Type | Coding |
39. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea | |
Definition | Lugar de Residencia Habitual - Tipo de Area |
Control | 1..1 |
Binding | The codes SHALL be taken from Tipos de Area Paraguay (set) |
Type | Coding |
40. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion | |
Definition | Lugar de Residencia Habitual - Dirección |
Control | 1..1 |
Type | string |
41. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa | |
Definition | Lugar de Residencia Habitual - Numero de Casa |
Control | 1..1 |
Type | string |
42. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono | |
Definition | Lugar de Residencia Habitual - Telefono |
Control | 1..1 |
Type | ContactPoint |
43. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto | |
Definition | Lugar de Residencia Habitual - Numero de Contacto |
Control | 1..1 |
Type | ContactPoint |
44. ModeloLogicoRegistroCaso.tumor | |
Definition | Informacion sobre el Tumor |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
45. ModeloLogicoRegistroCaso.tumor.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
46. ModeloLogicoRegistroCaso.tumor.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.tumor.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
47. ModeloLogicoRegistroCaso.tumor.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
48. ModeloLogicoRegistroCaso.tumor.fechaDiagnostico | |
Definition | Fecha de Diagnóstico |
Control | 1..1 |
Type | dateTime |
49. ModeloLogicoRegistroCaso.tumor.edadDiagnostico | |
Definition | Edad al Diagnóstico |
Control | 1..1 |
Type | Age |
50. ModeloLogicoRegistroCaso.tumor.baseDiagnostico | |
Definition | Método de diagnóstico más exacto utilizado. |
Control | 1..1 |
Binding | The codes SHALL be taken from Base Diagnostica de Tumor (set) |
Type | Coding |
51. ModeloLogicoRegistroCaso.tumor.textoDiagnostico | |
Definition | Texto libre para descripción del tumor |
Control | 1..1 |
Type | string |
52. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria | |
Definition | Localización anatómica del tumor (topografía) |
Control | 1..1 |
Binding | The codes SHALL be taken from Localizacion Primaria de Tumor (set) |
Type | Coding |
53. ModeloLogicoRegistroCaso.tumor.morfologia | |
Definition | Tipo histológico del tumor. Codificación y tipo |
Control | 1..1 |
Binding | The codes SHALL be taken from Morfologia de Tumor (set) |
Type | Coding |
54. ModeloLogicoRegistroCaso.tumor.comportamientoTumor | |
Definition | Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O |
Control | 1..1 |
Binding | The codes SHALL be taken from Comportamiento de Tumor (set) |
Type | Coding |
55. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica | |
Definition | Indica el grado de diferenciación histològica del tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Grado de Diferenciacion Histologica (set) |
Type | Coding |
56. ModeloLogicoRegistroCaso.tumor.lateralidad | |
Definition | Lateralidad del Tumor |
Control | 1..1 |
Binding | The codes SHALL be taken from Lateralidad (set) |
Type | Coding |
57. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT | |
Definition | Estadío Tumor Primario (T) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Tumor Primario -T- (set) |
Type | Coding |
58. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN | |
Definition | Estadío Nodos Regionales (N) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Nodos Regionales -N- (set) |
Type | Coding |
59. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM | |
Definition | Estadío Presencia Metástasis (M) |
Control | 1..1 |
Binding | The codes SHALL be taken from Estadio Presencia Metastasis -M- (set) |
Type | Coding |
60. ModeloLogicoRegistroCaso.notificante | |
Definition | Informacion sobre Profesional que Notifica |
Control | 1..1 |
Type | BackboneElement |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) |
61. ModeloLogicoRegistroCaso.notificante.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
XML Representation | In the XML format, this property is represented as an attribute. |
Summary | false |
62. ModeloLogicoRegistroCaso.notificante.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Summary | false |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
Slicing | This element introduces a set of slices on ModeloLogicoRegistroCaso.notificante.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
63. ModeloLogicoRegistroCaso.notificante.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Summary | true |
Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() or (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
64. ModeloLogicoRegistroCaso.notificante.identificacionProfesional | |
Definition | Número de Identificación del Profesional que realiza la notificación |
Control | 1..1 |
Type | Identifier |
65. ModeloLogicoRegistroCaso.notificante.especialidadProfesional | |
Definition | Especialidad del profesional que realiza la notificación |
Control | 1..1 |
Binding | The codes SHALL be taken from Especialidades de Profesionales (set) |
Type | Coding |
66. ModeloLogicoRegistroCaso.notificante.apellidoProfesional | |
Definition | Apellido del profesional que realiza la notificación |
Control | 1..1 |
Type | string |
67. ModeloLogicoRegistroCaso.notificante.nombreProfesional | |
Definition | Nombre del profesional que realiza la notificación |
Control | 1..1 |
Type | string |