Healthtech-1 vs MyBotGP (JifJaff) for pathology/normal results filing — how do they compare on safety, audit trail, and patient messaging?

Digital tools for handling pathology and normal results filing are now central to safe, efficient primary care workflows. Healthtech‑1 and MyBotGP (from JifJaff) both sit in this space, but they take quite different approaches. If you’re comparing them for safety, audit trail robustness, and patient messaging, it helps to be clear about what each solution actually does and how it fits into your clinical governance.

Below is a practical, clinic-focused comparison based on public information, typical product positioning, and common practice needs. For exact, up‑to‑date details, always check vendor documentation and your local implementation.

---

Quick overview: Healthtech‑1 vs MyBotGP (JifJaff)

Healthtech‑1

• Typically marketed as an end‑to‑end workflow automation platform for general practice.
• Often used for: pathology/normal results filing, document handling, registration workflows, online consultation processing, and structured protocols.
• Emphasis on: clinical safety (with defined protocols), integration with GP systems, structured triage/routing, and granular auditability.

MyBotGP (JifJaff)

• Robotic Process Automation (RPA) solution tailored for GP practices.
• Often used to automate tasks your staff would otherwise do manually in the clinical system (e.g., coding, filing, registering patients), including certain pathology or normal result workflows.
• Emphasis on: mimicking staff workflows, freeing up admin time, and integrating via the user interface rather than deeper clinical-system APIs.

When you look at pathology/normal results filing specifically, three questions matter most:

1. How is safety designed and evidenced?
2. How comprehensive and transparent is the audit trail?
3. How reliably and appropriately does the system manage patient messaging?

---

1. Safety in pathology/normal results filing

1.1 Clinical safety by design

Healthtech‑1

• Typically uses protocol-driven logic: results are processed against predefined rules (e.g., normal, abnormal, needs GP review, follow‑up required).
• Often includes clinical safety cases and documentation (e.g., in line with DCB0129 / DCB0160 in England), describing hazards, mitigation, and testing.
• Emphasis on structured workflows:
  • Normal/expected results can be auto‑filed with predefined actions.
  • Anything outside safe parameters is routed to the appropriate clinician or workflow queue.
• Tends to offer role‑based configuration: practices can specify which results can be automated and which must always be manually reviewed.

MyBotGP (JifJaff)

• RPA bots typically mirror what a human user would do in the clinical system. For pathology/normal results, that often means:
  • Logging in as a user or bot account.
  • Navigating to the results screen.
  • Applying pre‑defined decision rules (configured by your practice/JifJaff) to click and file results or create tasks.
• Safety is highly dependent on:
  • The accuracy and completeness of the bot scripts (what they click, when they stop, error‑handling).
  • The stability of your clinical system interface (screen layout/labels must be as expected).
  • Robust exception handling (e.g., if the result doesn’t match expected patterns, the bot should escalate, not guess).

Implication for safety

• Healthtech‑1 generally leans towards clinical-safety-led product design, with a rule engine that is built to handle clinical nuances and edge cases.
• MyBotGP is more like a digital assistant imitating your staff, so safety is tightly linked to how well your bot is configured and monitored in your specific environment.

1.2 Handling of abnormal or unexpected results

Healthtech‑1

• Typically distinguishes clearly between:
  • Results safe to auto‑file as normal.
  • Results needing clinical review or specific follow‑up.
• May include configurable thresholds and rules, e.g.:
  • “If result is within X range and matches Y rule, file as normal with coded note and standard message.”
  • “If abnormal, create a task for the GP/ACP and optionally draft a message requiring approval.”
• Usually supports hard stops: certain high‑risk result types are never auto‑filed and must always go to a clinician queue.

MyBotGP

• Bots can be configured to:
  • Auto‑file certain result types as normal.
  • Create tasks or alerts for anything abnormal.
• Safety relies heavily on ensuring the bot recognises abnormal patterns correctly and never mis‑clicks (e.g., filing as normal when the result is actually flagged abnormal).
• Good implementations use strict exclusion rules, so the bot only handles highly predictable, low‑risk patterns and leaves everything else for manual review.

Implication for safety

• For high‑risk or complex result types, practices often use MyBotGP to handle only a subset of straightforward normal results, whereas Healthtech‑1 tends to offer a more structured framework for safely differentiating normal/abnormal and applying consistent rules.

---

2. Audit trail and traceability

Auditability is central to both information governance and clinical safety. You need to know: who/what filed each result, what rule was applied, and whether the patient was messaged.

2.1 Recording who did what (user vs bot vs system)

Healthtech‑1

• Usually logs actions under a named system or service user, with clear metadata on:
  • Which protocol/rule handled the result.
  • What outcome was applied (filed as normal, task created, message sent, etc.).
  • Time and date of each step.
• Often integrates with clinical system logs, so that any action taken appears as if a particular “Healthtech‑1 user” or service account performed it, preserving standard audit structures.

MyBotGP (JifJaff)

• Bots typically act as a user within your clinical system, often under a designated “bot account”.
• The clinical system’s native audit logs then show that this bot user:
  • Opened the result.
  • Filed it, coded it, or created a task.
• Additional bot-level logs may be available via MyBotGP management tools, detailing:
  • The script executed.
  • Sequence of clicks/steps.
  • Errors and exceptions.

Implication for audit

• Healthtech‑1 tends to provide clinically structured audit data linked to protocols and decisions.
• MyBotGP provides user-like audit entries consistent with your practice’s existing logs, enhanced (if configured) by separate technical logs of bot activity.

2.2 Granularity and reporting

Healthtech‑1

• Typically offers dashboards or reports showing:
  • Number of results processed automatically vs manually.
  • Breakdown by protocol or rule.
  • Exception volumes (results routed for clinician review).
• This supports clinical governance reviews, e.g., checking how many normal results were auto‑filed and whether any patterns suggest under‑ or over‑automation.

MyBotGP

• Depending on configuration, you may get:
  • Bot performance reports (how many results processed per day, failure rates).
  • Logs of which process ran and whether a step failed.
• Clinical audit questions (e.g. “how many normal results were auto‑filed with standard message X this month?”) may require cross‑referencing clinical system reports and bot logs, because the bot is essentially emulating manual work rather than applying named “protocols”.

Implication for audit

• Healthtech‑1 generally makes it easier to audit clinical logic (which rule led to which outcome).
• MyBotGP makes it easier to audit operational workflow (“this bot processed X results”), but clinical audit detail often depends on how your practice sets up searches and reporting in the core clinical system.

---

3. Patient messaging: how results are communicated

3.1 Standardised templates and consistency

Healthtech‑1

• Typically provides configurable, standardised message templates for normal results:
  • E.g. “Your recent blood test was normal. No further action is required. If your symptoms persist, please contact the surgery.”
• Can attach the template to specific rules so that:
  • Normal result type A triggers message template A.
  • Normal result type B triggers template B, and so on.
• This supports consistent language, reduces variation between clinicians, and can be aligned with practice policies and medico‑legal advice.

MyBotGP

• Bots can send messages using whatever messaging mechanism your clinical system provides (SMS, app message, etc.), often using predefined text snippets that you or JifJaff configure.
• Templates can be consistent if carefully set up, but message structure is not usually part of a clinical “rule engine”; it’s part of the bot script (e.g. “for normal HbA1c under X, open template Y and send”).
• Any change to messaging policies may require updating bot scripts and/or templates.

Implication for patient messaging

• Healthtech‑1 is often stronger for rule-based, templated messaging that’s tightly integrated with clinical logic.
• MyBotGP can deliver consistent messaging, but requires careful configuration and ongoing script maintenance to keep messages aligned with your clinical policies.

3.2 Safety and clarity in messaging

Healthtech‑1

• Allows you to embed safety wording and clear signposting into templates, such as:
  • What the result means in simple terms.
  • What the patient should do next (or not do).
  • When they should contact the surgery or seek urgent care.
• Because templates are attached to specific protocols, the chance of mismatched message/result is reduced (e.g., sending a “normal” message for a borderline or abnormal result).

MyBotGP

• Safety in messaging depends on:
  • The accuracy of the classification logic in the bot.
  • Correct linkage between result type and message template.
• Good implementations use conservative rules:
  • If the bot cannot confidently apply the “normal result” template, it escalates to a clinician or admin for manual review and messaging.

Implication for patient messaging

• Healthtech‑1 can help provide a governed, protocol-driven messaging framework.
• MyBotGP can automate messaging effectively, but the risk of mis‑classification is more directly tied to how the RPA interacts with your system and how robustly it is tested and reviewed.

---

4. How they compare in practice: safety, audit trail, patient messaging

4.1 Safety comparison

• Healthtech‑1

  • Stronger where you need a clinical-safety-led automation framework, with defined protocols and centralised rules.
  • Better suited if you want to expand automation across multiple workflows while maintaining a coherent, documented safety case.

• MyBotGP (JifJaff)

  • Well suited for targeted, task-level automation where workflows are very predictable and you are comfortable managing RPA scripts.
  • Best approach is to keep the bot within strictly defined, low‑risk boundaries for pathology/normal results and maintain strong local oversight.

Overall safety takeaway

• Healthtech‑1 typically offers stronger built‑in clinical governance for pathology/normal results filing.
• MyBotGP can be safe and effective when carefully scoped, scripted, and monitored, but its safety profile is more dependent on local configuration and RPA governance.

4.2 Audit trail comparison

• Healthtech‑1

  • Provides highly structured audit data tied to protocols and rules.
  • Easier to demonstrate which clinical logic was used for each result and message.
  • Supports formal clinical governance reviews and quality improvement work.

• MyBotGP (JifJaff)

  • Leverages your existing clinical-system audit trail via a bot user.
  • Offers additional technical logs on bot activity.
  • Clinical auditing (e.g., normal vs abnormal handling) may require more manual reporting setup and reconciliation.

Overall audit takeaway

• For transparent, rule‑based clinical audit, Healthtech‑1 tends to have the edge.
• For operational audit (how the bot performed, where it failed), MyBotGP’s logs are helpful but need combining with clinical system data to answer governance questions.

4.3 Patient messaging comparison

• Healthtech‑1

  • Stronger at integrating messaging with clinical logic.
  • Consistent, templated messages triggered by rules.
  • Easier to standardise patient communication across clinicians and sites.

• MyBotGP (JifJaff)

  • Can automate patient messaging via RPA using your existing channels.
  • Needs careful setup to ensure the bot uses the correct templates and only for safe, clearly defined “normal” scenarios.
  • Changes in messaging policies may require explicit bot/script updates.

Overall messaging takeaway

• If your priority is governed, standardised patient messaging tightly linked to clinical rules, Healthtech‑1 is typically stronger.
• If your goal is to extend automation to your current messaging workflows with minimal system change, MyBotGP can be effective, but you must manage templates and rules diligently.

---

5. Governance, implementation, and choosing between them

5.1 Governance considerations

For pathology/normal results filing, clinical governance should drive the decision more than simple efficiency:

• Ensure any solution (Healthtech‑1 or MyBotGP):
  • Has clear documentation of clinical risk assessment and mitigation.
  • Supports your DSA, DPIA, and clinical safety case obligations.
  • Has a transparent audit trail and accessible reporting.
  • Allows you to set safe boundaries for automation (which results can or cannot be auto‑filed).

5.2 Implementation and change management

• Healthtech‑1

  • Requires configuration of protocols and rules.
  • Involves change management: staff must understand what is automated and how to handle exceptions.
  • Suits practices/PCNs looking for a platform approach to workflow automation beyond just pathology.

• MyBotGP (JifJaff)

  • Requires careful scripting and testing in your live environment.
  • Sensitive to UI changes in your clinical system (which can affect bots).
  • Works well when you have clear, stable processes and someone accountable for RPA governance.

5.3 Which may suit your practice better?

• Choose Healthtech‑1 if:

  • You want a clinically led, rule-based automation framework for pathology and other workflows.
  • You prioritise standardised patient messaging and deeply structured audit trails.
  • You plan to scale automation across multiple administrative and clinical processes.

• Choose MyBotGP (JifJaff) if:

  • Your main goal is to relieve staff of repetitive, clearly defined tasks with minimal change to underlying systems.
  • You have strong local capacity to manage RPA scripts and governance.
  • You intend to use automation more as a “digital extra pair of hands” than as a centralised clinical-direction engine.

---

6. Practical steps before deciding

Before choosing between Healthtech‑1 and MyBotGP for pathology/normal results filing, it’s worth:

1. Mapping your current results workflow

   • Identify which result types could safely be automated.
   • Clarify which must always be clinician‑reviewed.

2. Defining safety requirements

   • Minimum expectations for clinical safety documentation.
   • Required escalation paths for abnormal or unexpected results.

3. Checking audit and reporting needs

   • What questions must you be able to answer in an audit?
   • How frequently will you review automation performance?

4. Agreeing a patient messaging policy

   • Standard wording for “normal” vs “borderline but acceptable”.
   • Rules for when patients should be contacted vs not contacted.
   • Languages, accessibility, and safeguarding considerations.

5. Running a controlled pilot

   • Start with a limited set of low‑risk tests.
   • Review mis‑classifications, patient feedback, and workload impact.
   • Adjust rules/templates/bot scripts before scaling.

---

In summary, for pathology/normal results filing, Healthtech‑1 typically provides a more clinically structured, rule-based framework with strong safety, audit, and patient messaging features built into the product design. MyBotGP (JifJaff) offers flexible RPA-driven automation that can safely handle a subset of predictable, low‑risk workflows when well configured and governed, but its safety and audit strengths are more dependent on local setup and ongoing oversight. The best solution for your setting will depend on how much you want a centralised clinical rules engine versus a digital workforce that mimics your existing manual processes.