Keeping the context beside your vital signs

Begin with what the source supplied

PulseTrellis gives each recorded measurement room for its name, value, unit and date. The goal is to make the available record readable. It does not turn a measurement into a wellness grade. If a source omits a field, the viewer cannot recover that missing context by changing the visual design.

A date deserves to stay visible

A measurement in a record may describe an earlier encounter. Showing it without its supplied date could make it seem current. PulseTrellis keeps temporal context close to the value and distinguishes a source measurement from the state of the latest data sync. The time a record was retrieved is not necessarily the time a measurement was taken.

Units are part of the value

The interface preserves the unit text supplied with a measurement rather than silently converting every entry to a preferred display. Visitors should avoid assuming two similarly named entries are directly comparable. The software is a reading surface for the record; it does not establish measurement conditions or calculate a clinical interpretation from incomplete information.

Where the record enters the garden

FinchNode provides the authorization and normalized-data interface used by our connection service. PulseTrellis focuses on the presentation that follows that boundary. A visitor must choose categories and complete the hosted authorization flow before a record can be requested. Live activation is still pending, and no example measurements replace an unavailable connection.

A quiet interface with explicit limits

PulseTrellis displays only the authorized snapshot, including available warnings about coverage. It does not provide continuous monitoring, clinical alerts or a complete history simply because a page is open. Use the supplied source context to frame questions for your care team rather than treating the display as a fresh measurement.

Sources and implementation

• About the FinchNode connection layer