{"v":"

Items 1 and 2 from the notes above are built.<\/strong> Item 3 is still open.<\/p>\n

    \n
  1. FREQ is a drop-down: QD \u2014 Every day, QW \u2014 Every week, PRN \u2014 As needed.<\/strong> Each task starts at its default from Frank's table: Laundry and Shopping start as QW, Escort as PRN, everything else as QD. The supervisor can change it. A row is still asked only when the task is in the client's VESTA list (#108). The paper prints the code (QD \/ QW \/ PRN) in the FREQ cell.<\/li>\n
  2. The blank "other" row.<\/strong> "Does the attendant do any other task that is not listed?" is always asked, because it covers what VESTA doesn't list. Once a task is named, its frequency drop-down and A\/B\/C ratings appear. It prints on the paper's unlabelled row under "Assist w. Self-Admin. Med" (name on the line, code in FREQ, S\/U in the cells), checked on a rendered proof.<\/li>\n
  3. Still to ask the customer:<\/strong> now that there are sensible defaults, do we still need to refuse<\/em> QW on a daily task, or is the default enough? Nothing refuses it today.<\/li>\n<\/ol>\n

    Files: docs\/forms\/forms-3040.json<\/code>, docs\/form-placements\/forms-3040.json<\/code>, docs\/form-v2-interviews\/SOC_AO.json<\/code>. A mark can now print a code of up to three capitals (it was one letter), with a fit check so a code can't overflow its cell. Imported to the dev drafts, and the publish rehearsal passes all nine checks. It goes out in the pending SOC_AO release with #88\/#101\/#105\/#106: publish on \/admin\/form-v2-publish, then choose the release on \/admin\/form-v2-releases.<\/p>\n"}