Question 1

How does the EMIS Web integration work?

Accepted Answer

TriageNix connects to EMIS Web via the EMIS Partner API using OAuth 2.0 + mTLS. When a patient completes triage, TriageNix can:
1. Query real-time appointment slots from the practice diary.
2. Book the patient directly into an appropriate slot based on urgency and clinician availability.
3. Write a structured consultation note (SOAP format) back into the patient record, including the AI triage summary, red-flag assessment, and recommended pathway.
All writes are stamped with a TriageNix identifier so they are auditable in EMIS.

Question 2

How does the TPP SystmOne integration work?

Accepted Answer

TPP SystmOne integration uses SystmConnect FHIR APIs with NRL (National Record Locator) alignment. TriageNix can:
1. Read patient demographics and key record segments (allergies, medications, problems) to personalise triage questions.
2. Post triage outcomes as structured tasks into the SystmOne task list — e.g. "Review AI triage — possible UTI, moderate severity" — so the clinician sees it in their usual workflow.
3. Share the triage document via the GP Connect Send Document API so it appears in the patient's shared record.
Data is exchanged over TLS 1.3 with mutual authentication and audit logging on both sides.

Question 3

Are test / sandbox environments available?

Accepted Answer

Yes. Every integration ships with a pre-configured sandbox so your IT and clinical safety teams can validate before go-live:
• EMIS Web — EMIS Partner Test Environment (sandbox API endpoints + synthetic patient data).
• TPP SystmOne — TPP OpenTest environment with FHIR R4 sandbox and mock patient records.
• NHS login — NHS login Integration (INT) environment with mock OTP and synthetic NHS numbers.
• GP Connect — NHS Digital Opentest / Demonstrator environment with standard FHIR test fixtures.
We provide test credentials and sample data packs at kickoff so your team can run end-to-end triage-to-booking scenarios before touching production.

Question 4

What are the realistic timelines for each system?

Accepted Answer

Timelines vary by system, but typical durations from kickoff to production are:
• NHS login — 2–4 weeks (standard OIDC, mostly configuration and policy sign-off).
• GP Connect (read) — 4–6 weeks (FHIR mapping, endpoint registration, IGB integration).
• EMIS Web (write-back) — 6–10 weeks (partner programme onboarding, API provisioning, UAT with practice staff).
• TPP SystmOne (write-back) — 6–10 weeks (SystmConnect enrolment, task template setup, clinician training).
• FHIR UK Core standardisation — ongoing; initial profile alignment takes 2–3 weeks.
These run in parallel where possible. We always start with sandbox validation so live credentials are only requested once flows are proven.

Question 5

Where does patient data sit during integration?

Accepted Answer

TriageNix is architected as a data processor under UK GDPR. During integration:
• All patient-identifiable data is encrypted in transit (TLS 1.3) and at rest (AES-256).
• TriageNix does not persist full GP records — only the triage session, outcome, and a minimal reference ID needed to write back to the clinical system.
• Each integration uses scoped OAuth tokens with least-privilege access (e.g. appointments.write only, not full record read).
• Audit logs capture every API call, data access, and write-back event — exportable for CQC and IG evidence.
Our DPIA and DCB0129 hazard log are available for your IG team to review before contract.

Clinically governed triage platform for health systems, GP practices and private clinics — deploy in weeks.

Clinician-first

Compliance-ready

Enterprise-grade reporting

Plugs into the systems your clinicians already use.

A staged rollout, not a big bang.

Discovery & DPIA

Identity & single sign-on

FHIR UK Core + GP Connect (read)

EMIS Web / SystmOne write-back

Go-live & rollout

Integration FAQ

Plans

GP Practice

ICB / Multi-site

Private clinic

Investor & grant-ready

Implementation resources