pluto PLUTO-608

EVO-67: add 'No especificado' opt-out to sexo lookup

Done normal unassigned

Elazar GO 2026-07-19. sexoPaciente stays required=true (visual-cue-not-relax principle) — add a legitimate 'No especificado' value so users who won't specify have a non-blocking queryable choice. lookupOptions grupo='sexo' currently has Masculino/Femenino/Otro (see db/schema.md:1701, vOpcionesSexo). Add ONE row: value=noEspecificado, label 'No especificado', activo=true. Form (sexoPaciente RadioGroup, required) auto-picks it up as a valid selection, no form code change expected — coder to verify + confirm nothing hardcodes the 3-option set. Class-S.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 4w ago
wi-cli-venus completed · 4w ago

EVO-67: added lookupOptions row grupo=sexo, nombre='No especificado', orden=4, id f0a1ae43-c06a-4cc3-a9e6-bd9b3898f7e5, activo=true. sexoPaciente stays required=true. Clean pre-existing set (Masculino/Femenino/Otro), no combined-row split case. Code verified fully dynamic (form/validation/reports), no code change needed. DB+view confirmed 4 active rows in vActiveLookupOptions. Cache (unstable_cache tag=lookups, revalidate=3600s) self-heals within 1h; not manually busted (no unauth revalidate path, deemed not worth an Elazar interrupt).

Status

Priority

Assignee

Parent

Type

task

Created

4w ago by wi-cli-venus

Updated

4w ago

Closed

2026-07-19 04:57