{"v":{"content":"# Action Plan \u2014 Forms V2 after the on-site demo\n\n*As of 2026-10-13. 44 open Action Items: most from the SOC\/AO demo on 29 Sep (Jane's texts and\nFrank's notes), the rest from Jane's texts and our own notes on 7\u20138 Oct (marked **New**), plus the\nVESTA feed and form-publishing items. 46 are done (listed at the end). Each Action Item holds\nits own detail; this page is the order of work.*\n\nEvery item below says who it is waiting on:\n\n- **Waiting on the customer:** we need an answer, a list or a template from them.\n- **Waiting on Jane:** we need her to confirm or explain something.\n- **Nothing to wait for:** the next step is ours.\n\n---\n\n## Built \u2014 open for a confirmation\n\nThese are built (the two marked \"on dev\" are not on production yet). Each stays open until\nsomeone answers the question named.\n\n- #77 **Questions use the form's own wording.** Every SOC\/AO question and answer choice now\n  reads as the paper does. Our plain \"Ask: \u2026\" wording under each is hidden for now (8 Oct) and\n  can be brought back. Where the forms word it differently, the fullest wording wins, as the\n  customer asked: \"Client Name\", \"Male \/ Female\", \"1 - Bathing \/ Ba\u00f1ar\", the disaster plan's\n  paragraph for each emergency class. On 13 Oct the customer settled the last two: **\"Medicaid\n  #\"** (set as a standard, like \"Client Name\") and **\"Gender\"**. Published on dev as release\n  SOC_AO-20261013. **Nothing to wait for** from the customer. Before production we decide\n  whether \"Ask:\" stays hidden, and check the fragment labels (\"Phone\", \"Which directives\") and\n  the other labels the rule chose (\"Telephone No.\", \"Individual's Address\").\n- #140 \/ #90 **Other care is asked once** (published). One list fills the Coordination of Care\n  and both pages of the service plan. No other services prints \"None\" and \"N\/A\", which settles #90.\n  **Waiting on the customer:** check what each paper ticks for each kind of care.\n- #118 **Agency and branch details fill the forms.** The vendor and office address come from the\n  client's branch, and the visit check now lists any detail that is not on file. The customer\n  entered every branch office address on production on 9 Oct (street, city, state and ZIP now\n  have their own boxes). The SOC\/AO release carrying the office-details check is published\n  on dev (SOC_AO-20261013, 13 Oct). **Nothing to wait for:** publish it on production, then\n  choose it on Paperwork in Use.\n  Which number prints where (vendor or contract) is #117.\n- #103 **3040 frequency is a drop-down** (QD \/ QW \/ PRN), each task starting at Frank's default,\n  plus the blank \"other\" row. **Waiting on the customer:** with the defaults in place, must QW\n  still be refused on a daily task?\n- #101 **\"Did you explain\u2026\" questions start as Yes.** Questions that record the client's own\n  decision stay blank. **Waiting on Jane:** confirm both lists.\n- #160 **New. Attendants and hours step** (built on dev, not yet on production). The hours\n  table with the authorized hours comes right after Attendant A's phone; each attendant's days\n  sit behind a \"Show days and hours\" button, which opens by itself when a day has a problem;\n  an unused second or third attendant gets no days box. **Waiting on Jane:** with one\n  attendant, should B's questions give way to an \"Add another attendant\" button? Should the\n  identical \"All attendants\" row be left out? Should the days open by themselves when the week\n  is under the authorized hours?\n- #159 **New. \"Not known\" is switched off** on dev: blank now means not known, and an answer\n  already marked \"Not known\" still shows with \"Answer it instead\". It can be switched back on\n  exactly where it was. **Waiting on Jane:** what a required question left blank should do,\n  and whether any question must still record \"not known\".\n- #99 **Find the pharmacy.** The Emergency\/Disaster form looks the pharmacy (and the equipment\n  supplier) up in the registry, with this agency's past picks first. **Nothing to wait for:**\n  keeping the pharmacy on the client's record and prefilling it next time needs an office\n  step that accepts a visit, which does not exist yet.\n\n## Built 8 Oct, on dev \u2014 for Charles to review before production\n\n- #161 **New. A schedule can't change the number of days.** Hours can move between days; if a\n  day is added or dropped, a red note under the authorized hours says so and the forms can't be\n  generated until the count matches. Moving a day means changing both days. **Waiting on\n  Jane:** does \"for a given period\" mean per week? That is what is built.\n- #125 **Find the questions for a given form.** On a visit and on Visit Review, \"Show the\n  questions for\" picks one form and shows only its questions.\n- #126 **Compare any two published releases** on Paperwork in Use (\"What changed\", \"Compare two\n  releases\"). Each release lists the Action Items its notes name; name them when publishing.\n\n## Priority 1 \u2014 Forms: our next build\n\n- #156 **New. Each visit type has its own forms, questions, choices and fixed answers.** Check\n  that the visit and its questions handle that for every visit type, not only SOC\/AO.\n  **Nothing to wait for.**\n- #115 **Paired tick box:** ticking \"I am not providing a record\" ticks the box below it.\n  **Waiting on Jane:** the paper doesn't make it clear. The only box like it (\"I am \/ am not\n  providing a copy for my record\", on both consents and the Private Pay Agreement) has no box\n  below it. Which form and which box?\n- #122 **Questions that ask several things at once.** List them all and propose a split for\n  each. **Nothing to wait for** to draw up the list; **Jane** then confirms it.\n\n## Priority 2 \u2014 The VESTA feed\n\n- #147 **Finish the switch to the VESTA API** for the daily report pipeline, agency by agency.\n  **Nothing to wait for.**\n- #148 **On-demand VESTA pulls for one client** while forms are being filled: a queue the secure\n  server checks, then a one-client report run pushed to production. Needed because tasks and\n  schedules are not in the API. **Design first. Nothing to wait for.**\n- #168 **New. Compare what the forms say with what VESTA says**, as a report across our\n  clients. **Nothing to wait for:** to be written up first (which answers, which VESTA fields).\n\n## Priority 3 \u2014 Emergency priority list\n\n- #167 **New. A list of the clients who most need help in an emergency, chosen by area.**\n  VESTA has no \"bed-ridden\" field, but the client class, the priority flag, the help with\n  transfer and walking, and the county come close. The proposal is in four steps: first a\n  ranked list by county, branch or ZIP with the reasons shown beside each client and a\n  printable call sheet (no map needed); then a map to select by radius or drawn area; then the\n  visit's Emergency\/Disaster answers taking over from VESTA's; then tracking who has been\n  reached during an event. **Waiting on the customer:** how they handle an emergency today,\n  what the client class means to them, and who works the list (questions below). **Before the\n  VESTA API switch (#147):** the API does not send the client class, so decide how to keep it.\n\n## Priority 4 \u2014 Design calls\n\n- #94 **\"Request hours \/ schedule change\"** sent to the coordinator. **The largest new\n  feature.** **Waiting on the customer:** what a request holds, how the coordinator gets it,\n  and what \"done\" means.\n- #120 **Protecting a primary answer** whose follow-ups are filled in: lock, confirm and clear,\n  or warn? We suggest confirm and clear. **Waiting on the customer** to choose.\n- #119 **Correcting a signed form** without changing the signed original. **Nothing to wait\n  for:** ours to design (who may correct, whether the client signs again).\n- #128 **Who signs off before a release goes live on production**, and whether once for all\n  three agencies or once per agency. **Nothing to wait for:** our decision.\n- #164 **New. Translated forms are the same form.** A Spanish or Vietnamese 3040 keeps the\n  3040's questions and answers, with the wording stored per language and a switch to show it\n  beside the English. Forms that already print English and Spanish together would be split the\n  same way. **Nothing to wait for:** ours to design (a Vietnamese 3040 may arrive this week).\n- #158 **New. Language question:** English and Spanish up front, \"Other\" opening the full list\n  from a government form, and every language the client speaks ticked and kept separately.\n  **Waiting on Jane:** which government form has the full list?\n- #157 **New. Sex question:** Jane saw a form offering Male \/ Female \/ Other; none of the forms\n  we hold does. **Waiting on Jane:** which form? Then, what a two-box form prints when the\n  answer is \"Other\".\n- #163 **New. Internet-access programs for clients** (Lifeline, for which Medicaid qualifies a\n  household). It bears on clients receiving their signed forms online (#121, #123).\n  **Nothing to wait for:** check the facts first, then offer the customer a question at the\n  visit or a handout.\n\n---\n\n## Waiting on the customer \u2014 send as one request\n\nSend these as **one batch**, not one at a time.\n\n**Lists and templates they need to supply**\n- #81 Allergy list (one choice or several? how to word \"no known allergies\"?)\n- #135 Equipment list \u00b7 #134 Home hazard template \u00b7 #136 Everyday activities template\n- #95 \"Change needed\" template, and what the 3040 prints for \"should services end\"\n- #112 Who-signs list (POA, guardian\u2026), and the question a POA opens\n- #141 Which disaster form boxes are prefilled, and to what\n- #162 The disaster form's \"special needs?\" is only Yes\/No: should the visit ask what the needs\n  are? (Jane is raising it with them)\n\n**Confirm what we built**\n- #140 \/ #90 What each paper ticks for each kind of other care\n- #103 With the defaults in place, must QW still be refused on a daily task?\n\n**Rules to confirm**\n- #107 Which service plan answers replace the 3040 orientation questions\n- #109 What the 3040's Q4 and Q5 fill with when there are attendants\n- #117 Vendor vs contract number, per form and per branch (the branch addresses are in; this\n  rule and the contract numbers are what is left)\n- #116 Which PAS\/PHC consent version they use (send the current blank)\n- #100 STEAR: who registers the client, at the visit or the branch afterwards?\n- #120 Lock, confirm or warn when a primary answer changes\n- #94 What a change request holds, who receives it, what \"done\" means\n\n**Emergency priority list (#167)**\n- What do they do in an emergency today? Is there a spreadsheet or list we should match?\n- Does the client class in VESTA mean what we think, and is it kept current?\n- Should the visit ask more about special needs (oxygen or other powered equipment, lives\n  alone\u2026), even though the paper form does not print it?\n- Who works the list during an emergency: office staff only, or field supervisors for their own\n  clients? Should attendants be on the same map (whose shifts will drop)?\n\n**Priorities and research on their side**\n- #85 Their ranking of the visit steps\n- #124 Send them our draft client survey \u2192 its results then decide #121 (connectivity\n  checklist) and #123 (clients without a smartphone, blocked on it)\n\n## Ask Jane\n\n- #101 Confirm which \"did you explain\u2026\" questions start as Yes, and which stay blank\n- #98 \"EE hours change\": what does it mean?\n- #100 Confirm that \"on stear\" means registration\n- #122 Confirm the list of split questions, once we send it\n- #157 Which form offers Male \/ Female \/ Other?\n- #158 Which government form has the full list of languages?\n- #159 What should a required question left blank do, now that \"Not known\" is gone?\n- #160 With one attendant: an \"Add another attendant\" button instead of B's questions? Drop\n  the identical \"All attendants\" row? Open the days by themselves when the week is under?\n- #161 Does \"for a given period\" mean per week? (Built that way.)\n- #115 Which box goes with \"I am not providing a copy for my record\"? The paper has none below it.\n\n\n## Accomplished\n\n**Visit forms**\n- #169 A section's forms are behind an info button instead of printed on its button; the\n  \"answered \/ shown\" counts are gone from the section list (8 Oct, on production 9 Oct)\n- #165 A correction after the forms are generated re-signs only the forms it changed; the\n  answers lock behind **Change an answer** (8 Oct)\n- #166 Sections with questions nobody has looked at are marked \"N new\", and the forms wait for\n  them (8 Oct)\n- #145 A pull-out with the client's details beside the forms while filling them in (6 Oct)\n- #83 The visit asks for the client's (and a family member's) email address (6 Oct)\n- #111 Nobody is asked about signing for a client who signs (6 Oct)\n- #93 A schedule can't go over the authorized hours; under is allowed and flagged on Visit\n  Review (6 Oct)\n- #82 Find the doctor from the national provider registry; the customer keeps no list of their\n  own (6 Oct, closed 7 Oct)\n- #99 Find the pharmacy the same way (6 Oct; open for confirmation, above)\n- #137 Find the agency the same way, on the Coordination of Care and the Transfer form; \"home\n  health\" includes in-home support agencies (6 Oct, confirmed and closed 8 Oct)\n- #88 Supervision is every 12 months \/ PRN on every form; eight questions removed (6 Oct)\n- #105 3040 item 7 is worked out from the service plan's \"change needed\" answer (6 Oct)\n- #106 The 3040's report-to name and phone come from the agency (6 Oct)\n- #113 Witnesses sign on screen, and their dates come from the signing (6 Oct)\n- #114 Witnesses are asked for only when the client signs with an X (6 Oct)\n- #78 The 3040's item numbers show beside its questions (\"Form 3040, item 8\") (5 Oct)\n- #79 The form's name shows in the visit's document list and on each question (5 Oct)\n- #80 The Forms V2 plan now says the paper's wording replaces our spoken rewording (5 Oct)\n- #89 The service plan lists only the tasks VESTA authorizes for the client (5 Oct)\n- #108 The orientation visit's 3040 task grid uses the same VESTA task list (5 Oct)\n- #102 Task guide: only the client's tasks on screen; the full guide on paper with theirs marked\n  (5 Oct)\n- #104 The task guide no longer prints its logo and footer twice (a hidden layer in the blank)\n  (5 Oct)\n- #84 *Plan for emergencies* now follows emergency contacts (5 Oct)\n- #92 Authorized weekly hours are read-only in an SOC visit, taken from VESTA (5 Oct)\n- #91 Schedule hours print two decimals and move in quarter-hour steps (5 Oct)\n- #86 The service end date is no longer asked; it prints blank (5 Oct)\n- #87 \"Who will supervise the attendant\" is no longer asked; always Supervisor (5 Oct)\n- #96 \"Does the client need the services?\" is no longer asked; always prints Yes (5 Oct)\n- #97 \"Does the schedule vary week to week?\" is no longer asked; always No (5 Oct)\n- #139 The 3040 schedule note (FWD) is filled from the service plan start date (5 Oct)\n- #138 \"Which health problems must the attendant report?\" on the 3040 is now a Yes\/No reminder\n  (5 Oct)\n\n**Tooling, checks and decisions**\n- #110 Jane told where the 3040's item 8 (\"Is the attendant competent\u2026\") is asked: the\n  *Attendants and supervision* step (8 Oct)\n- #151 VESTA does show attendants working more than one time span a day, and the visit\n  already carries every span (up to five seen in one day) (7 Oct)\n- #152 The visit's sidebar names the forms (7 Oct)\n- #153 The Form Explorer shows which answers are shared between forms and which come from a\n  lookup (7 Oct)\n- #154 The Form Explorer can show only the agency\/branch answers, or only the prefilled ones\n  (7 Oct)\n- #155 The Form Explorer says \"Shared Answers\" (7 Oct)\n- #149 The visit type (which forms a visit needs) is published in the same step as its\n  questions (6 Oct)\n- #143 Every time the visit screens send back client information, who saw it is recorded\n  (6 Oct)\n- #150 A blank form that carries hidden layers is refused (would have caught #104) (6 Oct)\n- #127 One command imports, checks and publishes a visit type from the repo files (5 Oct)\n- #130 A completeness check runs before every publish, the same one as the Explorer's Gaps tab\n  (5 Oct)\n- #129 The form files are the source of truth; the on-screen form, interview and map editors are\n  retired, and a correction is a file change (5 Oct)\n\n**Agencies and sign-in**\n- #142 Agency administrator name confirmed on production (5 Oct)\n- #146 An agency can now carry more than one VESTA agency ID (5 Oct)\n- #144 The systems editor screen was reworked (5 Oct)\n- #132 Automatic sign-out after 15 minutes of inactivity (1 Oct)\n","updated_at":"2026-10-13T11:28:06-05:00"}}