Axional Health Suite does not require you to replace your clinical HIS — coexistence is proven, not promised.
Hospital Angloamericano runs Axional Health Suite alongside SAP and TrakCare/InterSystems. MútuaTerrassa runs the full ERP back-office alongside Dedalus. The integration boundary is explicit and stable: the clinical HIS owns the medical record; Axional owns the administrative and financial episode. Connected by HL7 v2.x and FHIR R4.
Clinical HIS coexistence, proven in production
Hospital Angloamericano: Axional Health Suite running alongside SAP (corporate ERP) and TrakCare/InterSystems (clinical HIS). MútuaTerrassa: Axional ERP running alongside Dedalus. No forced displacement — the clinical system the institution has built its workflows around stays in place.
HL7 v2.x and FHIR R4 at the integration boundary
ADT, ORM, DFT, MDM and SIU messages consumed from the clinical HIS at the moment the clinical event occurs. FHIR R4 resources — Patient, Encounter, Coverage, Account, Claim — over REST for the modern integration surface. The clinical episode drives the administrative episode in real time.
100% web, cloud-ready, deployable on-premise
No local installation on user devices. Cloud (AWS, Azure, GCP), private cloud or on-premise — the buyer's infrastructure policy, not a forced migration. The same platform supports a single-specialty clinic and an 80-plus hospital group without a rewrite or a different product tier.
ENS High · ISO 27001 · RGPD/LOPDGDD
High-level ENS controls for the public-hospital variant. ISO 27001 information security management aligned to the international standard. RGPD/LOPDGDD with granular access controls, full action audit trail and anonymisation for test environments.
The integration architecture in full.
Six surfaces — from the clinical boundary to the security posture — each engineered, not configured after the fact.
The integration boundary — where clinical ends and administrative begins
The clinical HIS owns the clinical record: diagnosis, treatment, medication administration, clinical decision support. Axional Health Suite owns the administrative and financial episode: admission, billing, physician fees, procurement, finance. The boundary is respected, not blurred. The clinical event drives the administrative event via HL7 or FHIR, in real time. Neither system reaches into the other's domain. The result: a clinical director works in the HIS they know; the finance director works in Axional; the data flows correctly between them without manual re-entry.
HL7 v2.x — the installed-base integration surface
ADT messages (A01 admission, A02 transfer, A03 discharge, A04 registration, A08 patient update), ORM order messages, DFT financial transaction messages, MDM document management messages and SIU scheduling messages — all consumed from the clinical HIS at the moment the clinical event occurs. The administrative episode reflects the clinical episode in lock-step. When a patient is admitted via the clinical system, the Axional Health Suite admission record is created automatically. When the patient is discharged, the billing cycle opens. No manual triggers, no nightly catch-up batch.
FHIR R4 — the modern integration surface
Patient, Encounter, Coverage, Account, Claim, ExplanationOfBenefit, Practitioner and MedicationRequest resources over REST. Bidirectional where the clinical system supports it — patient demographic updates flow back; coverage changes flow forward; encounter status synchronises both ways. The FHIR surface supports patient portals, physician portals, mobile applications and external analytics platforms through the same integration layer that connects the clinical HIS, without separate API configurations per consumer.
Payer portal integrations — named and in production
SITEDS (EsSalud Peru), SuSalud (Peru healthcare regulator), SEOGA (Sanitas Spain) and CASS (Caixa Andorrana de Seguretat Social, Andorra) in production. Private insurer portals — Adeslas, DKV, Asisa, Sanitas, Mutua Madrileña — connected for eligibility validation, authorisation status and policy data. Coverage validation occurs in real time at the moment of admission, not as a batch correction at billing time. Dispensing integrations with Pyxis and Kardex automated dispensing cabinets complete the medication circuit.
Architecture — 100% web, horizontally scalable, deployment-agnostic
No local installation on user devices — the full functional depth of the platform, from clinical billing to procurement approval to physician-fee settlement, runs in the browser. Server groups with load balancing for horizontal scalability. Replicated databases for vertical scale and high availability — automatic failover, continuous monitoring, replication. The same platform configuration supports a single-specialty clinic and an 80-plus hospital group: no rewrite, no different product tier, no separate licensing model. Deployment: cloud (AWS, Azure, GCP), private cloud, on-premise or hybrid. The buyer's infrastructure policy determines the deployment model, not the licensing contract.
Security and compliance posture
RGPD/LOPDGDD: granular access controls per role and per functional surface, full action audit trail (who acted, when, what changed, from which workstation), encryption at rest and in transit, anonymisation and pseudonymisation for test environments and analytics use cases, ARSULIPO rights management (access, rectification, suppression, limitation, portability, objection), cross-border data flow controls per the EU adequacy framework. ENS High level — Real Decreto 3/2010 as updated — for the public-hospital administrative variant. ISO 27001 information security management system aligned to the international standard. PDF/A with qualified electronic timestamp for long-term legal validity of clinical and administrative documents.
The coexistence question every CIO asks.
The first question a CIO asks when evaluating a new operational system is: what do I have to replace? In Axional Health Suite, the answer is: nothing you do not choose to replace. The clinical HIS the institution has built its clinical workflows around stays in place. The corporate ERP already integrated into group finance stays in place. Axional slots into the administrative and financial layer that those systems do not fully cover — the revenue cycle, physician compensation, hospital procurement, and the financial consolidation of a multi-entity group.
Hospital Angloamericano is the proof. SAP for group finance. TrakCare/InterSystems for clinical records. Axional Health Suite for the administrative-financial episode that connects them: admission, billing, physician fees, the digital patient file, the cashier workflow and the physician portal. Three systems, two integration points, zero middleware between them. When a patient is admitted via TrakCare, the Axional Health Suite admission record opens automatically via HL7. When the clinical episode closes, the billing cycle runs. Financial data flows to SAP via structured interfaces. The systems each own their domain; the seams between them are engineered, not improvised.
MútuaTerrassa follows the same architecture in the other direction. Dedalus owns the clinical record. Axional owns the full ERP back-office: procurement, finance, supply chain, asset management, and the administrative layer of every clinical episode. HL7 interfaces maintain coherence between the Dedalus clinical episode and the Axional administrative episode in real time. The division is clear: Dedalus owns the clinical record; Axional owns the administrative, financial and operational record. Neither system trespasses on the other's domain.