Source notes
Last synced is not the date every health record was created
Understand the difference between a source sync timestamp, an individual event date and the category counts shown in SourceWeave.
A timestamp needs a subject
The source card’s last-sync field describes the source metadata supplied in the snapshot. It is not a replacement for the date on each medication, observation or encounter. A recently synced source can contain much older events.
Three counts answer three questions
Sources returned counts the source metadata entries. Authorized categories counts the categories available to this session. Missing categories reflects the response metadata. None of these, by itself, establishes the number of clinical events expected to exist at a provider.
Look at the source object when a date is absent
Expand the source metadata to see the supplied fields. A missing or unclear sync date should remain a question about the response. SourceWeave does not run a background source refresh merely because a visitor switches between cards.
Describe freshness without overclaiming it
An operator extending the product should say whether a time refers to a source sync, a clinical event, or the time the browser received data. Labeling all three as “updated” would hide distinctions the provenance view is intended to preserve. The current connection request is a one-time transfer, not a continuously updating feed.
Source metadata from FinchNode, provenance questions in SourceWeave
SourceWeave reads the source and category metadata returned through FinchNode and turns it into an inspectable provenance view. The site’s task is to explain what those fields support, including the limits of a timestamp or source count.
Questions about this guide
Does a recent sync date mean every event happened recently?
No. A sync timestamp and the dates of individual events describe different things.
Does selecting another card refresh that source?
No. It changes the provenance view within the existing returned snapshot.