Source notes
How to trace a health record to its source in SourceWeave
Inspect organization labels, source-system identifiers and per-category counts to understand the provenance shown in an authorized snapshot.
Start with the returned source cards
Each card represents source metadata returned with the snapshot. It shows an organization label when available, the source-system identifier and a last-sync field. The cards are not a directory of every provider a person has ever visited.
Select a source and read the matching count
Choose “Inspect provenance” on a card. SourceWeave counts entries whose source field exactly matches the selected source’s system identifier. That is a specific matching rule, not an inference from similar organization names or nearby dates.
- Read the source-system identifier as well as the friendly label.
- Select the source you mean to inspect.
- Compare the matched total with the category counts below it.
- Expand source metadata when a label or timestamp needs more context.
Keep unmatched information unresolved
If a returned record lacks the matching source field, this view does not assign it to a source by guesswork. A low count can therefore describe the attribution available in the response rather than the total information held by the healthcare organization.
Use provenance to frame a precise question
Instead of asking whether the app has everything, ask which source identifiers and categories were returned and which records explicitly identify them. SourceWeave does not establish complete clinical coverage or availability at every organization using an EHR. Live connections remain pending production activation.
Questions about this guide
Does choosing a source make a new provider connection?
No. It selects a source already present in the returned snapshot.
Why might a record not appear in a source count?
The provenance view requires an exact match between the record’s source field and the selected system identifier.