Bloodwork Tracker User Guide

Signing In

1. Open health-tracker.project4.net.
2. Enter your approved email address.
3. Select Send code.
4. Enter the 6-digit one-time code from your email.
5. Select Sign in.

Codes expire after 10 minutes. Check spam, request a fresh code if needed, or contact your administrator.

The account header identifies your login; the patient label identifies your clinical record. Access is currently self-only. Account invitations do not share your patient record. Patient switching and clinician sharing are not available.

Main Navigation

• Tracker: clinical summary, latest-result table and expandable history.
• Charts & history: exact collection-date comparisons, results table, visual range rows and charts.
• Admin: separate Assays, Archive, Clinical notes and Maintenance sections.
• API: create API keys and review access logs.

Mobile navigation is always available; wide tables scroll horizontally. The theme button remembers your light/dark preference. Keyboard users can use Skip to content; dialogs support Tab, Shift+Tab and Escape. The footer shows version and latest build.

Finding Markers

Find marker searches by assay, group, unit, status or latest value. Group and Status narrow the active review tables, collection comparison and charts. Clear resets filters. Jump to is available on larger screens. Administration searches and overall summary counts are independent.

Each assay's latest result may be from a different date. Outside lab range counts the latest result per active assay, not just the latest collection. Numerical changes are not improvement/worsening judgments; incompatible values show Not comparable.

Adding Or Editing Results

1. Go to Tracker.
2. Select Add result, or open History and select Edit.
3. Enter the original laboratory value and date in YYYY-MM-DD format.
4. Check the reported unit and reference limits against the report; leave missing bounds blank.
5. Save the result.

If a result already exists for the same marker and date, the app asks before replacing it.

Editing opens original values/units regardless of display mode. History includes original measurements, displayed values, per-result ranges and status. Delete permanently removes a result after confirmation.

Units And Laboratory Status

Select SI units (default), US units, SI + US units, or Original laboratory units above the views. This never rewrites original measurements or definitions. Unsupported conversions retain original units with a warning.

Count units display as ×10⁹/L and ×10¹²/L. Unit fields offer catalogue suggestions and still accept custom text. Type x10^9/L, 10^9/L or paste ×10⁹/L: recognized forms use the existing unit ID and canonical notation. Values and JSON export notation are unchanged by display formatting.

• High / Low: outside that result's stored original laboratory bounds; both badges may be red.
• In range: within the available bound(s). One bound can still determine status.
• No reference range: neither bound was supplied. No result: nothing recorded.

Use text labels, not color alone. From assay definition marks inferred legacy bounds, not verified metadata recovered from the laboratory report.

Charts And Collection Comparison

Choose chronological Earlier and Later collections. Values are from those exact dates; Not collected is not replaced with a nearby result. Numerical changes require compatible analytes and displayed units.

Grey dashed chart bounds show the latest result's laboratory range, explicitly dated. They do not represent every historical report. Open Result history for each date's bounds and original measurement. Out-of-range points use their own stored bounds.

The light-green target zone is separate from laboratory limits. It may sit outside them and never changes High/Low/In range status. Incompatible units may prevent a chart or target band being shown.

Admin Tasks

• Assays: search active definitions, then New assay, Edit or Copy. Definition units remain original stored units, independent of display mode. Cancel exits editing.
• Set Default result date before entering several results from one collection. Changing assay defaults does not replace historical result metadata.
• Choose an existing group from suggestions or type a new group. Matching is case-insensitive to avoid duplicate groups.
• Target Zone: enabling copies lab limits into blank target fields and initially uses the same unit. Both target limits are needed for a band; they may lie outside the laboratory range. The app does not validate their clinical suitability.
• Clinical notes: edit patient notes and select Save notes. Notes are included in both export types.
• Maintenance: account invitations (administrator only), merge and clear-data controls. Invitations do not share patient data.

Merge requires matching analytes and units. Preview first: duplicate source dates already in the destination are skipped, then the source assay is removed. Clear all data permanently removes active and archived assays/results after confirmation, but not clinical notes or the login.

Archiving And Restoring

Select Archive beside an assay and optionally enter a note; cancel the prompt to leave it active. Results remain stored but leave active summaries, review and charts. Under Admin > Archive, search for the assay and select Unarchive to restore it.

Archiving is not access revocation: AI export includes archived history, and API clients can explicitly request it.

Import And Export

• Export: downloads active assays, their original results/metadata and clinical notes. It is not a complete archived-data backup.
• AI export: previews, copies or downloads all assay history, including archived assays and notes. Nothing is automatically sent to an AI provider.
• Import: accepts standard app JSON with tests, results and clinicalNotes. Browser import does not accept spreadsheets or AI-export JSON. Repeated imports can add duplicate definitions; supplied notes can replace existing notes.

Keep health exports secure and inspect them before sharing. Display settings do not remove original measurements from exports.

API Keys

Administrators create keys from API. New keys are shown once: copy and store them securely, and revoke unused keys. Keys can read, create, update and delete the issuing account's patient data. They are not read-only.

See the API documentation for endpoint details.