For ministries, public hospitals & authorities
Sovereign by construction, not by clause.
A data residency promise in a contract is a promise. An architecture with no vendor service in the data path is a property of the system. Pharos installs on your servers, inside your network, and continues to work if it never reaches us again.
The servers and the storage
Yours. The archive writes to storage you specify and control.
The administrative accounts
Yours, from first boot. Vendor access is granted, time-bound and logged, or not granted at all.
The data, in standard form
DICOM studies and structured results, readable by any conformant system without our software present.
The runbook
Install, update, back up, restore, and the known failure modes with the place each one is visible.
The case
Four properties a public imaging estate needs.
Rural sites keep working
District and rural units are exactly where connectivity is worst and where a lost day of scanning costs the most. Each site holds its own worklist, books its own walk-ins, and reconciles by itself when the link returns.
Images never leave the jurisdiction
There is no vendor cloud in the path. Pixels sit at the acquiring site or in the authority's datacentre, and remote reading reaches them there rather than copying them out.
No per-study meter
Licensing is per installation and per site, not per examination. Budgeting does not have to forecast volume, and a busy year is not a variation request.
Existing systems
It joins what you already run.
Public estates are never green field. The integration surface is standard, and the behaviour at the edges of it is deliberately conservative.
The hospital information system
Patient registration and orders arrive as HL7 version 2 and verified results go back the same way. Every message is answered, including refusals, and every message is retained verbatim for audit.
An archive you already own
Existing archives can be queried and retrieved from rather than migrated. Where a migration is genuinely wanted, it is a bulk transfer you schedule, not a precondition of going live.
Modalities of every vintage
Anything that can store DICOM and query a worklist will work. Machines that cannot are attached through an import path rather than excluded.
Refusal beats approximation
An unregistered sender is refused rather than guessed at, because a guess books one institution's patient into another's record. An unmapped order code is refused by name, not matched to the nearest-looking examination.
Procurement
What comes with the bid.
Evaluation panels ask the same questions in every jurisdiction. These are prepared rather than assembled after award.
| Document | Contents |
|---|---|
| DICOM conformance | Supported service classes, transfer syntaxes, application entity configuration, and the behaviour of each service under refusal. |
| HL7 interface specification | Message types accepted and emitted, segment-level mapping, acknowledgement behaviour, and the handling of unknown senders and unmapped codes. |
| Security & data handling | Authentication, roles and scoping, transport and storage protection, audit coverage, retention and disposal. |
| Deployment architecture | Server sizing per site and per estate, storage growth modelling, network requirements, and the offline behaviour of every component. |
| Operations runbook | Install, update, back up, restore, and a failure-mode table naming where the cause of each symptom is visible. |
| Training & handover | Technologist, front desk, radiologist and administrator tracks, with the administrative accounts transferred at handover. |
Governance
Separation that holds under audit.
Tenancy down to the register
An institution is a tenant. Its patients, examinations, staff, referrers and templates are invisible from another tenant — including a search of the patient register by national identifier.
Roles defined by the operator
Roles and the privileges attached to them are configured by the authority, not shipped as fixed vendor defaults that nobody can narrow.
Retention applied by the system
Retention periods and disposal are enforced by a scheduled process and recorded, rather than left as an instruction in a policy document.
Access recorded, refusals included
Sign-in, retrieval, export, sharing and administrative change are recorded against the account that performed them, and a refused action is recorded as a refusal.
Send us the specification. We will answer it line by line.
Requirements matrices, clarification rounds, site surveys and pilot deployments. Tell us the deadline and which authority governs the award.