Mid-market community health systems
Especially those facing an EMR transition, payer-mix shift, or population-health expansion in the next 12–18 months.
Design Partner Program
Build the first production deployment of Vantage OS — with us.
We're selecting a small cohort of mid-market health systems and affiliated primary care networks to deploy Vantage OS for the first time and shape its clinical logic, signal mix, and operational workflow design.
Why we're doing this.
Most clinical AI tools are built far from the front line and dropped on operational teams to absorb. Vantage OS is being built the other way around — designed alongside the care coordinators, panel managers, and clinical leaders who'll actually use the worklists.
A design partner deployment is how we keep that grounded. You get early access, real engineering attention, and direct influence over the product. We get the operational honesty that turns a good system into a useful one.
Who we're looking for.
A good design partner usually looks like one of the following:
Integrated delivery networks (IDNs) with affiliated primary care
Where panel continuity and referral leakage materially affect contribution margin.
Primary care networks with risk exposure
ACOs, CINs, or capitated PCP groups managing rising-risk panels with manual chart-review workflows.
Most partners come in with 25,000–250,000 attributed lives, an executive sponsor at the VP level or above, and a care-coordination or population-health team that's already feeling the pain of fragmented signals.
What design partners get.
Direct access to the founding team.
Weekly working sessions with our CMO and engineering lead during deployment.
Influence on product direction.
Your clinical workflows shape the signal library and routing logic before broader release.
Preferred commercial terms.
Founding-cohort pricing locked in for the duration of the partnership.
Validated retrospective analysis.
Before live deployment, we run signals against your historical data so you see what would have surfaced.
Transition-period support.
Visibility maintained through EMR or revenue-cycle migrations — exactly when you need it most.
First look at every new capability.
New signals, integrations, and workflow tools land with design partners first.
What we ask of you.
An executive sponsor.
Someone at the VP level or above who owns the relationship and unblocks decisions.
Operational point of contact.
A care-coordination, population-health, or quality leader who can co-design workflows and give weekly product feedback.
Data access.
Standard ADT feed or equivalent flat-file export. No custom EHR engineering required, but someone needs to authorize the connection.
A 90-day window.
Real attention during deployment. After go-live the cadence drops, but the first 90 days require both teams to show up.
Honest feedback.
Including when something doesn't work. We need it. The product gets better because of it.
The 90-day deployment, in detail.
Phase 01
Weeks 1–2
Ingestion
Flat-file or standard ADT feed intake. Identity resolution and patient-timeline normalization. No EMR integration project, no middleware required.
Phase 02
Weeks 3–4
Validation
Retrospective review of 12–24 months of your historical data. We run the signal library against past events to surface what would have been flagged — and confirm that the signals are clinically and operationally meaningful in your environment before going live.
Phase 03
Weeks 5–8
Workflow Mapping
Working sessions with your care-coordination and clinical leadership to tune signals, set thresholds, and design how worklists are delivered into existing operational rhythms. The goal is fitting Vantage OS into the way your teams already work, not asking them to adopt a new tool.
Phase 04
Weeks 9–12
Go-Live
Prioritized worklists delivered to operational teams. Twice-weekly office hours with the founding team during the first month of go-live. Outcome review at day 90.
How we handle your data.
HJME Systems is built for healthcare environments that require transparency, auditability, and explainable decisions. Our design partner architecture is structured around the following principles:
HIPAA-aligned architecture.
Data is handled under BAA with encryption in transit and at rest. Access is role-scoped and logged.
Source-level provenance.
Every signal Vantage OS produces traces back to the underlying records that generated it. Care teams can see why a patient surfaced.
Explainable clinical logic.
No black-box risk scores. Signal logic is documented, reviewable, and tunable by your clinical leadership.
Audit logging.
Every signal generation, routing decision, and worklist action is logged for retrospective audit.
Designed with SOC 2 controls in mind.
Formal certification is on our roadmap; the architecture is being built against those expectations from the start.
Data minimization.
We ingest the data needed to produce the signals you've prioritized — not more.
Specific data handling, retention, and security terms are formalized in the design partner agreement.
Apply to be a design partner.
If your organization fits the profile above and the timing is right, we'd like to start a conversation. Briefings typically take 30 minutes and cover your current visibility gaps, the signals that would matter most, and whether a 90-day deployment makes sense for your team.