EHR + PATHS
The EHR Knows the Clinical Story. PATHS Knows the Journey.
Electronic health records capture the clinical story: diagnoses, medications, procedures, treatment plans, and encounters. But much of the patient experience happens between those encounters.
PATHS captures another important part of the story: how patients engage with their care, what they understand, the Steps they complete, and where they may need additional support. PATHS makes patient engagement and follow-through more visible beyond clinical encounters.
Together, these two distinct records have the potential to provide healthcare organizations with a more complete understanding of the patient experience.
Two Complementary Records
Different Information. Equally Important.
EHR
The EHR captures diagnoses, medications, procedures, treatment plans, and encounters.
PATHS
PATHS captures structured patient journey engagement, learning, progress, and follow-through, including completed Steps, resources accessed, assessment results, and engagement over time.
The EHR captures the clinical story. PATHS makes the patient journey known.
Make the Journey Between Encounters Visible
What Happens Next Matters.
What did the patient understand? Which resources did they access? Which Steps did they complete? Where did they stop? PATHS provides timestamped engagement, assessments, and Reports at the individual and population level.
Delivering information is the beginning. Understanding what happens next is how healthcare learns.
API-First by Design
Integration Based on Need.
PATHS was built for integration from the beginning, with an API-first architecture that is foundational to the platform, not a connection feature added afterward.
This architecture provides a foundation for linking PATHS with other healthcare technologies while allowing the platform to remain focused on what it does best: understanding and improving the patient experience.
Full interoperability may be possible, but it isn't always necessary.
Healthcare organizations already maintain extensive clinical information within their electronic health records. What they often lack is visibility into how patients engage, what they understand, and whether they follow through between encounters.
PATHS captures that missing information.
For many organizations, a simpler approach may make the most sense: make relevant PATHS data available to the health system without requiring clinical information to flow back into PATHS.
This approach can reduce integration complexity while preserving the distinct purpose of each platform.
Full interoperability when needed. Simpler data exchange when sufficient.
1+1=3
When Two Records Are Known, a More Complete Picture Emerges.
The electronic health record tells the clinical story. PATHS reveals how patients engage with their care throughout the journey.
Each record provides valuable information independently. But when both are known, healthcare organizations have the potential to understand something more: how clinical decisions, patient understanding, engagement, and follow-through relate to one another.
That fuller perspective creates opportunities to identify gaps, improve care processes, and learn from the experiences of individual patients and entire populations.
Make the Invisible Journey Visible.
Start with one workflow. Understand what happens. Improve the next journey.