Healthtech-1 GP2GP filing (EMIS): how do we enable automation for degrade tasks and what gets filed automatically?

Healthtech-1 practices using EMIS often want to reduce manual GP2GP filing work, especially for degrade tasks, without losing clinical safety or oversight. The good news is that Healthtech-1 GP2GP filing (EMIS) supports controlled automation, and a defined set of items can be filed automatically when configured correctly.

This guide explains, in practical terms, how to enable automation for degrade tasks and what gets filed automatically in EMIS when using Healthtech-1, so your team can safely minimise repetitive admin work.

---

Understanding GP2GP filing and degrade tasks in EMIS

When a GP2GP transfer arrives in EMIS, Healthtech-1 analyses the incoming record and categorises each item into:

• Auto-file items – safe to file directly to the clinical record
• Degrade items – require review because:
  • The data is ambiguous, incomplete, or poorly coded
  • The mapping to EMIS codes isn’t clear
  • The clinical safety rules require a human to confirm the filing

Degrade tasks are the EMIS tasks created for those “uncertain” items. Automation in this context means:

• Reducing the volume of degrade tasks that need human review
• Allowing certain low‑risk items to be safely filed automatically
• Standardising how remaining degrade tasks are handled, so your team works faster and more consistently

---

What “automation” means for GP2GP degrade tasks

In Healthtech-1 GP2GP filing (EMIS), automation typically covers three areas:

1. Automatic filing of low‑risk items

   • Items that meet specific safety and data-quality rules are filed into EMIS without manual intervention.

2. Smart triage of degrade tasks

   • Only genuinely ambiguous or clinically sensitive items become tasks.
   • Non‑critical or repetitive items can be automatically resolved or standardised.

3. Consistent workflows for remaining tasks

   • Clear templates, task routing, and standard responses minimise variation between users and reduce errors.

Automation is always rule‑driven. You choose what is allowed to file automatically and what must stay as a degrade task. Healthtech-1 provides the framework; the practice controls the risk profile.

---

How to enable automation for GP2GP degrade tasks in EMIS

The exact steps can vary depending on the version and configuration of your Healthtech-1 service, but the overall process is generally:

1. Confirm your integration and access

Before you turn on more automation:

• Ensure Healthtech-1 is correctly integrated with EMIS for GP2GP filing.
• Verify that:
  • Your EMIS organisation and user permissions allow automatic filing.
  • The correct Healthtech-1 GP2GP user or role exists in EMIS (often a “system” or “robot” user).
  • Your practice is set up as a live Healthtech-1 site (not test).

If you’re unsure, your Healthtech-1 onboarding or support contact can confirm your current status.

2. Review your current GP2GP filing rules

Healthtech-1 usually operates with a set of default clinical safety rules for EMIS. These define:

• What is auto‑filed
• What becomes a degrade task
• What is blocked or flagged for manual review

Ask Healthtech-1 (or view your configuration notes) for:

• Your current auto‑filing rules
• A list of items always left as degrade tasks
• Any practice‑specific customisations already applied

This baseline is important before you enable more automation, so you don’t override safety-first defaults without knowing.

3. Decide your practice’s automation “risk profile”

Each practice can choose how aggressive or conservative it wants automation to be. In practice, this means deciding:

• Which categories of data you’re comfortable auto‑filing
• Which should always be reviewed as degrade tasks
• Whether you want different behaviour for:
  • Children vs adults
  • New registrations vs returning patients
  • High‑risk cohorts (e.g. patients on certain drugs)

Examples of configurable choices:

• “Always auto‑file past immunisations if fully coded and not conflicting.”
• “Never auto‑file significant past medical history; always present as degrade tasks.”
• “Auto‑file medication stop dates, but always manually review current repeat medications.”

Agreeing this policy internally helps Healthtech-1 configure automation that matches your governance and CQC expectations.

4. Enable or adjust auto-filing rules in Healthtech-1

Working with Healthtech-1 (or via your admin dashboard if available):

• Turn on auto‑filing for categories you’ve agreed are safe.
• Keep degrade tasks for anything requiring clinical judgement or interpretation.
• Apply exclusions for high‑risk items and sensitive codes (e.g. safeguarding, mental health, complex oncology history).

Healthtech-1 typically configures rules such as:

• “If coded, non‑duplicate and not on exclusion list → auto‑file.”
• “If ambiguous, text-only or conflicting with existing data → degrade task.”

These rules are applied consistently each time a GP2GP record is processed.

5. Configure EMIS task workflows for remaining degrade items

Even with automation, some degrade tasks will remain. To handle them efficiently:

• Set up task routing rules in EMIS:

  • Admin-type degrade tasks → Admin workgroup
  • Clinical-type degrade tasks → Duty doctor or named GP
  • Pharmacy-related items → Medicines management or pharmacist team

• Use task comments/templates:

  • Standardised messages for “GP2GP degrade – please file or annotate as appropriate”.
  • Clear identifiers that a task originates from Healthtech-1 GP2GP filing.

This ensures that whatever isn’t automated is still dealt with quickly and consistently.

6. Pilot, audit, and then expand automation

Automation should be introduced in phases:

1. Pilot phase

   • Enable automation for safe, low‑risk categories (e.g. some immunisations, simple observations).
   • Monitor for 2–4 weeks.

2. Audit phase

   • Randomly sample recent GP2GP transfers.
   • Compare what was auto‑filed vs what a clinician would have filed manually.
   • Check for:
     • Missing critical history
     • Incorrect coding or categorisation
     • Misfiled documents or results

3. Refinement phase

   • Tighten rules where over‑filing is a concern.
   • Loosen rules where you see a consistent pattern of safe manual filing that could be automated.

Over time, your degrade task volume should fall, while safety and record quality remain high or improve.

---

What gets filed automatically in Healthtech-1 GP2GP filing (EMIS)?

The exact behaviour depends on your configuration, but typical categories that can be auto‑filed safely (subject to rules) include:

1. Coded medical history that is clear and non-conflicting

Often auto‑filed when:

• The item is fully SNOMED coded (or mapped appropriately to EMIS codes).
• There is no direct conflict with existing EMIS data.
• The code is not on a local exclusion list (e.g. certain sensitive or ambiguous codes).

Examples:

• Past, clearly coded conditions (e.g. “Chickenpox – history of”).
• Straightforward, non-significant past illnesses that don’t affect current care.

Many practices still choose to keep “significant past medical history” as degrade tasks for clinician review, so this is configurable.

2. Immunisations and vaccinations

These are often good candidates for automation when:

• The vaccine is fully coded.
• Dates are clear and within expected ranges.
• There are no obvious duplicates conflicting with existing EMIS entries.

Examples:

• Childhood immunisation schedule items.
• Seasonal flu vaccines recorded in the past.

Some practices choose:

• “Auto‑file all unambiguous, coded immunisations.”
• “Flag and task any immunisations with missing batch or uncertain dates.”

3. Investigations, observations, and vital signs

Many simple observational entries can be auto‑filed if:

• They are coded and within a clinically plausible range.
• They don’t contradict existing critical observations (e.g. allergy status).

Examples:

• Historical BP readings, weight, height.
• Peak flow, BMI, simple coded observations.

For more complex results (e.g. pathology reports), practices often choose a mixed approach: text attachments may still be reviewed, while structured values are auto‑filed.

4. Allergies and adverse reactions (with strict rules)

Because allergies are high‑impact, Healthtech-1 uses conservative rules. Auto‑filing may be enabled if:

• The allergy is clearly coded and matches known drug/compound names.
• There is no conflicting existing allergy entry.
• The practice has explicitly agreed to allow this.

Many practices prefer allergies to remain degrade tasks so they can be confirmed by a clinician. Whether allergies are auto‑filed or not is a key configuration decision.

5. Medication history (partially automated)

Medication is complex, and practices usually adopt a hybrid:

• More likely to auto‑file:

  • Past medications that are clearly stopped and historical.
  • Simple acute items not currently active.

• Usually left as degrade tasks:

  • Current repeats and long‑term medications.
  • High‑risk drugs (e.g. warfarin, DOACs, methotrexate, lithium, insulin, opioids).
  • Items with unclear dose, route, or formulation.

Healthtech-1 can be configured so that repeat reauthorisation or active medication lists always require clinician review, even if some historical items are auto‑filed.

6. Administrative and demographic elements

Some non-clinical items may be auto‑filed or handled automatically, such as:

• Certain coded administrative notes (e.g. “Patient moved abroad – past”).
• Some demographic flags when supported by EMIS (though most demographic changes are handled by core GP systems, not via Healthtech-1).

Again, this is controlled by your configuration and local data governance policies.

---

What is usually not auto-filed and stays as degrade tasks?

Even in a highly automated setup, some GP2GP items are best kept for manual review:

• Ambiguous or free-text-only entries

  • Items with no reliable code or unclear clinical meaning.

• Conflicting or duplicate data

  • For example, a new allergy that conflicts with existing EMIS entries.

• Sensitive or high-risk information, such as:

  • Complex mental health history
  • Safeguarding and social services involvement
  • High‑risk medication regimes
  • Oncology or transplant history

• Complex documents and attachments

  • GP letters, hospital discharge summaries, detailed scanned documents.

These items appear as degrade tasks so a clinician or trained admin can decide how to file or annotate them.

---

Best practices for safe automation of degrade tasks

To get the most from Healthtech-1 GP2GP filing (EMIS) while protecting clinical safety:

1. Document your local policy

   • Write down which categories are auto‑filed, and which stay as degrade tasks.
   • Share this with all clinicians and admin staff.

2. Align with your Data Protection, IG, and clinical governance policies

   • Ensure your automation rules are acceptable for CQC inspection and local governance.

3. Provide training

   • Show staff:
     • How auto‑filed items appear in EMIS.
     • How to handle degrade tasks consistently.
     • What to do if they spot an incorrectly auto‑filed entry.

4. Monitor and review regularly

   • Quarterly or biannual audits of GP2GP transfers.
   • Adjust rules if issues are detected or if your risk appetite changes.

5. Use feedback loops

   • Encourage clinicians to report any problems with auto‑filed items.
   • Share findings with Healthtech-1 so rules can be refined.

---

Troubleshooting: if automation doesn’t seem to work as expected

If you think automation for degrade tasks isn’t enabled or isn’t behaving correctly:

• Check recent GP2GP transfers

  • Are items you expected to auto‑file appearing as degrade tasks?
  • Are any items auto‑filing that you didn’t intend?

• Confirm settings with Healthtech-1 support

  • Ask for a summary of your active rules.
  • Verify that automation profiles are applied to your site and EMIS organisation.

• Verify EMIS user/permissions

  • Ensure the Healthtech-1 filing user exists and isn’t blocked or restricted.
  • Check that no local EMIS setting is preventing automatic filing.

• Review error or activity logs (if available)

  • Logs can show whether items were rejected, blocked, or downgraded to degrade tasks by rules.

---

Summary

In Healthtech-1 GP2GP filing (EMIS), automation for degrade tasks is enabled by:

• Integrating Healthtech-1 correctly with EMIS and confirming permissions.
• Agreeing a local, risk‑based automation policy.
• Configuring auto-filing rules for clearly coded, low‑risk items.
• Keeping ambiguous, sensitive, or high‑risk data as degrade tasks.
• Routinely auditing and refining your setup.

What gets filed automatically depends on your chosen configuration, but typically includes clearly coded history, immunisations, some observations and certain low‑risk medication history, while allergies, complex medications, and sensitive history usually remain as degrade tasks for manual review.

By tuning these rules with Healthtech-1, you can significantly reduce workload from degrade tasks in EMIS while maintaining safe, high‑quality GP2GP records for your patients.