EMIS Web integration
EMIS Web triage integration — booking and SOAP write-back.
- EMIS Partner API: Appointments + Consultations
- OAuth 2.0 + mTLS, scoped least-privilege tokens
- Real-time slot booking by urgency band
- SOAP write-back with TriageNix audit identifier
- EMIS Partner Test Environment for sandbox validation
What it is
Who it's for
- GP practices on EMIS Web
- PCNs and federations consolidating access on EMIS
- OOH and same-day hubs using EMIS as primary record
- ICBs commissioning EMIS-aligned digital front doors
How it works
TriageNix queries real-time appointment availability scoped to the practice's diary.
Patient is booked into an appropriate slot based on AI-assessed urgency and clinician availability.
Consultation note (S, O, A, P) posted to the patient record with triage summary and red-flag assessment.
Every write is identifiable and reversible; full audit log exportable for CQC / IG.
FAQ
Which EMIS APIs do you use?
EMIS Partner API (Appointments + Consultations) over OAuth 2.0 with mTLS, plus GP Connect for read-only record access where the practice is enabled.
Do you write back consultation notes?
Yes — structured SOAP notes including the AI triage summary, red-flag assessment and recommended pathway. Every write is stamped with a TriageNix identifier for audit.
Is a sandbox available?
Yes. We use the EMIS Partner Test Environment with synthetic patient data, so your clinical safety and IT teams can validate end-to-end before live credentials are requested.
What are realistic timelines?
Typical EMIS Web write-back: 6–10 weeks from kickoff, covering EMIS Partner Programme onboarding, API provisioning, UAT with practice staff and CSO sign-off.
What about TPP SystmOne?
We integrate with both. SystmOne uses SystmConnect FHIR APIs with NRL alignment — equivalent timeline and equivalent write-back guarantees.
Run the EMIS sandbox with your team
We'll provision a TriageNix sandbox tenant with the EMIS Partner Test Environment so your IT and clinical leads can validate flows in days, not months.