Published Policy v1.0 · effective 2026-08-18 Prior versions

Patientflows Service Description

Version 1.0 · Effective 18 August 2026 · A Published Policy under Section 18 (Standard) / Section 19 (Founder Cohort) of the Master Subscription & Services Agreement.


1 · What this document is, and what it does

This document describes the functions included in a Patientflows subscription. It exists so that one question has a written answer: when Patientflows releases something new, is it included in what you already pay for, or is it a separately priced module?

The Agreement answers that by reference to this document:

Included at no additional charge — improvements, corrections, performance work and capability enhancements to the functions described here as of your Effective Date, and any function Patientflows later folds into a tier at no charge.

Not included — a module that Patientflows separately markets and separately prices, offers generally to customers as a distinct product, and identifies as such in Section 4 below.

Patientflows may not re-characterise a function described here on your Effective Date as a separately priced module, and may not move a function out of your tier in order to charge for it. That restriction is in the Agreement, not merely here, and it is the reason this document can be updated on notice without putting your subscription at risk.

This document does not state what is built today. Delivery status is Exhibit C of your Agreement, completed in your own environment and initialled by you. This document states what is included in the price. The two are deliberately separate: a function can be included and not yet built, and Exhibit C is where that is disclosed honestly.


2 · Included in every tier — the spine

The clinical record and the workflow that produces it are bundled in every tier. They are never a line item, never an add-on, and never described as free. They are the spine of the platform.

FunctionIncluded
Patient recordDemographics, history, medications, documentation and storage. The patient is the spine of the data model
Wound recordWound as a first-class entity, with its own history, measurements and imagery
Clinical documentationStructured, wound-care-native documentation with versioned, effective-dated protocols
ARC FileAssembly of the documentation record for a course of care
Provider attestationElectronic signature and attestation. The provider is always the author
Sherpa routingThe New Task router — prescriptions, labs, messages and care coordination proposed as options and confirmed by the provider
Scribe captureAmbient and typed capture during the encounter
Wound measurementManual length × width × depth with derived area and volume
Clinical imagingIn-app image capture and storage against the wound record
Offline capture and syncDocumentation and schedule access without connectivity, with verified sync on reconnect
eCQM / quality captureStructured capture at documentation time. Quality reporting is not a separate surface
Care coordinationWave 1 scope as described in Exhibit C
Audit logging and record managementFull audit trail and HIPAA-compliant record handling
Data exportSelf-service export in the formats stated in Exhibit C, at any time, without charge
Transition assistanceBounded assistance migrating to another platform, at no charge, as stated in Exhibit D
Roles and permissionsUnlimited non-attesting users — nurses, MAs, coordinators, front desk, billing, admin — at no per-user charge
UpdatesAll improvements, corrections, performance work and capability enhancements to the above

Sherpa Credits meter AI compute and usage only. They are not tied to, and do not vary with, clinical volume, patient volume, reimbursement, product fulfilment, or the volume or value of any referral. Grants by tier are stated in Exhibit E.


3 · Included, varying by tier

These functions are included, and their scope or capacity varies by subscription tier as stated in Exhibit A. Moving between tiers is a tier change, not the purchase of a module.

FunctionVaries by tier as
Providers of RecordSeats included per tier; additional seats at the seat rate in Exhibit A
Sherpa Credit grantMonthly grant per tier, plus a grant per added seat
ARC TeamHuman support scope, included at the tiers that state it
OnboardingWhite-Glove Onboarding scope per tier, per Exhibit B
SupportResponse targets and channels per tier

4 · Separately priced modules

A function appears on this list only after it is generally offered to customers as a distinct, separately marketed and separately priced product. Nothing is added retroactively: a function described in Sections 2 or 3 on your Effective Date cannot later be moved here.

ModuleStatus
(none)As of v1.0 there are no separately priced modules. Every function Patientflows offers today is included in the tiers

Where a module is added in a later version of this document, it is added here with its effective date, and existing customers may add it by Order Form at the rate then in effect. Adding a module to this list does not remove anything from Sections 2 or 3.


5 · Not part of the subscription at all

For completeness, because these are commonly assumed to be included:


6 · How this document changes

Updated on at least thirty (30) days' written notice, or promptly where a change is required by law or to address a security risk. An update may not change pricing, fees, seat rates, Sherpa Credit allotments, the Term, your rates or rate lock, the allocation of risk in Sections 10 through 12, or the handling of Protected Health Information. If an update materially and adversely affects you, you may terminate within thirty (30) days and receive a refund of prepaid fees for every whole month remaining, as provided in the Agreement.

Version history

VersionDateChange
1.02026-08-18Initial publication

Patientflows, LLC · This document is incorporated into the Master Subscription & Services Agreement. Not legal advice; counsel signs off before execution.