Get started
AnalyticsLive · in the productReport

Outcomes

PROMs and outcome registries per specialty.

Get OutcomesOpen the appAvailable nowHow pricing works →

What it is

Patient-reported outcome measures with the instrument as the contract: scores outside its bounds are refused, one baseline per patient per instrument, follow-ups build the patient’s own curve. The registry aggregates the cohort that has both ends — how many improved, and by how much — turning a practice’s results into evidence. For a chain, Branch by branch puts the same measure side by side at each branch: each patient counted where most of their visits between the two scores were seen, with those visits as their sessions, the median sessions, the average change and how many improved; a branch with fewer than five such patients shows its count only.

Who uses it
Built for: Every specialty
Reads
Submissions, the chart, visits per branch
Writes
Registry entries
Never
Registry exports are de-identified — the patient column is a per-export serial, and no name, MRN or id leaves.
Access
Only people whose role includes it — the clinic owner decides who
Your data
Full PHI. Hosted in Boston, United States. On uninstall: Registry data stays with the tenant.

How it works

  1. Publish the instruments you useAdd one of the standard sets — Oxford Hip, Oxford Knee, Oswestry, PHQ-9, DLQI — or your own, with its bounds.
  2. Record the baselineOne baseline per patient per instrument. It is the score you cannot go back and capture later, so the desk asks for it first.
  3. Record the follow-upsThey build the patient’s own curve. A score outside the instrument’s bounds is refused rather than stored and averaged.
  4. Read the registryThe cohort that has both ends: how many improved and by how much. Exports are de-identified — the patient column is a per-export serial.
  5. Compare the branchesBranch by branch, under the registry, shows each measure at each branch: patients with both scores, median sessions, the average change and how many improved. A branch with too few patients shows its count only.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

Registry exports are de-identified — the patient column is a per-export serial, and no name, MRN or id leaves.
An identified export is a consent event, and v1 ships no identified export at all.
The branch comparison reports where outcomes differ; it does not change anyone’s treatment plan.

AI in Outcomes

AskQuestions about what is on screen — “What needs attention in Outcomes today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Outcomes — Measure treatment results with patient scoresCaptured from the running demo clinic
Outcomes — Outcomes — Measure treatment results with patient scores
1 of 1
Open the interactive design preview →

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 2
See the whole clinic →

Questions clinics ask

What does Outcomes do?
PROMs and outcome registries per specialty. Patient-reported outcome measures with the instrument as the contract: scores outside its bounds are refused, one baseline per patient per instrument, follow-ups build the patient’s own curve. The registry aggregates the cohort that has both ends — how many improved, and by how much — turning a practice’s results into evidence. For a chain, Branch by branch puts the same measure side by side at each branch: each patient counted where most of their visits between the two scores were seen, with those visits as their sessions, the median sessions, the average change and how many improved; a branch with fewer than five such patients shows its count only.
What data does Outcomes read and write?
Outcomes reads submissions, the chart, visits per branch and writes registry entries. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does Outcomes deliberately not do?
Registry exports are de-identified — the patient column is a per-export serial, and no name, MRN or id leaves. An identified export is a consent event, and v1 ships no identified export at all. The branch comparison reports where outcomes differ; it does not change anyone’s treatment plan.
What happens to our data if we uninstall Outcomes?
Registry data stays with the tenant.
Is Outcomes available today?
Yes — Outcomes is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see Outcomes running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Analytics

All 26 →
Featured inSurgical Practice stackOrthopaedicsOncologyNeurologyRheumatologyPhysiotherapy & RehabSpeech & Language TherapyOccupational TherapyPain Medicine