The most useful dose log is factual. It records what the user says happened, when it happened, and which plan or vial the entry belongs to. It does not automatically turn notes, symptoms, or changes into medical conclusions.
Distinguish planned from completed
A calendar item can exist because a protocol scheduled it. A dose-history entry should exist only after the user records a completed, skipped, corrected, or voided action. Keeping those records separate prevents a schedule from being mistaken for evidence of completion.
Record date, time, and status
- The local date and time entered for the action
- A normalized timestamp for ordering and cross-device sync
- A clear status such as taken, skipped, corrected, or voided
- The time the record itself was created or changed
Keep the user-entered amount and unit together
A number without its unit is incomplete. Preserve whether the user entered mg, mcg, mL, or a U-100 scale value. If a calculator result is linked, keep the underlying vial, water, and target inputs available for review rather than storing only the final mark.
Add administration context without making recommendations
A record may include a user-selected administration route and site. Reviewing prior sites can support an auditable rotation history, but the log should not choose a route, site, or technique for the user.
Associate the record with a vial when possible
Linking a completed entry to a compatible vial can preserve which reconstitution inputs were in effect and update a calculated remaining quantity. Inventory values are estimates based on user entries and should remain distinguishable from a physical measurement.
Keep related observations separate
Meals, hydration, weight, appetite, symptoms, and free-form notes can provide useful context. Store them as separate timestamped observations. Their proximity to a logged dose does not prove that the dose caused a change.
- Use consistent scales for repeated check-ins.
- Record missing days as missing instead of inventing a value.
- Describe observations in neutral language before interpreting them.
- Review longer patterns with visible data coverage and appropriate professional guidance.
Preserve corrections, skips, and voids
If an entry was recorded incorrectly, a correction or void should preserve enough history to explain the change. A skipped action should remain distinct from a missing record. Undo behavior should be bounded so an accidental tap can be corrected without silently erasing older history.
- Peptide or protocol label
- Date, time, status, amount, and unit
- Optional route, administration site, and vial association
- Neutral notes and separately timestamped observations
- Correction, void, and sync history when a record changes