How custom markers are created during PDF import
When you import a PDF, the AI identifies any results that don’t match a known biomarker. For each unrecognized result it suggests:- A category to place it in (e.g. biochemistry, hormones)
- A name for the marker in plain English
- The unit it is measured in
- A reference range (minimum and maximum) when the source report provides one
Creating custom markers manually
You can create a new biomarker without importing a PDF:1
Open the marker creation form
Open Custom markers from the Manage section of the sidebar. On mobile, open the menu and choose Custom markers.
2
Choose or create a category
Pick an existing category from the list, or type a new category name to create one. You can set a custom emoji icon for new categories using the picker — or leave it blank to get an auto-inferred icon.
3
Enter the marker details
Fill in the marker name, unit, and optionally a reference range and optimal range. All fields except the name can be left blank and filled in later.
4
Click Create
The app immediately opens the Add Value form so you can log your first data point. The marker appears in Labs, marker search, dashboard marker widgets, and AI chat context while Blood marker results are enabled in Manage → Context.
Editing custom markers
Custom marker definitions are set when first created and are not overwritten by future imports of the same marker. You can edit them at any time:- Reference and optimal ranges — click the range values in the marker’s detail modal to edit them inline. If no ranges are set, a clickable “Reference: – – –” placeholder appears.
- Open-ended ranges — clear one side of a range using the × button to create a bound like “>59” with no upper limit.
- Name and unit — editable in the marker’s detail modal.
Grouping custom markers
Custom markers follow the same category system as built-in markers:- Category — assigned when you create the marker manually or during import. Markers in the same category appear together in Labs and chart views.
- Moving a marker — open its detail modal, choose Change category, and select a compatible destination. This changes where it appears for the current profile without changing its values, history, notes, import mapping, or identity. Choose Restore original category to undo the placement.
- Renaming categories — click the category name in the category view header to rename it. The display label changes; the underlying key and all your data are unaffected.
- Category icons — click the icon next to any category name to open the emoji picker. The picker includes categorized tabs (Science, Health, Nature, Food, Objects), a search field, and a Reset button to revert to the default.
Where custom markers appear
Once created, custom markers are treated identically to built-in markers throughout the app:- Labs charts with reference range bands and trend detection
- Data tables alongside every other biomarker
- AI chat context — the assistant knows about your custom markers when Blood marker results are enabled in Manage → Context
- JSON backup — included in exports and restored on import
- Future PDF imports — the AI uses your existing custom markers to avoid creating duplicates
Specialty lab pipeline
For non-blood tests (OAT, DUTCH, HTMA, fatty acids, and similar panels), the importer uses test- and product-specific categories and adds a group field that determines Labs navigation placement. Recognized Mosaic OAT, Mosaic MOAT, and Metabolomix+ reports are normalized after AI extraction into deterministic product keys. Other OAT reports use a laboratory-scoped prefix when the product name is available. Existing custom-marker histories are preserved when a new product adapter ships; they are not silently merged into the new product namespace. On a later import, review the proposed mapping before deciding whether old and new results represent the same assay and product.Custom markers vs. specialty lab adapters
Use custom markers for anything not yet covered by a built-in adapter — deuterium levels, functional medicine panels, home monitoring devices, or any specialist test. If getbased later ships an adapter for that test type, your existing data remains intact and the import review lets you verify future mappings.