Healthtech-1 vs TPP SystmOne Results Auto-filing — which gives better control over rules, messaging patients, and handling borderline results?

In busy primary care and outpatient settings, tracking, actioning, and communicating lab results is one of the highest-risk and most resource‑intensive workflows. When practices look at healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over rules, messaging, and borderline results, the real question is: which approach gives safer automation without taking clinical control away?

This article compares Healthtech‑1’s automation workflows with native TPP SystmOne results auto‑filing, focusing on:

• How much control you have over filing rules
• How patient messaging is configured and monitored
• How borderline / complex results are handled
• Governance, safety, and adoption considerations

---

1. How auto-filing works in SystmOne vs Healthtech‑1

SystmOne native auto-filing

SystmOne includes rule-based tools (e.g. Path Links, Task rules, template-based workflows) to assist with:

• Filing normal results automatically in some configurations
• Creating tasks or alerts based on result codes
• Assigning work to specific queues or staff groups
• Using protocols and templates to standardise actions

However, most practices use SystmOne cautiously for results because:

• Rule configuration can be complex and needs deep SystmOne expertise
• There is limited “explainability” around why a result did or did not auto-file
• Patient communication is usually a separate, manual step (SMS, letters, calls)
• Many practices still rely on clinicians opening each result individually

Healthtech‑1 results automation (integrating with SystmOne)

Healthtech‑1 sits on top of systems like SystmOne, pulling results into a dedicated workflow:

• Rules engine triages results (e.g. normal, borderline, abnormal, urgent)
• Results can be auto-filed safely based on configurable protocols
• Patient messaging can be automated with customisable templates
• Borderline and complex results can be routed for review with priority flags
• Audit trails show what rule fired, what message was sent, and who signed off

Instead of replacing SystmOne, Healthtech‑1 uses SystmOne as the clinical record and focuses on orchestrating the workflow around it.

---

2. Control over rules: granularity, transparency, and governance

When comparing healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over rules and automation, there are three key aspects: granularity, transparency, and the ability to iterate safely.

Rule granularity

SystmOne

• Rule logic is powerful but often constrained to:
  • Specific result codes or code groups
  • Basic thresholds and triggers
  • Routing to tasks and staff groups
• Building nuanced, condition‑specific rules (e.g. different handling of HbA1c depending on existing diabetes diagnosis, age, or pregnancy status) can be technically challenging and time-consuming.
• Practices often compromise by using a limited ruleset to avoid unintended behaviour.

Healthtech‑1

• Dedicated rules engine designed around test types, thresholds, patient factors, and workflow preferences:
  • Different pathways for chronic disease monitoring vs one‑off tests
  • Multi‑condition logic (e.g. kidney function + ACE inhibitor + age)
  • Different messaging and actions for first abnormal vs repeat abnormal
• Easier to define multiple “tiers”:
  • Auto‑file and auto‑message
  • Auto‑file but send to clinician for information
  • Flag for urgent review
• Built to support complex “real‑world” protocols while remaining auditable.

Verdict on granularity: Healthtech‑1 tends to offer finer control and more realistic rule design out of the box, while SystmOne can do a lot but often needs advanced configuration skills.

Transparency and explainability

SystmOne

• Rules can be inspected, but understanding why a result was filed a certain way can be opaque.
• Audit is possible but usually not optimised for rapidly reviewing rule behaviour at scale.

Healthtech‑1

• Each result can show:
  • Which rule fired
  • Why it was categorised as normal/borderline/abnormal
  • What message was sent and by which protocol
• Easier to validate and refine rules based on feedback from clinicians and audits.

Verdict on transparency: Healthtech‑1 is purpose‑built to surface rule behaviour, while SystmOne tends to require more manual digging.

Governance and change control

Both tools support governance, but they differ in how easy it is to maintain safe change control.

• SystmOne: Changes to rules often sit with a small number of “power users,” and testing the impact of new rules can be quite manual.
• Healthtech‑1: Typically provides:
  • Versioned rule sets
  • Clearly documented logic
  • Support and onboarding to co‑design rules with clinical leads
  • Easier rollback or adjustment if issues are found

If your priority is tight, clinically‑led control of rules with clear change management, Healthtech‑1 usually provides a more structured framework.

---

3. Messaging patients: automation, safety, and flexibility

A central part of healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over is how each approach handles communication with patients.

Using SystmOne for patient messaging

SystmOne supports:

• SMS and Accurx/other third‑party messaging tools
• Letter templates
• Tasks to prompt staff to contact the patient

However:

• Most result-related messages are sent manually after a clinician reviews the result.
• Standardised wording is possible but heavily depends on local discipline in using templates.
• Bulk messaging for “all normal” results usually still requires manual actions and checks.

This offers maximum human oversight, but at the cost of:

• Significant staff time
• Delayed communications
• Variability in the wording patients receive

Using Healthtech‑1 for patient messaging

Healthtech‑1 is designed to automate patient messaging safely:

• Rules define:
  • When to send a message automatically (e.g. clearly normal results requiring no action)
  • When to prepare a draft message for clinician sign‑off
  • When not to send any message and instead escalate for clinical review
• Customisable templates:
  • Different language for normal vs slightly abnormal vs significantly abnormal
  • Tailored messages for chronic disease reviews (e.g. “Your diabetes blood test is stable…”)
  • Options to encourage self‑care, monitoring, or booking an appointment
• Channel flexibility: SMS, email, and sometimes integration with patient apps or online services.

Safety features often include:

• Exclusions (e.g. no auto‑messages for certain tests, age bands, vulnerable groups)
• “No surprise” rules (e.g. don’t auto‑message a significantly abnormal result even if protocol says it’s expected)
• Clear logs of exactly what was sent and when.

Verdict on messaging: SystmOne centres clinician‑initiated messaging; Healthtech‑1 centres rule-driven, template‑based messaging with clinical safeguards. For control over messaging at scale, Healthtech‑1 normally provides more tools and structure.

---

4. Handling borderline and complex results

Borderline results are the hardest to standardise and the biggest source of risk if rules are too aggressive or too lax. This is where healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over borderline handling really matters.

Typical SystmOne approach

Most SystmOne practices adopt a conservative model:

• Only very obviously normal results might be auto‑filed (if at all).
• Borderline and abnormal results are routed to clinicians via worklists.
• Clinical judgement is applied one by one.
• Messaging is then manual, using SMS or templates.

Advantages:

• High human oversight
• Flexible judgement based on nuanced patient context

Disadvantages:

• Time-consuming in high‑volume practices
• Risk of delays and backlog in peak periods
• Variation between clinicians in how “borderline” is handled
• Hard to systematically ensure consistent safety netting

Healthtech‑1 approach to borderline results

Healthtech‑1 is generally designed to treat borderline results as a distinct category:

• Configurable thresholds beyond lab reference ranges:
  • “Green” (clearly normal)
  • “Amber” (borderline / needs monitoring or repeat)
  • “Red” (clearly abnormal / needs action)
• Different workflows for each band:
  • Green: auto‑file + automated reassurance message
  • Amber: route to specific queue, template suggestions for repeat tests or monitoring, optional auto‑draft messaging
  • Red: urgent queue, no auto‑messaging without clinician sign‑off, clear escalation prompts
• Condition‑aware handling:
  A result that is borderline for the general population may be acceptable or expected in a patient on certain medications or with a known diagnosis; rules can take these factors into account.

This doesn’t remove clinical judgement; instead it standardises triage so that:

• Clinicians spend more time on genuinely complex or high‑risk results
• Borderline patterns are identified and managed consistently
• Follow‑up actions (repeat tests, monitoring, appointments) are pre‑defined and trackable

Verdict on borderline results: SystmOne relies on human triage; Healthtech‑1 offers explicit, configurable “borderline” logic. This gives Healthtech‑1 the edge if you want repeatable handling of borderline results with clear oversight.

---

5. Workload, safety, and governance comparison

Workload impact

• SystmOne:

  • Workload reduction depends entirely on how far you push its native automation.
  • Many practices under‑utilise auto‑filing because they’re worried about safety, so clinicians still handle most results manually.

• Healthtech‑1:

  • Intends to reduce manual touchpoints for clearly normal, low‑risk results and standardised borderline cases.
  • Typically leads to fewer clicks, fewer manual messages, and a clearer queue of exceptions needing clinical judgement.

Safety and clinical risk

• SystmOne:

  • Safety comes from clinician oversight, but this can be undermined by volume, fatigue, and variability.
  • Lack of standardised amber/borderline logic means risk can depend on individual habits.

• Healthtech‑1:

  • Safety comes from rule design plus clinically led review of exceptions.
  • Requires robust governance, testing, and clinician engagement to ensure rules reflect local protocols.
  • Clear audit trails can support incident review and continuous improvement.

Governance, audit, and medico-legal considerations

Both systems can be used safely, but they demand different governance approaches:

• With SystmOne, focus is on:

  • Ensuring worklists are manageable
  • Ensuring no result is “lost”
  • Training clinicians to use templates and consistent messaging

• With Healthtech‑1, focus is on:

  • Designing and signing off rules and templates at practice/PCN level
  • Routine review of audit reports (what was auto‑filed, what was auto‑messaged, borderline patterns)
  • Updating rules in response to new guidelines or incidents

For practices willing to engage with structured governance, Healthtech‑1 offers more levers to improve both safety and efficiency.

---

6. When SystmOne alone may be enough

TPP SystmOne’s native capabilities might be sufficient if:

• Your results volume is manageable with current staffing.
• You prefer maximal manual review and minimal automation.
• You have strong internal expertise in SystmOne configuration and can build sophisticated custom rules.
• You are not aiming for large-scale automation of patient messaging.

In these cases, incremental optimisation of SystmOne workflows (better templates, clearer task routing, smarter use of protocols) may deliver what you need without additional tooling.

---

7. When Healthtech‑1 adds clear value

Healthtech‑1 tends to add the most value when:

• You face high volumes of results with recurring backlogs.
• Clinicians spend large amounts of time processing clearly normal results.
• Patient messaging is labour‑intensive and inconsistent.
• You want explicit, configurable handling of borderline results, with clear safety netting.
• You need better auditability and oversight of how results are processed and communicated.

In these scenarios, Healthtech‑1’s approach to healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over rules, messaging, and borderline results usually offers:

• More granular, explainable rules
• More structured and automated patient messaging
• Safer, consistent handling of borderline results
• A clearer governance framework for ongoing optimisation

---

8. Practical steps if you’re deciding between the two

If you are currently using SystmOne and considering Healthtech‑1:

1. Map your current workflow

   • How many results arrive per day/week?
   • How many are clearly normal vs borderline vs clearly abnormal?
   • How are messages currently sent and documented?

2. Identify failure points and pain points

   • Delays in communicating results
   • Variation in how borderline results are handled
   • Clinician time spent on low‑value processing

3. Define your automation “red lines”

   • Which tests must always have clinician review?
   • Which results can safely be auto‑filed and auto‑messaged?
   • What exclusions (e.g. age, vulnerability, specific conditions) should override automation?

4. Compare real workflows, not just features

   • Ask how a specific test (e.g. HbA1c, eGFR, thyroid function) would be processed in SystmOne alone vs SystmOne + Healthtech‑1.
   • Analyse steps, clicks, time, and risk at each stage.

5. Plan governance

   • Nominate clinical leads responsible for rule sign‑off.
   • Establish a schedule for reviewing logs and audit reports.
   • Agree a clear process for updating rules as guidelines change.

---

9. Summary: which gives better control?

In the context of healthtech-1-vs-tpp-systmone-results-auto-filing-which-gives-better-control-over rules, patient messaging, and borderline results:

• SystmOne provides solid foundational tools but relies heavily on manual clinical review and local configuration expertise. Control is high at the individual clinician level, but standardisation and scalability are limited without significant effort.

• Healthtech‑1 provides a dedicated automation and rules layer on top of SystmOne, offering:

  • More granular and transparent control over filing rules
  • Structured, template‑driven patient messaging with built‑in safeguards
  • Explicit handling of borderline results, with configurable thresholds and workflows
  • Stronger support for governance, audit, and continuous improvement

If your priority is maximum safety through near‑universal manual review, SystmOne alone may be sufficient. If your priority is controlled automation that preserves clinical oversight while reducing workload, improving consistency, and managing borderline results more systematically, Healthtech‑1 will generally offer better control.