HCE — Historia Clinica Electronica
HCE is the hospital information system for public healthcare institutions. It manages the complete patient journey — from arrival through discharge — with AI-assisted clinical decision support built into every workflow.
What HCE does
HCE unifies the operational reality of a public hospital into a single platform:
- Patient intake — registration, emergency triage, and appointment scheduling
- Clinical encounters — emergency consultations, outpatient visits, inpatient care
- Diagnostics — laboratory orders and results, radiology and imaging, AI-assisted analysis
- Surgery — scheduling, operating room coordination, anesthesia, post-op
- Pharmacy and supply — prescriptions, dispensing, inventory, blood bank
- Records and reporting — digital clinical records and regulatory reporting
Who HCE is for
HCE is purpose-built for public healthcare institutions. If you are a private clinic or hospital group, see Clinora instead.
| Institution profile | Fit |
|---|---|
| National / regional / district public hospital | ✓ Primary target |
| Public specialty center (maternity, oncology, trauma) | ✓ |
| Ministry of Health / public health network | ✓ |
| Private clinic or hospital group | → Clinora |
| Small private practice | → Clinora |
What makes HCE different
- Government-ready by design — regulatory reporting, national ID identification, official diagnostic coding, and language localization built-in
- AI embedded, not bolted on — clinical decision support appears as buttons inside the consultation, not as a separate tool
- Privacy-first AI — default pipelines run on-premise; external AI providers are gated and auditable
- Full audit trail — every clinical action is logged with actor, context, and severity
- Operational, not just clinical — SIGSA reporting, pharmacy logistics, surgery scheduling, blood bank, and more, in one system
How to use these docs
This public documentation covers what HCE does and how to operate it as a user. It does not cover implementation details (internal architecture, data schemas, deployment runbooks, integration internals, or threat model). Those materials are provided to licensed customers under the support agreement — contact your SISMAUS account manager for access.
- Capabilities — the full feature map
- Patient Journey — how a patient moves through HCE
- AI Clinical Support — what AI does, how it stays private
- Compliance — audit, access control, regulatory alignment
- Licensed Documentation — how to access the full technical docs
Need implementation detail?
Technical architecture, data models, deployment runbooks, and integration internals are covered in our licensed documentation portal, available to customers under a support contract and to partners under NDA. Contact your account manager or open a support ticket to request access.