Outcomes

● live in clinics

PROMs and outcome registries per specialty.

In plain words: Measure treatment results with patient scores.

Analytics · Full PHI · Every specialty

What Outcomes does

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.

How you actually use it

  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.
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

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 · 1
See the whole clinic →

What it reads

submissionsthe chart

What it writes

registry entries
Same patient record as every other app — nothing is copied into a silo. Data class: Full PHI.

What it does 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.

Every app page carries this section. A listing with only benefits is an advertisement.

Questions clinics ask

What data does Outcomes read and write?

Outcomes reads submissions, the chart 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.

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.

Ask about Outcomes

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 analytics apps
Featured inOrthopaedicsOncologyNeurologyRheumatologyPhysiotherapy & RehabSpeech & Language TherapyOccupational TherapyPain Medicine