What Pathmarker does

Everything that happens between visits.

One record the member adds to every day and your team reads every week — lab results, wearables, daily logs, medications, care plans, education and messages. Each person gets a version built for what they actually do.

Member app Screens for your team One record AI a person approves Your data kept separate
One system, not five

Everything in one place,
on one record.

What the member does day to day and what your team does — all on one record. Nothing gets typed in twice, and nothing sits out of date in another system.

The record

One record

Lab results, wearables, daily logs, medications and notes, all on one timeline.

Lab results

Upload a PDF. We pull out the numbers, chart them over time and show the normal range.

Wearables

Oura and Strava, synced daily into the same record.

Daily log

Habits, symptoms, medications and activity, logged on one screen.

What the member sees

Care plans

Every change is saved, so you can always see what the plan said and when it changed.

Medications

Doses taken, side effects, refills, and whether they are keeping up.

Education

An article library and video lessons that remember where someone left off.

Meal planning & recipes

Diet plans and a recipe library your clinic curates, with AI writing new recipes grounded in that member’s own diet plan — reviewed before they see them.

Care-team messaging

Private, secure messages between the member, their practitioner and their coach.

Community

Optional member groups with posts, polls and milestones, moderated by your team.

Onboarding & consent

Consent, intake forms and a first-visit checklist, before anyone gets in.

What your team uses

Clinician inbox

One list of what needs you, with the most urgent first.

AI chart summaries

The whole chart summed up in a minute. Written by AI, checked by a clinician before anyone acts on it.

AI scribe

A draft visit note from the recording you already make. You edit it and sign it.

Forms

Build your own questionnaires, send them to a group at once, or upload a PDF form you already use.

Programs

Build a program once and reuse it, so every practitioner runs it the same way.

Enrollment & care teams

Add members one at a time or from a spreadsheet, and set who looks after each of them.

Care pipeline

See where every member is in their program, so nobody quietly stalls.

Booking & calendar sync

Members book real openings, and it syncs both ways with Google and Outlook.

Trust and privacy

Each clinic kept apart

Your clinic’s records are walled off in the database itself, with their own encryption key.

Canadian data residency

Patient information is stored in Canada. The AI runs under a signed agreement with Amazon.

The member app

Members actually use it between visits.

Most patient portals only get opened when a lab result comes in. This one is built for daily use — to tick off a habit, check the plan, or message the team. That is what keeps people on track between appointments.

A home screen that knows what has happened

Their latest lab movement, this week's logging streak, today's recipe, the course they are partway through, their wearable data and the next appointment. All live — not a welcome page.

The member dashboard, reading from live labs, logs, and wearable data.

Labs that mean something over time

A lab PDF becomes charted numbers with the normal range and the history behind them, so a member can see which way things are heading rather than just the latest figure. Sensitive results are stored separately.

One screen for the whole day

Habits, symptoms, medication doses and activity on one screen — done, missed, or as needed. Activity from a wearable lands there on its own.

Logging a day: habits, symptoms, doses, and activity in one pass.

The care plan they were actually given

The plan their practitioner published, in full. If they are on more than one program, every item shows which one it came from.

A published care plan, each item showing which program it came from.

And the rest of the app

  • Medications and supplements — mark a dose taken or skipped, note side effects, see what needs refilling, search a drug list, add a supplement of their own.
  • Education — a searchable article library grouped by clinical area, with citations that link to primary sources, plus video lessons that remember where you stopped.
  • Messaging — encrypted topic threads with the practitioner and coach, with status so nothing quietly goes unanswered.
  • Booking — real openings from the clinic calendar, with Google and Outlook export.
  • Meal planning — a recipe library, diet plans, and cookbooks the clinic curates.
  • Community — opt-in cohorts with posts, comments, polls, and milestones, moderated from the clinician inbox.
  • Onboarding — typed-name consent, intake forms, and a first-visit checklist before anyone reaches the dashboard.
For your clinical team

It opens on what needs you today.

The chart is where the year adds up. The inbox is where the week gets sorted. Both are built for a practice that sees people every few months and gets data in between.

One queue, worked from the keyboard

Lab reviews, sign-offs, messages, community moderation and appointment changes in one list, most urgent first. Number keys set priority, and Enter takes you straight to the work — a visit note waiting on your signature, say — instead of routing you through a chart first. The list updates as colleagues clear their own items.

Priority set with number keys, then Enter straight into a scribe draft awaiting sign-off.

The chart opens already summarised

The Summary tab starts with an AI-written summary of the whole record, checked by a clinician before anyone acts on it. Underneath is the same record the member adds to every day.

The chart Summary tab, opening on an AI-drafted chart summary.

From chart review to a signed note

The practitioner reads the chart, works through the notes, and lands on sign-off — where the AI-drafted scribe summary is edited and approved. The member’s own summary of the visit goes out only after a clinician has signed it.

Chart review, then notes, then sign-off — the AI scribe draft approved before the member’s summary is shared.

Trends, and what actually moved them

Lab markers over months with the normal range, then the view that lines habits up against the markers they moved, and their wearable data beside it. The question every member asks is whether any of this is working. This is where you answer it with their own numbers.

Care plans built from a template, tailored per member

Start from a program, pull in what is already in the chart, then keep, drop or change each item. Publishing saves the new version, retires the old one and records who did it.

Scheduling that matches how the clinic runs

Set your hours and exceptions, see the staff calendar, book and edit appointments, and sync both ways with Google and Outlook so the clinic calendar stays the one that counts.

The staff schedule, synced two ways with Google and Outlook.

Behind the chart

  • Clinical libraries — biomarkers, lab panels, formulary and stacks, symptom instruments with a full item-bank and scoring builder, habit and goal templates, visit types, diet plans.
  • Programs — build a program once, reuse it, and see what changed between versions.
  • Forms platform — author questionnaires across eleven question types, assign them in bulk, or import an existing PDF form.
  • Enrollment and care teams — single or CSV member enrollment, with atomic care-team assignment and an audit trail.
  • Care pipeline — a board view of where each member sits in their program.
One record

Why the rest of it works.

Lab results, wearables, daily logs, medications, symptoms, food, education, forms, visit notes and the care plan are not ten tools stitched together. They are one record — which is what makes a trend readable and a handover safe.

How the AI is controlled

AI that drafts. Clinicians who decide.

The AI writes drafts. A qualified person approves them before anyone sees them. That is built into the software, not just written in a policy.

Visit notes

Your existing Zoom or Fathom transcript in; an editable SOAP draft back, signed off in place.

Lab interpretation

A new report arrives already drafted. The member reads the practitioner’s note, never the model’s output.

The controls behind that

  • The AI never publishes anything. Nothing it writes reaches a member until a qualified person approves it.
  • Three off switches. One in the software, one your clinic controls, and one for each feature.
  • It only works from what you give it. A recipe is written from that member’s own diet plan; a visit note from that visit’s transcript. If it cannot show where an answer came from, it says nothing rather than guessing.
  • We will not tell you it is anonymous. Patient information does go to the AI provider to produce a draft. It is not stored there, and we have a signed agreement covering how they handle it — but it is not anonymous, and we are not going to pretend otherwise.
  • Every use is logged. What was asked, what it drew on, and what it cost.
  • It never tells a member what their results mean. That is the clinician’s job, and the software stops it happening.
For coaches

Coaches see the behaviour. Not the chart.

Coaches keep people on track between visits, so they need to see what is happening — without seeing the medical detail. They get the behaviour, not the chart, and one button to bring in a clinician when something needs one.

  • Behaviour, not results — goals, logging patterns and wearable trends, with no lab values and no medication names or doses.
  • Flag for the clinical team — one click puts a member in front of a practitioner, with the context attached.
  • Their own inbox and messages — a queue of their own, and their own conversations with members.
  • Education progress — what the member has actually worked through.
Canadian-domiciled · PHIPA · PIPEDA · PIA-ready

Something you can explain to your privacy officer.

Most platforms keep clinics apart using their own software. We do it in the database itself, so a coding mistake cannot expose another clinic's records.

  • Every table of health information is locked to one clinic — enforced by the database itself, not by our code, and tested for.
  • A separate encryption key for each clinic — the key is held outside the database, so a stolen copy of the data is unreadable on its own. Destroy one clinic's key and that clinic's data is gone, without touching anyone else's. We are still extending this across the rest of the system.
  • A record of who did what that cannot be edited afterwards.
  • Being a practitioner is not enough — you have to be on that member's care team to open their record.
  • Stored in Canada, aligned to PHIPA and PIPEDA, and built to get through a privacy review.
What’s next

The roadmap.

What we’re building next.

In build

  • Canada-hosted video and transcription, so the whole visit path stays in-country
  • Direct lab-vendor result feeds, alongside the PDF upload that works today
  • More wearables — Apple Health, Whoop, Fitbit, Garmin, CGM
  • Native mobile apps

Further out

  • EMR integration
  • CRM
  • In-app billing and subscriptions
  • SMS reminders

Connects today: lab reports by PDF upload · Oura · Strava · Zoom · Fathom · Google Calendar and Outlook, two-way · Cloudflare Stream · AWS Bedrock · EuropePMC, CrossRef, OpenAlex, NCBI and Health Canada NHP.

A 30-minute conversation, not a contract

The fastest way to know whether this fits is to walk your own workflow through it.

Bring something real — a lab result that came back last week, a plan you would normally rebuild by hand — and we will run it through the software while you watch.