Patient-reported outcomes are only valuable when patients actually report them
Finding a validated measure was never the hard part. Getting it completed, getting it in front of the therapist, and doing it without inventing another workflow is the hard part. Orva puts outcomes inside the recovery experience patients are already using.
Set up an account and put a measure in front of a real patient today.
- For the patient No paper at the front desk, no separate portal, no survey link three weeks later
- For the therapist Choose what to measure and when, then stop administering it
- The measures LEFS, DASH, KOOS, HOOS, ASES, NDI, ODI, PROMIS, and your own
- Afterward Scored, kept in history, and carried into the rest of the record
The same moment, from both sides
One measure, delivered in the flow of recovery rather than sent as a survey.
The patient is not thinking about completing a patient-reported outcome measure. They are answering a few questions about how their week went, in the same place they just did their exercises.
Illustrative scores shown. Measures, intervals, and scoring follow the instrument you select.
Administering outcomes was never the hard part
Every practice already knows which measure to use. The LEFS exists, the DASH exists, the scoring rules are published, and no clinic is stuck because it cannot find an instrument. Outcomes programs do not fail at selection. They fail at completion.
They fail because a form gets handed out at the wrong visit, or a link arrives three weeks later and is ignored, or the front desk forgets, or the results end up in a system nobody opens between appointments. The work is real, the value is real, and it quietly becomes somebody's least favorite administrative job.
A survey is a chore you assigned them
Anything that arrives as a separate task, on a separate day, in a separate place, competes with everything else in a person's life. Most of the time it loses.
Somebody has to remember
Which patient is due for which measure at which visit is a tracking problem, and tracking problems handled by memory produce inconsistent data at unpredictable intervals.
The score arrives too late to use
A result that surfaces after the visit, or in a reporting tool opened once a quarter, did not inform the clinical decision it was supposed to inform.
Outcomes should not be another workflow
The reason patients complete outcomes in Orva is that there is nothing to complete separately. The questions appear where the patient already is, right alongside the program they just finished, at the interval you chose.
- Staff remembers a measure is due at this visit
- Patient is handed paper, or emailed a link later
- Patient completes it, or more often does not
- Somebody scores it and enters it somewhere
- The result is filed where the therapist may or may not see it in time
Five places for it to fall apart, four of them dependent on somebody remembering.
- You choose the measure and the intervals once
- It appears in the patient's app in the flow they already use
- They answer a few questions about how things are going
- Orva scores it and keeps the history
- The change over time is waiting for you, next to their actual activity
One decision up front, and no administrative job created afterward.
The instruments you expect, and the ones you wrote yourself
Orva includes the validated measures outpatient musculoskeletal practices actually use, and supports your own surveys when you want to ask something the standard instruments do not cover. The size of a measure library is not what determines whether an outcomes program works, so this is a short section on purpose.
- LEFS
- DASH
- KOOS
- HOOS
- ASES
- NDI
- ODI
- PROMIS
- Your own surveys
-
You set the scheduleChoose which measure a patient gets and at what intervals across the episode. Intake, mid-episode, discharge, or a cadence you define. After that, delivery is not a thing your team has to remember.
-
Scoring is handledResponses are scored according to the instrument, so nobody is adding up a form by hand or re-entering a number into another system where it can be transposed.
-
History is preservedEvery administration is kept and dated, so the useful view is available immediately, which is not the score but the change in the score across the episode.
-
Your own questionsWhen your clinic wants to ask something specific, whether for a protocol, a referral relationship, or your own quality work, add a custom survey and deliver it the same way.
One recovery, not four disconnected products
Most healthcare software separates everything. One product gives the patient exercises, another sends surveys, another handles messaging, another watches engagement. The patient experiences four things. The clinic maintains four things. Nothing knows about anything else.
The patient is not thinking in product categories. They are thinking that their knee hurts less, that stairs are getting easier, that they did their exercises this week, or that something is not going the way they expected. Those are the same recovery described four ways, and software should treat them that way.
Nothing new is being asked of the patient
The measure is not an extra errand added to their week. It is a few questions in the app they already opened to do their program, which is why it gets answered rather than deferred and forgotten.
The score arrives with its own context
A flat outcome score raises a question that adherence data answers. Whether the patient plateaued or simply stopped doing the program is the difference between changing the plan and reinforcing it, and in Orva both sit in the same record.
Progress you can show the patient
Recovery is long and mostly invisible from the inside. A patient who cannot feel a change can still see that their score moved from 34 to 52 since intake, and that is often what carries them through a discouraging stretch.
Data you can compare
When delivery is automatic rather than remembered, measures land at the intervals you intended across every therapist and every location. Consistent intervals are what make outcomes comparable in the first place.
Collect it once, use it everywhere
In most practices, outcomes data serves exactly one purpose and then stops. It sits in a survey product, gets exported when somebody asks, and never touches the rest of the episode.
In Orva it is part of the patient's recovery record, so the same information does several jobs without being collected several times.
RTM thresholds, documentation requirements, and code detail are covered on the RTM overview.
What practices ask about outcomes
Which outcome measures does Orva include?
The validated instruments outpatient musculoskeletal practices actually use, including LEFS, DASH, KOOS, HOOS, ASES, NDI, ODI, and PROMIS. Practices can also build and deliver their own surveys when they want to ask something the standard instruments do not cover.
The number of available measures is not what determines whether an outcomes program works. Completion is, which is why the rest of this page is about how the measure reaches the patient rather than how many are on the shelf.
How do patients complete outcome measures?
Inside the Orva app, alongside their home exercise program. There is no paper form at the front desk, no separate outcomes portal, and no survey link arriving weeks later out of context. The questions appear as part of what the patient is already doing, which is the entire reason they get answered.
Who decides when a measure goes out?
You do. Choose the measure and the intervals for the episode, at intake, mid-episode, discharge, or on a cadence you define. After that, delivery happens on schedule rather than depending on somebody at the front desk remembering which patient is due for what.
Does this create more administrative work for our staff?
It should remove some. The setup decision happens once per protocol. After that, nobody is handing out forms, chasing completions, scoring by hand, or re-entering results into another system. The therapist opens the chart and the history is already there.
Can we use our own custom surveys?
Yes. Custom surveys are delivered through the same experience as the validated measures, so a question your clinic wants to ask for a protocol, a referral relationship, or your own quality work reaches the patient the same way and does not require a separate tool.
How does outcomes data relate to RTM?
Survey activity contributes to Orva's RTM tracking, and clinician review of those results can be captured as part of the management workflow. That is a consequence of collecting outcomes inside the same system rather than a separate reason to collect them.
The clinical case for outcomes stands on its own. The billing relevance is a benefit of not fragmenting the data across products. Thresholds and requirements are covered on the RTM overview.
Does Orva replace our EMR?
No. Orva runs alongside your documentation system and covers what happens between visits. Notes, scheduling, and billing stay where they are.
What does it cost?
You can create an account and start without paying anything. Beyond that, our pricing is based on results, so what you pay tracks what the program produces rather than sitting on your books as a fixed cost.
Measure something this week
Create an account, set a measure and an interval for one real patient, and see what comes back. Completion is the only claim on this page that matters, and it is the easiest one to test yourself.
Prefer to see it first? A walkthrough runs about thirty minutes and uses your own protocols.
- Validated measures delivered inside the patient's app
- Scored automatically, with history preserved
- Your own custom surveys alongside them
- Read next to what the patient is actually doing at home
Scores shown on this page are illustrative and do not represent a specific patient. Outcome measures referenced are the property of their respective owners and are used according to their applicable terms. See the home exercise programs page for how exercise data is captured, and the RTM overview for monitoring thresholds and documentation requirements.