# Device source provenance

> A source’s role and the extent actually read determine which device statements it can support.

Regulator decisions, applicant summaries, manufacturer pages and original studies answer different questions. Conflicts retain their source rather than being averaged away.

Written by the Monun Device Research Group editorial team on October 25, 2026. Canonical address: https://kliftingdevices.site/topics/source-records.

## Why does device source provenance separate source roles?

A decision, a technical submission and a manufacturer description support different statements.

A regulator document can contain an applicant’s technical summary. Hosting in that document does not convert every technical claim into independent comparative clinical evidence. An original study has its own model, population and endpoint boundaries.

**Source roles kept separate**

| Role | Useful question | Limit |
| --- | --- | --- |
| Regulatory decision | Which indication and jurisdiction? | No universal efficacy ranking |
| Manufacturer statement | Which name or technical configuration? | Party to the commercial claim |
| Original study | Which model and measured endpoint? | Only its studied conditions |

## How does device source provenance mark partial reading?

Selected sections, abstracts, indexed excerpts and full-text checks remain distinct reading states.

A downloaded file is not automatically a full-text review. An old IFU can be useful for its identified section while later events remain outside that revision. Citation metadata records those limits next to the source.

## What happens when device source provenance reveals conflicting values?

Conflicting observations keep their units, model context and source identities without producing an unverified average.

Oligio X frequency descriptions illustrate why source identity matters. A brand-branded commercial page with unverified affiliation does not have the same role as an authenticated manufacturer document or FDA submission. Recall scope also needs the exact tip and lot rather than a brand-wide summary.

**Fields retained when records differ**

| Field | Purpose | Boundary |
| --- | --- | --- |
| Unit and observation | Keep the actual value’s meaning | No unverified average |
| Source affiliation | Distinguish authenticated parties | Brand name alone is insufficient |
| Revision and date | Locate the text in time | Do not silently merge versions |

## How is device source provenance updated?

Changed documents trigger review of the linked model fields, explanations and language versions.

Routine checking concerns source links, safety records and revisions; it is not a guarantee of complete surveillance. Unread or blocked content stays outside confirmed statements until it is actually checked.

## What else do people ask about device source provenance?

### Are an FDA landing page and PDF independent studies?

They may be two locations for one regulatory event.

### Are PubMed and PMC separate papers?

They may provide access to the same original work.

### Does a full download mean full review?

The recorded reading extent determines what was checked.

### Can conflicting specifications be averaged?

Averaging does not resolve source or model identity.

### Are sources a device safety score?

No. Their roles and limitations remain individual fields.

## Where do these numbers come from?

- [K250065 : DENSITY; DENZA; DENSITY Noir](https://www.accessdata.fda.gov/cdrh_docs/pdf25/K250065.pdf) - U.S. Food and Drug Administration
- [Efficacy and Safety of Monopolar Radiofrequency for Tightening the Skin of Aged Faces](https://www.mdpi.com/2079-9284/11/3/71) - Cosmetics
- [Class 2 Device Recall XERF EFFECTOR 60](https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfres/res.cfm?id=216122) - U.S. Food and Drug Administration