0.9.0 - ci-build

VigiCanPY - Local Development build (v0.9.0). See the Directory of published versions

Logical Model: ModeloLogicoRegistroCaso - Detailed Descriptions

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

Control0..?
2. ModeloLogicoRegistroCaso.establecimiento
Definition

Datos Generales del Establecimiento

Control1..1
TypeBackboneElement
3. ModeloLogicoRegistroCaso.establecimiento.establecimientoCodigo
Definition

Codigo del Establecimiento Generador de la Ficha

Control1..1
BindingThe codes SHALL be taken from Establecimientos PY (set)
TypeCoding
4. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento
Definition

Servicio o Departamento del Establecimiento de Salud

Control1..1
BindingThe codes SHALL be taken from Servicio o Departamento (set)
TypeCoding
5. ModeloLogicoRegistroCaso.ficha
Definition

Datos de la Ficha

Control1..1
TypeBackboneElement
6. ModeloLogicoRegistroCaso.ficha.numeroLocalRegistro
Definition

Numero asignado por el sistema generador del caso

Control0..1
TypeIdentifier
7. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro
Definition

En caso de alta, lo asigna el sistema receptor

Control0..1
TypeIdentifier
8. ModeloLogicoRegistroCaso.ficha.fechaNotificacion
Definition

Fecha en la que el Establecimiento de Salud notifica al registro

Control0..1
TypedateTime
9. ModeloLogicoRegistroCaso.paciente
Definition

Datos Generales del Establecimiento

Control1..1
TypeBackboneElement
10. ModeloLogicoRegistroCaso.paciente.tipoDocumento
Definition

Tipo de identificación del paciente

Control1..1
BindingThe codes SHALL be taken from Tipo de Documento (set)
TypeCoding
11. ModeloLogicoRegistroCaso.paciente.numeroDocumento
Definition

Numero de documento del paciente

Control1..1
Typestring
12. ModeloLogicoRegistroCaso.paciente.primerNombre
Definition

Primer Nombre del Paciente

Control1..1
Typestring
13. ModeloLogicoRegistroCaso.paciente.segundoNombre
Definition

Segundo Nombre del Paciente

Control0..1
Typestring
14. ModeloLogicoRegistroCaso.paciente.primerApellido
Definition

Primer Apellido del Paciente

Control1..1
Typestring
15. ModeloLogicoRegistroCaso.paciente.segundoAPellido
Definition

Segundo Apellido del Paciente

Control0..1
Typestring
16. ModeloLogicoRegistroCaso.paciente.nombreSocial
Definition

Nombre Social del Paciente

Control0..1
Typestring
17. ModeloLogicoRegistroCaso.paciente.fechaNacimiento
Definition

Fecha de Nacimiento

Control1..1
TypedateTime
18. ModeloLogicoRegistroCaso.paciente.nacionalidad
Definition

Codigo de Nacionalidad del Paciente

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
19. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica
Definition

Aplica Pueblo Indigena

Control1..1
Typeboolean
20. ModeloLogicoRegistroCaso.paciente.puebloIndigena
Definition

Codigo de Pueblo Indigena - solo si aplica

Control0..1
BindingThe codes SHALL be taken from Pueblos Indigenas Paraguay (set)
TypeCoding
21. ModeloLogicoRegistroCaso.paciente.sexo
Definition

Sexo del Paciente

Control1..1
Typecode
22. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais
Definition

Lugar de Nacimiento - Pais

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
23. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento
Definition

Lugar de Nacimiento - Departamento - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
24. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad
Definition

Lugar de Nacimiento - Ciudad - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
25. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento
Definition

Lugar de Residencia Habitual - Departamento

Control1..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
26. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito
Definition

Lugar de Residencia Habitual - Distrito/Ciudad

Control1..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
27. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio
Definition

Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento

Control1..1
BindingThe codes SHALL be taken from Barrios Paraguay (set)
TypeCoding
28. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea
Definition

Lugar de Residencia Habitual - Tipo de Area

Control1..1
BindingThe codes SHALL be taken from Tipos de Area Paraguay (set)
TypeCoding
29. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion
Definition

Lugar de Residencia Habitual - Dirección

Control1..1
Typestring
30. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa
Definition

Lugar de Residencia Habitual - Numero de Casa

Control1..1
Typestring
31. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono
Definition

Lugar de Residencia Habitual - Telefono

Control1..1
TypeContactPoint
32. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto
Definition

Lugar de Residencia Habitual - Numero de Contacto

Control1..1
TypeContactPoint
33. ModeloLogicoRegistroCaso.tumor
Definition

Informacion sobre el Tumor

Control1..1
TypeBackboneElement
34. ModeloLogicoRegistroCaso.tumor.fechaDiagnostico
Definition

Fecha de Diagnóstico

Control1..1
TypedateTime
35. ModeloLogicoRegistroCaso.tumor.edadDiagnostico
Definition

Edad al Diagnóstico

Control1..1
TypeAge
36. ModeloLogicoRegistroCaso.tumor.baseDiagnostico
Definition

Método de diagnóstico más exacto utilizado.

Control1..1
BindingThe codes SHALL be taken from Base Diagnostica de Tumor (set)
TypeCoding
37. ModeloLogicoRegistroCaso.tumor.textoDiagnostico
Definition

Texto libre para descripción del tumor

Control1..1
Typestring
38. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria
Definition

Localización anatómica del tumor (topografía)

Control1..1
BindingThe codes SHALL be taken from Localizacion Primaria de Tumor (set)
TypeCoding
39. ModeloLogicoRegistroCaso.tumor.morfologia
Definition

Tipo histológico del tumor. Codificación y tipo

Control1..1
BindingThe codes SHALL be taken from Morfologia de Tumor (set)
TypeCoding
40. ModeloLogicoRegistroCaso.tumor.comportamientoTumor
Definition

Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O

Control1..1
BindingThe codes SHALL be taken from Comportamiento de Tumor (set)
TypeCoding
41. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica
Definition

Indica el grado de diferenciación histològica del tumor

Control1..1
BindingThe codes SHALL be taken from Grado de Diferenciacion Histologica (set)
TypeCoding
42. ModeloLogicoRegistroCaso.tumor.lateralidad
Definition

Lateralidad del Tumor

Control1..1
BindingThe codes SHALL be taken from Lateralidad (set)
TypeCoding
43. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT
Definition

Estadío Tumor Primario (T)

Control1..1
BindingThe codes SHALL be taken from Estadio Tumor Primario -T- (set)
TypeCoding
44. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN
Definition

Estadío Nodos Regionales (N)

Control1..1
BindingThe codes SHALL be taken from Estadio Nodos Regionales -N- (set)
TypeCoding
45. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM
Definition

Estadío Presencia Metástasis (M)

Control1..1
BindingThe codes SHALL be taken from Estadio Presencia Metastasis -M- (set)
TypeCoding
46. ModeloLogicoRegistroCaso.notificante
Definition

Informacion sobre Profesional que Notifica

Control1..1
TypeBackboneElement
47. ModeloLogicoRegistroCaso.notificante.identificacionProfesional
Definition

Número de Identificación del Profesional que realiza la notificación

Control1..1
TypeIdentifier
48. ModeloLogicoRegistroCaso.notificante.especialidadProfesional
Definition

Especialidad del profesional que realiza la notificación

Control1..1
BindingThe codes SHALL be taken from Especialidades de Profesionales (set)
TypeCoding
49. ModeloLogicoRegistroCaso.notificante.apellidoProfesional
Definition

Apellido del profesional que realiza la notificación

Control1..1
Typestring
50. ModeloLogicoRegistroCaso.notificante.nombreProfesional
Definition

Nombre del profesional que realiza la notificación

Control1..1
Typestring

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.

Control0..* This element is affected by the following invariants: ele-1
InvariantsDefined 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

Control1..1
TypeBackboneElement
InvariantsDefined 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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
BindingThe codes SHALL be taken from Establecimientos PY (set)
TypeCoding
5. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento
Definition

Servicio o Departamento del Establecimiento de Salud

Control1..1
BindingThe codes SHALL be taken from Servicio o Departamento (set)
TypeCoding
6. ModeloLogicoRegistroCaso.ficha
Definition

Datos de la Ficha

Control1..1
TypeBackboneElement
InvariantsDefined 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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control0..1
TypeIdentifier
9. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro
Definition

En caso de alta, lo asigna el sistema receptor

Control0..1
TypeIdentifier
10. ModeloLogicoRegistroCaso.ficha.fechaNotificacion
Definition

Fecha en la que el Establecimiento de Salud notifica al registro

Control0..1
TypedateTime
11. ModeloLogicoRegistroCaso.paciente
Definition

Datos Generales del Establecimiento

Control1..1
TypeBackboneElement
InvariantsDefined 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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
BindingThe codes SHALL be taken from Tipo de Documento (set)
TypeCoding
14. ModeloLogicoRegistroCaso.paciente.numeroDocumento
Definition

Numero de documento del paciente

Control1..1
Typestring
15. ModeloLogicoRegistroCaso.paciente.primerNombre
Definition

Primer Nombre del Paciente

Control1..1
Typestring
16. ModeloLogicoRegistroCaso.paciente.segundoNombre
Definition

Segundo Nombre del Paciente

Control0..1
Typestring
17. ModeloLogicoRegistroCaso.paciente.primerApellido
Definition

Primer Apellido del Paciente

Control1..1
Typestring
18. ModeloLogicoRegistroCaso.paciente.segundoAPellido
Definition

Segundo Apellido del Paciente

Control0..1
Typestring
19. ModeloLogicoRegistroCaso.paciente.nombreSocial
Definition

Nombre Social del Paciente

Control0..1
Typestring
20. ModeloLogicoRegistroCaso.paciente.fechaNacimiento
Definition

Fecha de Nacimiento

Control1..1
TypedateTime
21. ModeloLogicoRegistroCaso.paciente.nacionalidad
Definition

Codigo de Nacionalidad del Paciente

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
22. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica
Definition

Aplica Pueblo Indigena

Control1..1
Typeboolean
23. ModeloLogicoRegistroCaso.paciente.puebloIndigena
Definition

Codigo de Pueblo Indigena - solo si aplica

Control0..1
BindingThe codes SHALL be taken from Pueblos Indigenas Paraguay (set)
TypeCoding
24. ModeloLogicoRegistroCaso.paciente.sexo
Definition

Sexo del Paciente

Control1..1
Typecode
25. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais
Definition

Lugar de Nacimiento - Pais

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
26. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento
Definition

Lugar de Nacimiento - Departamento - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
27. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad
Definition

Lugar de Nacimiento - Ciudad - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
28. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento
Definition

Lugar de Residencia Habitual - Departamento

Control1..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
29. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito
Definition

Lugar de Residencia Habitual - Distrito/Ciudad

Control1..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
30. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio
Definition

Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento

Control1..1
BindingThe codes SHALL be taken from Barrios Paraguay (set)
TypeCoding
31. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea
Definition

Lugar de Residencia Habitual - Tipo de Area

Control1..1
BindingThe codes SHALL be taken from Tipos de Area Paraguay (set)
TypeCoding
32. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion
Definition

Lugar de Residencia Habitual - Dirección

Control1..1
Typestring
33. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa
Definition

Lugar de Residencia Habitual - Numero de Casa

Control1..1
Typestring
34. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono
Definition

Lugar de Residencia Habitual - Telefono

Control1..1
TypeContactPoint
35. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto
Definition

Lugar de Residencia Habitual - Numero de Contacto

Control1..1
TypeContactPoint
36. ModeloLogicoRegistroCaso.tumor
Definition

Informacion sobre el Tumor

Control1..1
TypeBackboneElement
InvariantsDefined 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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
TypedateTime
39. ModeloLogicoRegistroCaso.tumor.edadDiagnostico
Definition

Edad al Diagnóstico

Control1..1
TypeAge
40. ModeloLogicoRegistroCaso.tumor.baseDiagnostico
Definition

Método de diagnóstico más exacto utilizado.

Control1..1
BindingThe codes SHALL be taken from Base Diagnostica de Tumor (set)
TypeCoding
41. ModeloLogicoRegistroCaso.tumor.textoDiagnostico
Definition

Texto libre para descripción del tumor

Control1..1
Typestring
42. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria
Definition

Localización anatómica del tumor (topografía)

Control1..1
BindingThe codes SHALL be taken from Localizacion Primaria de Tumor (set)
TypeCoding
43. ModeloLogicoRegistroCaso.tumor.morfologia
Definition

Tipo histológico del tumor. Codificación y tipo

Control1..1
BindingThe codes SHALL be taken from Morfologia de Tumor (set)
TypeCoding
44. ModeloLogicoRegistroCaso.tumor.comportamientoTumor
Definition

Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O

Control1..1
BindingThe codes SHALL be taken from Comportamiento de Tumor (set)
TypeCoding
45. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica
Definition

Indica el grado de diferenciación histològica del tumor

Control1..1
BindingThe codes SHALL be taken from Grado de Diferenciacion Histologica (set)
TypeCoding
46. ModeloLogicoRegistroCaso.tumor.lateralidad
Definition

Lateralidad del Tumor

Control1..1
BindingThe codes SHALL be taken from Lateralidad (set)
TypeCoding
47. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT
Definition

Estadío Tumor Primario (T)

Control1..1
BindingThe codes SHALL be taken from Estadio Tumor Primario -T- (set)
TypeCoding
48. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN
Definition

Estadío Nodos Regionales (N)

Control1..1
BindingThe codes SHALL be taken from Estadio Nodos Regionales -N- (set)
TypeCoding
49. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM
Definition

Estadío Presencia Metástasis (M)

Control1..1
BindingThe codes SHALL be taken from Estadio Presencia Metastasis -M- (set)
TypeCoding
50. ModeloLogicoRegistroCaso.notificante
Definition

Informacion sobre Profesional que Notifica

Control1..1
TypeBackboneElement
InvariantsDefined 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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
TypeIdentifier
53. ModeloLogicoRegistroCaso.notificante.especialidadProfesional
Definition

Especialidad del profesional que realiza la notificación

Control1..1
BindingThe codes SHALL be taken from Especialidades de Profesionales (set)
TypeCoding
54. ModeloLogicoRegistroCaso.notificante.apellidoProfesional
Definition

Apellido del profesional que realiza la notificación

Control1..1
Typestring
55. ModeloLogicoRegistroCaso.notificante.nombreProfesional
Definition

Nombre del profesional que realiza la notificación

Control1..1
Typestring

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

Control0..* 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
4. ModeloLogicoRegistroCaso.establecimiento
Definition

Datos Generales del Establecimiento

Control1..1
TypeBackboneElement
InvariantsDefined 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.establecimiento.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
BindingThe codes SHALL be taken from Establecimientos PY (set)
TypeCoding
9. ModeloLogicoRegistroCaso.establecimiento.servicioDepartamento
Definition

Servicio o Departamento del Establecimiento de Salud

Control1..1
BindingThe codes SHALL be taken from Servicio o Departamento (set)
TypeCoding
10. ModeloLogicoRegistroCaso.ficha
Definition

Datos de la Ficha

Control1..1
TypeBackboneElement
InvariantsDefined 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.ficha.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control0..1
TypeIdentifier
15. ModeloLogicoRegistroCaso.ficha.numeroUnicoRegistro
Definition

En caso de alta, lo asigna el sistema receptor

Control0..1
TypeIdentifier
16. ModeloLogicoRegistroCaso.ficha.fechaNotificacion
Definition

Fecha en la que el Establecimiento de Salud notifica al registro

Control0..1
TypedateTime
17. ModeloLogicoRegistroCaso.paciente
Definition

Datos Generales del Establecimiento

Control1..1
TypeBackboneElement
InvariantsDefined 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.paciente.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
BindingThe codes SHALL be taken from Tipo de Documento (set)
TypeCoding
22. ModeloLogicoRegistroCaso.paciente.numeroDocumento
Definition

Numero de documento del paciente

Control1..1
Typestring
23. ModeloLogicoRegistroCaso.paciente.primerNombre
Definition

Primer Nombre del Paciente

Control1..1
Typestring
24. ModeloLogicoRegistroCaso.paciente.segundoNombre
Definition

Segundo Nombre del Paciente

Control0..1
Typestring
25. ModeloLogicoRegistroCaso.paciente.primerApellido
Definition

Primer Apellido del Paciente

Control1..1
Typestring
26. ModeloLogicoRegistroCaso.paciente.segundoAPellido
Definition

Segundo Apellido del Paciente

Control0..1
Typestring
27. ModeloLogicoRegistroCaso.paciente.nombreSocial
Definition

Nombre Social del Paciente

Control0..1
Typestring
28. ModeloLogicoRegistroCaso.paciente.fechaNacimiento
Definition

Fecha de Nacimiento

Control1..1
TypedateTime
29. ModeloLogicoRegistroCaso.paciente.nacionalidad
Definition

Codigo de Nacionalidad del Paciente

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
30. ModeloLogicoRegistroCaso.paciente.puebloIndigenaAplica
Definition

Aplica Pueblo Indigena

Control1..1
Typeboolean
31. ModeloLogicoRegistroCaso.paciente.puebloIndigena
Definition

Codigo de Pueblo Indigena - solo si aplica

Control0..1
BindingThe codes SHALL be taken from Pueblos Indigenas Paraguay (set)
TypeCoding
32. ModeloLogicoRegistroCaso.paciente.sexo
Definition

Sexo del Paciente

Control1..1
Typecode
33. ModeloLogicoRegistroCaso.paciente.lugarNacimientoPais
Definition

Lugar de Nacimiento - Pais

Control1..1
BindingThe codes SHALL be taken from Paises
TypeCoding
34. ModeloLogicoRegistroCaso.paciente.lugarNacimientoDepartamento
Definition

Lugar de Nacimiento - Departamento - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
35. ModeloLogicoRegistroCaso.paciente.lugarNacimientoCiudad
Definition

Lugar de Nacimiento - Ciudad - solo si es Nac-PY

Control0..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
36. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDepartamento
Definition

Lugar de Residencia Habitual - Departamento

Control1..1
BindingThe codes SHALL be taken from Departamentos Paraguay (set)
TypeCoding
37. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDistrito
Definition

Lugar de Residencia Habitual - Distrito/Ciudad

Control1..1
BindingThe codes SHALL be taken from Ciudades Paraguay (set)
TypeCoding
38. ModeloLogicoRegistroCaso.paciente.residenciaHabitualBarrio
Definition

Lugar de Residencia Habitual - Barrio/Compañia/Asentamiento

Control1..1
BindingThe codes SHALL be taken from Barrios Paraguay (set)
TypeCoding
39. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTipoArea
Definition

Lugar de Residencia Habitual - Tipo de Area

Control1..1
BindingThe codes SHALL be taken from Tipos de Area Paraguay (set)
TypeCoding
40. ModeloLogicoRegistroCaso.paciente.residenciaHabitualDireccion
Definition

Lugar de Residencia Habitual - Dirección

Control1..1
Typestring
41. ModeloLogicoRegistroCaso.paciente.residenciaHabitualNumeroCasa
Definition

Lugar de Residencia Habitual - Numero de Casa

Control1..1
Typestring
42. ModeloLogicoRegistroCaso.paciente.residenciaHabitualTelefono
Definition

Lugar de Residencia Habitual - Telefono

Control1..1
TypeContactPoint
43. ModeloLogicoRegistroCaso.paciente.residenciaHabitualContacto
Definition

Lugar de Residencia Habitual - Numero de Contacto

Control1..1
TypeContactPoint
44. ModeloLogicoRegistroCaso.tumor
Definition

Informacion sobre el Tumor

Control1..1
TypeBackboneElement
InvariantsDefined 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.tumor.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
TypedateTime
49. ModeloLogicoRegistroCaso.tumor.edadDiagnostico
Definition

Edad al Diagnóstico

Control1..1
TypeAge
50. ModeloLogicoRegistroCaso.tumor.baseDiagnostico
Definition

Método de diagnóstico más exacto utilizado.

Control1..1
BindingThe codes SHALL be taken from Base Diagnostica de Tumor (set)
TypeCoding
51. ModeloLogicoRegistroCaso.tumor.textoDiagnostico
Definition

Texto libre para descripción del tumor

Control1..1
Typestring
52. ModeloLogicoRegistroCaso.tumor.localizacionPrimaria
Definition

Localización anatómica del tumor (topografía)

Control1..1
BindingThe codes SHALL be taken from Localizacion Primaria de Tumor (set)
TypeCoding
53. ModeloLogicoRegistroCaso.tumor.morfologia
Definition

Tipo histológico del tumor. Codificación y tipo

Control1..1
BindingThe codes SHALL be taken from Morfologia de Tumor (set)
TypeCoding
54. ModeloLogicoRegistroCaso.tumor.comportamientoTumor
Definition

Comportamiento del tumor notificado. Con relación a las recomendaciones del CIE-O

Control1..1
BindingThe codes SHALL be taken from Comportamiento de Tumor (set)
TypeCoding
55. ModeloLogicoRegistroCaso.tumor.gradoDiferenciacionHistologica
Definition

Indica el grado de diferenciación histològica del tumor

Control1..1
BindingThe codes SHALL be taken from Grado de Diferenciacion Histologica (set)
TypeCoding
56. ModeloLogicoRegistroCaso.tumor.lateralidad
Definition

Lateralidad del Tumor

Control1..1
BindingThe codes SHALL be taken from Lateralidad (set)
TypeCoding
57. ModeloLogicoRegistroCaso.tumor.estadioTumorPrimarioT
Definition

Estadío Tumor Primario (T)

Control1..1
BindingThe codes SHALL be taken from Estadio Tumor Primario -T- (set)
TypeCoding
58. ModeloLogicoRegistroCaso.tumor.estadioNodosRegionalesN
Definition

Estadío Nodos Regionales (N)

Control1..1
BindingThe codes SHALL be taken from Estadio Nodos Regionales -N- (set)
TypeCoding
59. ModeloLogicoRegistroCaso.tumor.estadioPresenciaMetastasisM
Definition

Estadío Presencia Metástasis (M)

Control1..1
BindingThe codes SHALL be taken from Estadio Presencia Metastasis -M- (set)
TypeCoding
60. ModeloLogicoRegistroCaso.notificante
Definition

Informacion sobre Profesional que Notifica

Control1..1
TypeBackboneElement
InvariantsDefined 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.

Control0..1
Typestring
XML RepresentationIn the XML format, this property is represented as an attribute.
Summaryfalse
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.

Control0..*
TypeExtension
Summaryfalse
Alternate Namesextensions, 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.

InvariantsDefined 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())
SlicingThis element introduces a set of slices on ModeloLogicoRegistroCaso.notificante.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
  • value @ url
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).

Control0..*
TypeExtension
Is Modifiertrue
Summarytrue
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 Namesextensions, 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.

InvariantsDefined 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

Control1..1
TypeIdentifier
65. ModeloLogicoRegistroCaso.notificante.especialidadProfesional
Definition

Especialidad del profesional que realiza la notificación

Control1..1
BindingThe codes SHALL be taken from Especialidades de Profesionales (set)
TypeCoding
66. ModeloLogicoRegistroCaso.notificante.apellidoProfesional
Definition

Apellido del profesional que realiza la notificación

Control1..1
Typestring
67. ModeloLogicoRegistroCaso.notificante.nombreProfesional
Definition

Nombre del profesional que realiza la notificación

Control1..1
Typestring