rubyforgood / rubyforgood/alongwithyou

Decide the Medicine Diary shape: current list vs. dated log (ADR 0014)

Open
#132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:decision
Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
9h 34m
Merged PRs (30d)
16

Description

ADR 0014 was merged in #120 with status Open and has had no tracking issue since. It needs a named owner.

The question is what Section 2 (Medicine Diary) actually contains: a current list of medications the person is on, a dated log of what was taken when, or both. It follows the precedent set by 0011 for Section 8 — a product call, not a technical one.

It blocks the diary UI only. The storage and search decisions underneath it are settled: 0012 picked RxNorm/RxNav with openFDA secondary, and 0013 put the catalog on the device. So this can be answered independently of any of that work.

What is needed
  • A named owner to decide: current list, dated log, or both
  • Confirmation of how it interacts with #53 (current vs. historical medication distinction in the UI), which assumes some version of this answer
  • 0014 updated from Open to Accepted with the outcome
Related
  • #51 — Current/stopped medication list
  • #52 — Medication detail fields
  • #53 — Current vs. historical medication distinction in UI
  • #20 — the equivalent open shape question for Section 8, which 0014 follows

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read docs/decisions/0014-medicine-diary-shape.md and compare its Section 2 question with decision 0011. Check how the outcome interacts with #53, then record the product decision in ADR 0014 and change its status from Open to Accepted with a named owner.

Written by the indexing model from the issue text.

Assessment

Domain
design, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.