ExecuMedical
EMERGE

EMERGE · Primary care intelligence and operations

See everything.
Act on what matters.

EMERGE is the operating layer above the systems a practice already has. It turns performance, people, capacity, premises and demand data into prioritised signals, turns the ones that matter into actions with a named owner, and records what happened next.

Status: Active product development
Current product
EMERGE Practice OS, the first EMERGE product, being built for general practice; primary care network views are a later stage
Role in the loop
See: understand what matters
Availability
Not yet publicly available, to buy or to trial. Early conversations are welcome.
  1. SeeEMERGE
  2. BuildEducation
  3. DeployWorkforce
  4. ImproveAdvisory

The principle

Not another dashboard.

Practices have never had more information. Clinical reporting, compliance folders, rotas, room plans, triage exports and alerts each show something. None of them decides what to do next, and none of them remembers whether it worked. That gap is the product.

A dashboard

Shows more

  • Shows more information
  • Leaves prioritisation to whoever happens to be looking
  • Has no owner, no due date and no outcome
  • Forgets what the organisation decided
The differenceSame signals. A different job.

An operating layer

Helps you act

  • Shows what needs attention, and why
  • Prioritises with rules that can be traced
  • Turns a signal into an action with a named owner
  • Records the intervention, the outcome and the evidence

If a feature only shows more data, it is not finished.

Built so a practice manager, partner or clinical lead can answer, quickly:

  1. What changed?
  2. What matters?
  3. Why does it matter?
  4. What should we do?
  5. Who owns it?
  6. Did it work?
  7. What evidence do we now have?

The operating loop

From signal to evidence.

One loop, shared by every domain. A deteriorating clinical indicator and an expired training certificate travel the same route. That is what makes EMERGE one product rather than a set of modules.

  1. Data
  2. Signal
  3. Priority
  4. Action
  5. Owner
  6. Intervention
  7. Outcome
  8. Evidence
Data
What the organisation already records or imports.
Signal
Something that warrants attention, with its reasons attached.
Priority
Priority, Watch or Opportunity, decided by rule.
Action
One organisational action model, whatever the source.
Owner
A named person and a due date.
Intervention
What was actually done.
Outcome
What changed, measured again.
Evidence
The record the organisation keeps.

The organisation remembers not only what it knew, but what it decided and what happened next.

The architecture

Modules are sensors. The product is the operating layer.

EMERGE does not replace a clinical reporting tool. It does record people, requirements, rooms and availability itself, because no practice system holds them in a form the loop can use; it records them as sensors, not as an HR system or a rota app. EMERGE sits where the signals meet and connects what they know into one organisational picture and one path to action.

  • Performance
  • Assurance
  • Guidance
  • Capacity
  • Premises
  • Workforce
  • Finance

Organisation signals

  1. Priority
  2. Action
  3. Intervention
  4. Outcome
  5. Evidence

Finance is direction only. The other domains exist in the current build at differing depths; establishing one common signal shape matters more than pretending every domain is complete.

Existing systems

Sit above, not instead of.

Clinical systems, reporting tools, and triage and demand exports each do a sensor’s job well. EMERGE is designed to sit above that kind of system rather than rebuild it. The value is in cross-domain context, prioritisation, ownership, outcomes and organisational memory.

Today, development works from exported reports and recorded facts. No live connections to clinical or reporting systems are claimed; the one external feed, public medicines and device alerts, is fetched on demand and classified like any other source. Every imported source is classified as live, operational snapshot, recent or planning, and that class limits what EMERGE is allowed to say about it.

Connecting domains

Three sensors. One possible intervention.

The value is not detecting issues in separate domains. It is connecting them. The difference between information and operations is the sentence that follows the data: here is what your organisation could do about it.

Illustrative example

  • PerformanceA hypertension indicator is below trajectory.
  • PeopleA healthcare assistant holds the relevant, in-date competencies and has recorded availability on a weekday afternoon.
  • PremisesA treatment room has residual capacity in the same window.

Possible intervention

Run an afternoon hypertension recall clinic.

Presented for review with its capacity, room, workforce and cohort made explicit. A person decides. Nothing is assigned automatically.

The first cross-domain proof of this exists in the current build: a clinical need, an eligible person, residual capacity and a suitable room combined into one reviewable option. The example is illustrative and describes no organisation.

The Workforce module is now in development. For practices using both products, a planned connection would turn a need into a cover request, coordinate room and equipment reservations, and return delivery and value information. This integration is not live.

Where it stands

What is built, and what is not.

EMERGE Practice OS is being built for primary care. The following is built and tested in the current product. It is not yet publicly available.

  • Clinical performance signals from deterministic rules, with visible provenance.
  • Assure for people, requirements, evidence and competencies, with expiry surfacing as a signal rather than a spreadsheet entry.
  • Shared Actions with intervention, outcome and evidence recorded against them, across domains.
  • A Signal Centre and management cockpit that lead with exceptions and keep detail on demand.
  • Sites, rooms and derived capacity: availability minus what is already committed.
  • Deterministic workforce eligibility for a person, a site and an activity, with explicit reasons and no score.
  • Operational Needs and reviewable deployment candidates, matched on eligibility and dated residual capacity.
  • Provenance and freshness classes for imported and fetched sources, limiting what each is allowed to claim.
  • A vendor-neutral historical demand model for planning only, never presented as today’s position, with a working AccuRx import adapter; production validation against a real export is the outstanding step.
  • External guidance alerts with transparent, deterministic relevance matching.
  • Registered population intelligence: practice list size observed monthly from NHS England’s own published data, with deterministic month‑on‑month and 12‑month change and no signal attached.
  • Multi-practice group oversight: a practice can opt in to share summary counts or an agreed capacity package with one group it belongs to, counts-only and read-only, never an automatic booking across practices.

Not yet

  • Public availability, to buy or to trial
  • Named customers
  • Live integrations with clinical or reporting systems
  • Patient-identifiable decision support
  • Additional domains, including finance

Built and tested is not the same as available. EMERGE is not yet publicly available, and no release date is stated here.

What EMERGE will not claim

  • Official QOF payment unless calculated from validated, current specifications
  • CQC compliance, or a likely CQC rating
  • Clinical urgency from an operational score
  • That a person is competent, compliant or eligible without recorded, validated evidence
  • Contractual entitlement from incomplete data

Early product stages prefer aggregate, non-identifiable data. Before patient-identifiable data or clinically influential decision support are introduced, information governance and clinical safety are treated as first-class product work.

Design constraints

A cockpit, not a KPI cemetery.

These constraints protect the product from becoming a collection of technically impressive but disconnected features.

  1. Exceptions first. Detail on demand.

    The first screen answers what needs attention today. Domain detail exists, but it is one step away rather than the front page.

  2. One action model.

    Performance, assurance, capacity and premises issues create the same kind of Action, with a source, a reason, an owner, a due date and an outcome. That is how an organisation remembers.

  3. Rules decide. AI explains.

    Thresholds, eligibility, expiry and status come from auditable rules. AI may summarise, draft and suggest, clearly labelled and always reviewable.

  4. Never fresher than the evidence.

    Each imported source carries a freshness class. Live, snapshot, recent and planning data are allowed to make different claims, whatever day they were imported.

Talk to ExecuMedical

Follow EMERGE as it is built.

EMERGE is not yet publicly available. If you lead a practice or a primary care network and these are your problems, we would like to hear how they show up for you. What EMERGE sees, Education builds and Workforce deploys; what advisory work redesigns, EMERGE measures.

Get in touchExplore Education