The atlas journal
Why similar entries remain separate in a health timeline
Learn how CareThread Atlas preserves record IDs and source context instead of automatically merging similar-looking events.
Similar wording can describe different records
Two entries can have similar labels while differing in category, date, status or source. The timeline preserves the returned entries so that a reader can inspect those differences. It does not collapse them merely because the titles look alike.
Inspect identity before calling something a duplicate
Open each event and compare its supplied fields. The displayed ID and source label provide a starting point; the expanded JSON provides more context. If the entries remain unclear, preserve the uncertainty rather than assuming that one can be discarded.
Presentation is not reconciliation
Sorting and filtering make a record easier to navigate. Deciding that two entries represent one clinical event is a different task with different evidence requirements. CareThread Atlas currently implements the navigation task and leaves source entries intact.
Design a future merge feature with traceability
An operator adding a merged view should retain access to every contributing entry and explain the matching rule. Ambiguous cases need a visible outcome. The current source implementation does not provide automatic deduplication, and these notes are not a claim that a reconciliation feature already exists.
FinchNode provides categories; Atlas preserves the trail
CareThread Atlas builds its timeline from the authorized categories returned through FinchNode. The product adds a category label for navigation and a chronological view while keeping the supplied record fields inspectable. That separation matters when two entries appear to describe the same thing.
Questions about this guide
Does CareThread Atlas remove repeated-looking records?
No. It retains separate returned entries so their source fields can be inspected.