Up to three named feeds
Agree which exports or supported connectors can answer the question. A single system may provide more than one feed.
The starter offer
Data Foundation Build
Start with a reporting decision. Paid discovery establishes which sources can support it, what the words in the report mean, and what evidence your team will accept.
What is included
One bounded reporting workspace.
The starter is designed for one client organization. We confirm source rights, history, volume, viewers, platform licenses, and engineering capacity before committing to an implementation.
Three reporting datasets
For each dataset, define what one row represents, how records match, and who owns each measure.
Three starter dashboards
Each dashboard has one page and up to five agreed measures. Your team reviews the numbers against the source.
Operating the reports
A refresh your team can check.
The proposed starting point is up to 12 months of available history, refreshed daily or weekly in the client’s approved environment.
Checks and exceptions
Required fields, duplicates, types, ranges, and freshness are checked. Reference totals are reconciled to agreed tolerances. Exceptions have an owner and an explanation.
Review and acceptance
Two consolidated dashboard review rounds are included in the proposed starter. Your approver verifies the measures, permissions, refresh window, and recovery steps.
Handoff
Receive the data dictionary, source mappings, dependencies, operating runbook, known limitations, and a training session for the report owner.
After delivery
Choose the support your team needs.
Your practice owns its data and chooses its approved platform. Ongoing support and governance are separate scopes.
Governance setup
Document data owners, definitions, access decisions, quality rules, and change approvals.
Maintenance
Agree on the assets to monitor, support hours, severity levels, escalation, and monthly health reporting. Additional sources or changed exports are reviewed separately.
Performance advisory
Once the reporting foundation is in use, discuss how the figures inform an operating decision. Advisory support is an optional follow-on.
Scope boundaries
What needs a different agreement.
The starter uses supported connectors or agreed exports and scheduled batch updates. Final scope follows discovery.
Custom APIs, real-time streaming, extensive backfills, complex record matching, and source-system repairs need separate technical review. More locations or feeds can change delivery effort.
Clinical recommendations, EHR replacement, predictive AI, and round-the-clock support are outside the starter.