ITKIT
Identity and government services · 02 / 20
OneService + OneGov
Government services and ministry modernisation
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Three offices. Three queues.
1
A national portal only digitises the front door if ministries still work on paper.
2
Every entity builds its own forms, workflows and payment code.
3
Infrastructure is sized and secured differently in every building.
Three forms · Three stamps · Three queues · One visit to the doctor
ITKIT · OneService + OneGov · Prototype screens, synthetic data
The problem
Our answer
Ask once. Track every step. Walk through the prototype.
One front door for citizens and businesses, and a repeatable method to modernise each ministry behind it: its applications, data, integrations, infrastructure and operations.
How it works · 1 of 7
Life events
One request. Three offices.
With OneService, Hala starts one journey. The hospital has already told us about the birth, so most details are filled in.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 2 of 7
Consent and payment
You see who gets your data. You pay once.
She sees exactly which office receives which record, and pays once. The Treasury passes each fee to the office that earned it.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 3 of 7
Signed certificate
Signed. Verifiable. Revocable.
The certificate is sealed by the Civil Registry. Anyone can check it, and a withdrawn document shows as revoked.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 4 of 7
Case work
People decide. The system advises.
Behind the app, Rami sees his queue by deadline. The system flags a cropped photo, but Rami makes the decision, and every step is logged.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 5 of 7
Service factory
New services without new code.
Ministries build new services with shared form, rule and workflow builders. Cases in progress keep the version they started with.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 6 of 7
OneGov blueprint
Every ministry. Its own data. Tested recovery.
OneGov gives each ministry a blueprint: what to reuse, what to integrate, what to build, and infrastructure whose recovery is tested, not assumed.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
How it works · 7 of 7
Service centre
Online or at the counter. Same rules.
People without a smartphone are served at the counter, with their own consent and the same record.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
How it works
What it includes
20 screens and workflows in the prototype
Life event: New baby
Parents
Pay fees
Applicants
Check a document
Anyone who receives a government document: banks, schools, employers, officials
Track my request
Applicants
Employee workspace: case queue
Case officers and supervisors
Service builder: form and catalogue entry
Service designers and service owners
OneGov ministry blueprint
Ministry CIOs and the OneGov programme architects
Service-centre desk: assisted application
Service-centre agents
ITKIT · OneService + OneGov · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in OneService + OneGov |
|---|---|
| WCAG 2.2 (W3C Recommendation, 5 Oct 2023) | SC 3.3.1, 3.3.3 and 3.3.7: errors and redundant entry |
| OpenID Connect Core 1.0 incorporating errata set 2 (15 Dec 2023) | Scopes and claims requested by the relying party |
| NIST SP 800-63C-4 (Jul 2025) | Relying party requests and checks assurance levels (xAL) |
| Regulation (EU) 2018/1724, Single Digital Gateway (benchmark) | Art. 14 once-only principle |
| BPMN 2.0.2 (OMG, Jan 2014) | Process constructs and model interchange |
| X-Road security architecture (NIIS, X-Road 7) | Mutual TLS between gateways, signed messages, message log |
| ETSI EN 319 102-1 V1.4.1 (2024) | Validation of advanced electronic signatures and seals; revocation (requirement PRD-009) |
| ISO/IEC 27001:2022 | Annex A 5.15 access control, 8.3 information access restriction, 8.15 logging |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
Built to standards
Connects to
What OneService + OneGov works with
OneID
ITKIT ESP
Ministry legacy systems via adapters
National payment gateway [to confirm]
ITKIT · OneService + OneGov · Prototype screens, synthetic data
Connects to
Safeguards
What OneService + OneGov will never do
No automatic centralisation of ministry databases and no cross-government data lake.
Existing Digital Syria initiatives are assessed before anything is replaced.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
Safeguards
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
OneService + OneGov at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
ITKIT · OneService + OneGov · Prototype screens, synthetic data
Durations are typical ranges, fixed per contract
Next step
Walk through the prototype and choose a pilot ministry.
OneService and OneGov. Ask once, track every step. Walk through the prototype with us and choose your pilot ministry.
1 · Demo
A guided session on the OneService + OneGov prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you