ClaimData is now Affiant. Read the announcement.
Illustration of client functional data flowing from a phone through looping streams to a doctor reviewing daily evidence for a medical source statement

Equipping Treating Sources: How Functional Data Transforms Medical Source Statements

March 29, 2026 · Affiant Team

When your claimant's physician writes "in my judgment, the patient would need to rest during the workday," the ALJ can substitute their own judgment. When the physician writes "based on documented daily reports over eight months, the patient rests an average of 2.3 hours per day" — that's a different statement entirely.

Medical Source Statements (MSS forms) are among the most important pieces of evidence in SSD hearings. A treating source's RFC opinion, when properly supported, can be the difference between a favorable and unfavorable decision.

But most MSS forms are weak. Not because treating physicians don't care about their patients — they do — but because they lack the data to provide the specific, quantified opinions ALJs need.

When a physician completes an MSS form, they typically work from two sources:

1. Clinical notes: Their office visit documentation, which — as Art 1 explains — captures clinical findings, not functional capacity 2. Clinical impression: Their general sense of the patient's limitations based on their treating relationship

The result is MSS opinions that rely on qualitative clinical judgment rather than documented functional evidence. They contain phrases like:

  • "In my opinion, the patient would likely need to rest during the workday"
  • "I believe the patient has difficulty with prolonged sitting"
  • "The patient would probably miss work 2–3 days per month"

These opinions are not wrong. But they are vulnerable. ALJs can — and regularly do — discount MSS opinions that lack specific, objective support. When the treating source's opinion is based on "clinical judgment" rather than documented evidence, the ALJ has discretion to give it less weight.

The 2017 regulatory change (effective for claims filed March 27, 2017 and later) eliminated the "treating physician rule" that had previously given controlling weight to treating source opinions consistent with other evidence. Under the current regulations (20 CFR § 404.1520c and § 416.920c), ALJs evaluate all medical opinions based on five factors:

1. Supportability — how well the opinion is supported by the source's own evidence and explanations 2. Consistency — how consistent the opinion is with other evidence in the record 3. Relationship with the claimant 4. Specialization 5. Other factors

Supportability and consistency are the most important factors. Both favor MSS opinions grounded in documented functional evidence rather than clinical impression alone.

Supportability asks: does the treating source explain and support their opinion with relevant evidence? An MSS that says "based on documented daily functional reports over eight months, the patient requires an average of 2.3 hours of rest/reclining per day" is supported by specific evidence. An MSS that says "in my opinion, the patient needs to rest" is supported by clinical judgment alone.

Consistency asks: is the opinion consistent with other evidence in the record? When the record includes a longitudinal functional record showing daily rest/reclining data, and the treating source's MSS opinion cites that data, the opinion is consistent with documented evidence. Without the functional record, the MSS opinion may be inconsistent with MER that doesn't document rest/reclining needs — not because the opinion is wrong, but because the MER-RFC gap leaves function undocumented.

The treating source coordination methodology provides physicians with the documented functional data they need to write MSS opinions grounded in evidence rather than impression.

Pre-MSS Functional Summary

Before requesting an MSS from a treating source, provide a functional data summary covering the documentation period. This summary includes:

  • Physical function averages: Documented sitting tolerance, standing tolerance, rest/reclining time, lifting/carrying capacity — with daily averages, ranges, and trends
  • Cognitive function data: Documented off-task frequency, concentration duration, task completion rates
  • ADL limitation patterns: Documented rates of independent vs. assisted performance across daily activities
  • Medication side-effect frequency: Documented rates of side effects affecting daily function
  • Symptom variability: Good day/bad day distribution, flare-up frequency and duration
  • Treatment compliance record: Appointment attendance, medication compliance

This summary gives the physician what they don't have from OVNs alone: a quantified picture of how their patient functions across the 23+ hours per day they don't observe.

The Transformation in MSS Quality

With functional data in hand, the physician's MSS opinions shift:

MSS DimensionWithout Functional DataWith Functional Data
Rest/reclining needs"In my judgment, the patient would need to rest approximately 2 hours during a workday""Based on documented daily reports over eight months, the patient rests or reclines an average of 2.3 hours per day during waking hours, with a range of 1.0 to 4.5 hours. This is consistent with my clinical assessment."
Off-task time"The patient has difficulty concentrating""Daily records document symptom-related task interruptions on 68% of days, averaging 3.2 episodes per day. Based on these records and my clinical findings, I estimate the patient would be off-task approximately 20–25% of the workday."
Absenteeism"The patient would probably miss 2–3 days per month""Daily records show the patient was unable to complete basic daily activities on 31% of documented days. Based on this documented pattern and my clinical assessment, the patient would likely miss approximately 6–7 days of work per month."
Sitting tolerance"The patient has difficulty with prolonged sitting""Documented records show the patient reports needing to change position after 15–25 minutes of sitting on most days. I concur based on my clinical findings of [specific findings]."

The second column in each row is harder for an ALJ to discount. The opinion cites specific, documented evidence. It satisfies the supportability factor. And because the documented functional record is part of "other evidence in the record," it also strengthens consistency.

A common concern: will treating sources be willing to review functional data and incorporate it into their opinions?

In practice, most physicians welcome it. Completing MSS forms is an uncomfortable exercise for physicians precisely because they know their clinical encounters don't capture daily function. They are being asked to opine on dimensions they haven't observed. A functional data summary gives them the information they need to provide opinions they're confident in — grounded in data rather than guesswork.

The physician isn't being asked to adopt the claimant's self-report uncritically. They're being asked to interpret documented functional data through the lens of their clinical expertise. That is precisely what MSS opinions should reflect: clinical expertise applied to functional evidence.

When to request: 60–90 days before the scheduled hearing, after a sufficient documentation period (ideally 6+ months of daily data).

What to provide: A concise functional data summary (2–4 pages), organized by RFC category, with key averages, ranges, and trends highlighted. Not raw data — a curated summary the physician can review in 10–15 minutes.

How to frame it: "We've been tracking [patient]'s daily functional capacity as part of their disability case. Here is a summary of the documented data over the past [X] months. Would you be willing to review this alongside your clinical findings when completing the RFC assessment form?"

The MSS form itself: Provide a standard MSS form that maps to RFC categories and includes space for the physician to reference the functional data summary. Affiant provides a standard MSS form compatible with its reports.

For the complete methodology on building the functional record that enables this coordination, see From Daily Documentation to RFC Evidence. For how the resulting MSS is used at hearing, see Using Functional Evidence at Hearing.

A
Affiant Team
Affiant Team