{"v":"

Where this stands today<\/h2>\n

The visit sidebar (renderSteps()<\/code> in pages\/visit-v2.php<\/code>) shows each section with an answered \/ shown<\/strong> count. Nothing records which sections the filler has actually opened. The visit stores only current_step<\/code>. So when an answer reveals new questions in a later section, the only sign is a count changing from 4\/4 to 4\/6, which is easy to miss. The Check step lists missing required<\/em> answers, but an optional question that newly appears is never pointed out at all.<\/p>\n

Proposed plan<\/h2>\n

Track what has been shown, per question, on the server.<\/strong> Do not track it per section, and do not track it in the browser.<\/p>\n

    \n
  • Record a question as seen<\/strong> when its section is open and the question is visible at that moment. The page already saves on every step change (pendingStep<\/code>), so the save carries the visible question keys of the section being left and the server records them. Question keys are not PHI. I'd use a small table, form_v2_visit_seen (fk_form_v2_visit, question_key, first_seen_at, seen_by)<\/code>, through a migration. It lives on the server so a visit resumed on another iPad, or after a reload, keeps it.<\/li>\n
  • Waiting<\/strong> = visible now, not yet seen, and not answered. The server computes it beside form_v2_visit_progress()<\/code> (pure, in form_v2_visit_rules.inc.php<\/code>) and returns it per section with the progress.<\/li>\n
  • The re-flag from the description comes for free.<\/strong> A question revealed by a later answer was never seen, so its section lights up. If the answer is changed back and the question hides again, the flag goes away. If it was seen once, hidden, then shown again, it stays seen. See question 2.<\/li>\n<\/ul>\n

    On screen:<\/strong><\/p>\n

      \n
    • The sidebar shows a dot and "N new<\/em>" on a section with waiting questions, beside the existing count. Inside the section, the waiting questions carry a small New<\/strong> label until the section is left.<\/li>\n
    • After a save that reveals questions in another<\/em> section, show a short notice: "This answer added questions in Emergencies<\/em>", with a link.<\/li>\n
    • The Check step lists "Sections with questions you haven't seen" above the issues, each with a link.<\/li>\n<\/ul>\n

      Tests:<\/strong> pure rule cases (seen\/visible\/answered combinations; hidden then revealed), plus a state test showing the seen set survives a reload and that a step change records only that section's visible questions.<\/p>\n

      Questions<\/h2>\n
        \n
      1. Should a question that is already filled in from VESTA count as waiting if nobody has opened its section?<\/strong> Its value came from the record, not from the client. My recommendation: yes<\/strong>. "Seen" means the filler looked at it, and a prefilled authorization answer is exactly the kind that may be out of date. The flag would then mean "not looked at", not "not answered". The catch: on a fresh visit every section starts flagged, which is arguably right.<\/li>\n
      2. Seen once, hidden, then revealed again with its old answer:<\/strong> flag it again? The plan (\u00a76) says a reactivated branch "requires review before those saved answers become current again". That suggests yes<\/strong>, so I'd clear "seen" when a question hides. Please confirm.<\/li>\n
      3. Does a waiting question block Generate forms?<\/strong> I'd block<\/strong>, with the list of sections as the reason. Otherwise forms can be printed with a question nobody asked. The alternative is a warning the filler can override. This is the same decision as question 3 on #165.<\/li>\n<\/ol>\n

        #165 depends on this for its "revisit these sections" half, so I'd build this one first.<\/p>\n"}