Help guide

Provider & Clinics

12 topics from the guide built into BioHack Track, published in full.

What the Provider tier is

Provider is a plan for clinicians and clinics, on top of everything in Pro. It turns the app into a place to hold the records your patients send you: import the file a patient shares from their own app and it lands on a roster with no cap on how many people are on it.

$19.99/month or $199.99/year. BioHack Track does not prescribe. A change you send through it is not a prescription — your patient reviews each one and chooses whether to accept it.

Your practice details

Settings → Practice holds who you are: practice name, clinician name and credentials, phone, email, address, website and NPI or licence number, plus an optional standing note.

Everything you fill in travels with every protocol change, note and patient file you send, and prints on the exported chart file. Anything you leave blank is left out entirely rather than shown empty. A practice with nothing filled in signs as “Your provider” — so fill it in before you send anything.

The roster, and one file per patient

Each patient is one record, not one record per visit. Import a newer file from the same patient and it updates their existing entry, archives the previous snapshot as a dated version, and shows you what changed since the last one — rather than adding a second row for the same person.

Patients are matched on an identifier inside the file, never on their display name, so two patients you have not labelled can never collapse into one. You can give any patient your own reference — a chart number, an MRN, whatever your practice uses — and it is kept across re-imports.

Reaching a patient

A shared record can carry the patient's phone and email, so a clinic ringing about a result is not hunting for them in another system. It is the patient's choice: a toggle on their share screen, off by default, typed by them and never read from their contacts.

On your side it shows on their record as a tappable row. You can correct it — a number changes without anyone re-sharing, and your correction is kept separately from what they sent, so a newer record never overwrites it. Leave your copy blank to use theirs.

A later record that carries no contact details does not wipe what you already have.

Reading a record

Open a patient and everything they tracked is charted, not listed.

  • At a Glance — every headline metric as start → current with the dates and the change
  • Protocols with real adherence, not just a dose count
  • Labs — every marker with its reference range, out-of-range values flagged; tap one for its full run with the band shaded
  • Body composition — every scan metric as its own series, plus segmental lean and fat for each limb and the trunk
  • Symptoms vs Doses — plot any symptom against the days they actually dosed, side effects marked

Drag across any chart to read a single day.

Proposing a protocol change

From a patient's record you can propose starting, changing, pausing or stopping a protocol. Compounds come from a menu of what that patient is actually running, or from the full library by search — you should not have to type a compound name.

A start can carry the dose, unit, frequency, route, start date, duration and a full titration ramp. When the patient accepts, all of it is set up in their app with nothing typed on their side.

Nothing is applied automatically. A start or change opens their own protocol editor so they see the exact record before it saves; a pause or stop asks them to confirm, and their logged history is kept either way.

Notes, labs, visits, scans and vitals

Private clinical notes stay on your device and are never written into anything you send. Notes marked for the patient ride along with the next change you send and appear in their app badged with your practice.

Alongside a protocol change you can send:

  • Lab results you have and they do not — they land on the draw date, so they sit in the right place on their trend rather than on the day you sent them, and are marked as coming from you.
  • Visit notes, which appear on their timeline as a Provider Check-In with your practice named. It is not stored as one of their own check-ins, so it never inflates their check-in count.
  • Vitals from the visit — weight, height, blood pressure and waist — filed on the visit date. Send only what you actually measured; each field is optional.
  • A body scan you ran here — an InBody, a clinic scale or a DEXA. It lands as a scan in their own history, so every metric charts from their first reading to the latest instead of them re-typing a printout.
  • A follow-up date, and the panel you want drawn before the next visit.

A number they recorded themselves is never overwritten silently. If your weight for a day differs from theirs, they are shown both and choose. Anything they left blank is simply filled in.

Sending an update over the phone

You do not have to email a file. On a saved protocol change, Read a Code puts it on a relay and shows you a twelve-character code to read to the patient. They open BioHack Track, tap Enter a Code on the provider screen, and the update arrives.

Case and dashes do not matter, and the letters I, L and O are not used — so a misheard letter still opens the plan.

What the relay can and cannot see. Your device encrypts the file before it leaves, using a key derived from the code. The code is spoken and never sent, so the relay only ever holds ciphertext it cannot read. It hands the file over once and deletes it, and anything uncollected disappears after 72 hours.

It carries a protocol change only — never a patient record. Sending by file (email, Messages, AirDrop) still works and is still the default.

If a code does not open, it has usually already been used or has expired. Send it again.

Asking a patient for an updated record

You do not have to wait for a patient to think of it. Request an Updated Record sends them a file that asks for one; their app pre-ticks what you asked for and they choose whether to send it.

It is a request, not access. Nothing is pulled from a patient's device — there is no mechanism for that and there is not going to be.

Where patient records live

Patient records are held in a database separate from your own data, and it is never synced to iCloud. We never receive them. They leave your device only in a file you export yourself — a practice backup, or a patient's chart handed to a colleague. Both go wherever you send them; neither passes through us.

They are not backed up by iCloud either: use Back Up the Practice before you change devices. Where you keep that file, and how it is protected, is yours to decide under whatever rules govern your practice — we do not hold, inspect or transmit patient records, so meeting your own obligations is not something we can do for you, and nothing here is limited on the assumption that we could.

On iPad

The practice roster is built for a tablet: patients on the left, the selected chart filling the rest of the screen, and a patient's full record opens full screen rather than in a column. Everything works on iPhone too — it pushes between the list and the record instead of showing both.

iPhone, iPad and Android

The file a patient shares is plain, portable JSON with every date written in a standard format, so it reads the same on either platform. An Android patient can share with an iPad clinic and an iPhone patient with an Android clinic.

Provider tools are on iOS and iPadOS first; the Android build is catching up. Receiving a file your clinician sent you is free on every plan, on both platforms.