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

Most EMIS practices using Healthtech-1 for GP2GP filing want two things: to minimise manual “degrade” work, and to be certain what the system can safely file automatically. This guide walks through how Healthtech-1 GP2GP filing works with EMIS, how to enable automation for degrade tasks, and exactly what gets filed automatically versus what still needs clinical review.

Understanding Healthtech-1 GP2GP filing in EMIS

Healthtech-1 GP2GP filing (EMIS) is designed to:

Import electronic GP2GP records into EMIS Web
Automate safe, low‑risk filing actions
Surface “degrade” items that need human review
Provide audit trails for what was filed and by whom (system vs user)

In practice, the workflow usually looks like this:

A GP2GP record is received in EMIS.
Healthtech-1 picks up the record and analyses its contents.
Items are triaged into:
- Auto‑filed (filed directly into EMIS)
- Degrade tasks (require user review/decision)
Clinicians or admins process remaining degrade items using the Healthtech-1 workflow.

Automation is controlled centrally in Healthtech-1 and then reflected in how tasks and items appear in EMIS.

What are “degrade tasks” in the EMIS Healthtech-1 flow?

“Degrade” refers to situations where the GP2GP content cannot be filed with its original quality or structure, or where clinical judgement is needed. Typical degrade scenarios include:

Unmapped codes
- Incoming SNOMED/Read codes that don’t match EMIS equivalents.
Ambiguous problem lists
- Problems that might be historical versus active.
Complex medication histories
- Non‑formulary drugs, discontinued items without clear stop reasons, or mismatched dose instructions.
Allergy and adverse reaction issues
- Conflicting allergy status, vague descriptions, or duplicated entries.
Document and attachment problems
- Unsupported formats, missing metadata, or unclear clinical category.
Demographic discrepancies
- Differences between incoming GP2GP data and existing EMIS registration details.

Healthtech-1 flags these as degrade tasks so they can be checked before they affect the permanent record.

Enabling automation for degrade tasks in Healthtech-1 (EMIS)

How you enable automation depends on your local setup and permissions, but the core steps are broadly consistent. Always follow your organisation’s SOPs and governance rules.

1. Check your Healthtech-1 configuration access

Before changing automation behaviour:

Confirm you have administrator or GP partner-approved access to the Healthtech-1 configuration portal (or equivalent console).
Verify whether your ICB/PCN or IT provider manages settings centrally—some controls may be locked down.

If your practice doesn’t have direct access, you may need to request changes through your IT team or Healthtech-1 support.

2. Review current GP2GP filing rules

Within the Healthtech-1 GP2GP filing settings for EMIS, identify:

Which categories are currently set to Auto‑file
Which are set to Degrade / require review
Any existing whitelists/blacklists for codes, drugs or document types

Typical configuration screens will group settings by:

Problems / diagnoses
Medications
Allergies
Investigations / results
Documents and attachments
Demographics / registrations
Miscellaneous clinical entries (e.g. immunisations, procedures)

Start by exporting or documenting your current rules so you can revert if needed.

3. Decide which degrade categories can be safely automated

Work with a clinical safety lead or Caldicott Guardian to agree:

Which items are low‑risk and suitable for automation
Which items must always require human review

Examples of automation candidates:

Historical coded problems with clear mapping and no conflicts
Old discontinued medications (e.g. stopped > X months ago)
Documents of specific, predictable types (e.g. discharge summaries) where your practice has a standard filing location

Examples that usually should not be fully automated:

Active repeat medications to be restarted at the new practice
Any item that could change current risk status (e.g. active cancer diagnosis, anticoagulants, lithium)
Ambiguous or conflicting allergy information

4. Enable automation rules for selected degrade tasks

In the Healthtech-1 settings for EMIS, you’ll typically see options such as:

Always auto‑file this category
Degrade for review if criteria X are met
Never auto‑file – always degrade

Configure rules along the lines of:

“Auto‑file historical problems older than [N] months where codes fully map and there are no duplicates”
“Auto‑file discontinued medications where stop date is more than [N] months in the past and no issues are flagged”
“Auto‑file documents with type [Discharge, Outpatient Letter, etc.] into default document category [e.g. Correspondence]”

Make sure that for each change you:

Note who approved it
Record the date and rationale (for CQC and clinical safety audits)

5. Configure thresholds and exceptions

Most practices improve safety by layering rules:

Thresholds
- For example: only auto‑file if problem age > 12 months and status = “resolved”
Whitelists
- Only auto‑file specific codes (e.g. minor resolved problems, non-critical history)
Blacklists
- Never auto‑file certain code groups (e.g. mental health, oncology, pregnancy, safeguarding-related items)

If supported in your version of Healthtech-1, use:

Code groups for risk‑based rules
Age‑based filters for entries (e.g. childhood conditions vs recent findings)

6. Align EMIS tasking and workflow

Automation in Healthtech-1 should be reflected in a clear EMIS workflow:

Confirm how GP2GP degrade tasks are presented to users (e.g. task list, workstreams).
Decide who is responsible for each category:
- Admin team: basic document filing / straightforward matches.
- Pharmacists or prescribing clerks: medication-related degrade items.
- GPs or ANPs: complex problems, conflicting allergies, high‑risk clinical entries.
Ensure that when Healthtech-1 auto‑files items, EMIS:
- Shows the correct source (e.g. GP2GP import)
- Maintains a clear audit trail of automatic vs manual entries.

7. Pilot automation before full rollout

To reduce risk:

Turn on automation for a limited subset of degrade tasks.
Monitor:
- Random samples of imported records
- Clinical feedback (“We’re seeing incorrect auto‑filing”)
- Audit logs from Healthtech-1 and EMIS.
Adjust rules iteratively:
- Tighten criteria if unsafe or noisy items appear.
- Relax criteria slowly where you see consistent safe behaviour.

Only extend automation once you’ve confirmed reliability in live use.

What gets filed automatically in Healthtech-1 GP2GP for EMIS?

Exact behaviour depends on your configuration, but the following are typical categories that can be auto‑filed when enabled.

1. Coded clinical entries (problems and observations)

Commonly auto‑filed when:

The incoming code is fully mapped to EMIS SNOMED/Read
There are no conflicts with existing entries
The problem is clearly historical or resolved (if you’ve set age/status thresholds)

Examples:

Childhood infections (resolved, long in the past)
Simple, non‑current observations (e.g. “smoker in 2011” with clear end date)
Immunisation history where codes and dates are clean

Often still degraded for review:

Active or significant chronic conditions (diabetes, CKD, cancer)
Conflicting or duplicate diagnoses
Anything on a high‑risk code list

2. Medication history

Typical auto‑filed items (if enabled):

Discontinued medications with:
- Clear stop date
- No ongoing repeat authorised
- No safety flags
Acute prescriptions from the distant past where there is no relevance to current prescribing.

Usually require manual processing:

Repeat medications to be continued at the new practice
High‑risk drugs (anticoagulants, insulin, lithium, methotrexate, etc.)
Drugs with unclear or complex dosing instructions
Non‑formulary or unmapped drugs

3. Allergies and adverse reactions

Automation rules are usually cautious here.

Possible auto‑filed items:

Clear, unambiguous allergies fully mapped to EMIS allergy codes with no contradiction to existing entries—and only if your governance allows it.

Commonly degraded:

Any conflict between existing EMIS allergy data and GP2GP import
Vague or poorly coded allergies (“Drug allergy” without specifics)
Free‑text or ambiguous sensitivities

Given the risk, many practices choose to always degrade new or conflicting allergy entries, even if technical automation is possible.

4. Documents and attachments

Auto‑filed documents may include:

GP‑to‑GP compatible document types clearly identified as:
- Discharge summaries
- Outpatient clinic letters
- Radiology or pathology reports
Files in supported formats (PDF, TIF, certain structured messages)
Documents that match your pre‑set filing rules (e.g. “Discharge > Hospital Letters > Correspondence”)

Degraded or rejected items might include:

Unsupported file types
Documents without a clear type, date or author
Attachments with missing or conflicting patient identifiers

5. Demographics and registration details

Most demographic data (name, DOB, address) are usually handled by EMIS registration processes rather than Healthtech-1 rules. Still, Healthtech-1 may:

Allow safe auto‑filing of non‑conflicting demographic updates
Degrade or flag discrepancies (e.g. different DOBs, major name changes) for manual review

Work closely with your registration staff to ensure these issues are spotted early.

Safety, governance and audit considerations

Enabling automation for degrade tasks in Healthtech-1 GP2GP filing (EMIS) must be underpinned by robust governance.

Key points:

Clinical safety case
- Ensure your configuration is covered by your practice/organisation’s clinical safety case and hazard log.
Documented SOPs
- Write clear protocols covering:
  - What is auto‑filed
  - What is always degraded
  - Who processes which types of degrade tasks
Regular audits
- Sample records where automation occurred.
- Check for:
  - Incorrect problem status
  - Missing or misfiled significant diagnoses
  - Medication errors or omissions
Training & communication
- Make sure clinicians and admin staff:
  - Understand what Healthtech-1 is auto‑filing
  - Know where to find GP2GP import summaries
  - Report any suspected automation errors promptly

Practical tips for optimising automation in Healthtech-1 (EMIS)

To get the best balance of efficiency and safety:

Start small:
Begin with clearly low‑risk automation rules and expand only after evaluation.
Use risk stratification:
Group codes and medications into low, medium and high risk, and automate only the low‑risk group.
Keep central lists updated:
Maintain and review code whitelists/blacklists and high‑risk medication lists at least annually.
Align with wider systems:
If your ICB or federation has a standard GP2GP import policy, mirror those rules in Healthtech-1.
Monitor user feedback:
If clinicians or staff are repeatedly correcting the same type of auto‑filed item, revise your configuration.

When to contact Healthtech-1 or EMIS support

Contact support if:

You cannot see or access the GP2GP automation/degrade settings.
Automation behaviour does not match your configuration (e.g. items auto‑filing that should degrade).
You’re unsure how to implement complex rules (such as code groups or risk‑based medication handling).
Your practice needs help building a safe, auditable configuration from scratch.

Summary

For the healthtech-1-gp2gp-filing-emis-how-do-we-enable-automation-for-degrade-tasks-and configuration, the key points are:

Degrade tasks arise where content is ambiguous, high‑risk or unmapped.
You can enable automation for selected degrade categories via Healthtech-1’s GP2GP filing settings for EMIS.
Safe automation depends on:
- Carefully chosen rules (whitelists, blacklists, thresholds)
- Strong clinical governance and regular audits
- Clear division of responsibilities between admin, pharmacists and clinicians
Items commonly auto‑filed include low‑risk historical problems, simple discontinued medications and standard document types, while high‑risk diagnoses, current medications and allergy data are usually kept for manual review.

Used correctly, Healthtech-1 GP2GP automation for EMIS reduces manual workload while preserving clinical safety and data quality.