The administrative engine for hospital networks — engineered alongside the clinical record, not in competition with it.
Patient administration, revenue cycle and payer settlement, physician compensation, regulated procurement. Integrated with the clinical HIS via HL7 and FHIR; the back-office that turns each clinical episode into a coded encounter, a payer claim, a regulatory submission, an audited financial transaction. In production at Quirónsalud — Europe's largest private hospital group.
Not a clinical HIS — the administrative engine alongside one
The medical record belongs to the clinical HIS. Axional Healthcare is the back-office that runs everything downstream of it — admissions, billing, fees, procurement, regulatory submission. Built to integrate with the clinical record, not to replace it.
HL7 and FHIR as primary inputs
ADT, ORM, DFT, MDM messages consumed from the clinical HIS in real-time. FHIR R4 for the modern surface — Patient, Encounter, Coverage, Account, Claim resources mapped to the administrative metadata repository at the engine tier.
Multi-entity, multi-payer, multi-regime
Hospital groups, foundations, public-private mixes; private insurance, mutual societies, social security, state coverage — engineered at the entity and payer tiers, not bolted on as configuration. DRG-based billing, regulator-specific reporting.
In production at hospital scale
Europe's largest private hospital group in production for years across procurement, billing, multi-entity consolidation, physician compensation and public-health integration. The administrative engine that survives 50,000 employees and 58 hospitals.
Four modules, one administrative engine.
Each module is a packaged surface of the healthcare practice. Adopt one or several. The same metadata repository, the same audit trail, the same engineering team across all four.
Patient Administration
Demographics, admissions, transfers, episode tracking — and HL7 / FHIR ingestion from the clinical HIS. The administrative shadow of the medical record, kept in lock-step with billing and regulatory reporting. SNOMED, ICD-10 and IHE profiles consumed at the metadata tier.
Revenue Cycle & Payer Settlement
Eligibility verification, multi-payer coverage rules (private insurance · mutual societies · social security · state coverage), DRG-based billing, claims generation, payer settlement, patient invoicing with the complex multi-cover rules the Spanish and LATAM markets carry.
Physician Compensation
Honorarios médicos — fee schedules per specialty, per payer, per contract type. Performance-based pay-out reconciled against episode volume and quality measures. Multi-entity practitioner rosters; payroll-adjacent settlement; audit-grade evidence per fee paid.
Regulated Procurement & Compliance
Hospital procurement — pharmaceuticals, medical supplies, capital equipment — with lot / batch / expiry traceability at the engine. Multi-entity contracts and framework agreements. ENS Medium for the public-sector variant; GDPR / LOPDGDD enforced at the data tier.
What Axional Healthcare is not.
Healthcare software is a category that runs from the bedside to the finance department, and a single product cannot credibly own all of it. The clinical surface — the medical record itself, clinical decision support, medication administration, the order-entry workflow at the point of care — is the domain of the clinical HIS. Epic, Cerner, IBM Sentry and the national public-hospital information systems each own that surface in their respective markets. Axional Healthcare does not compete with them.
What Axional Healthcare does own is the administrative consequence of every clinical event the HIS records. The episode that becomes an encounter. The encounter that becomes a claim. The claim that becomes a payer settlement. The settlement that reconciles into a multi-entity general ledger and a regulatory submission. The physician who performed the procedure and is paid against a fee schedule with the right specialty, the right payer, the right contract. The supplier who delivered the consumable that was charged against that episode. This is the back-office of the hospital — engineered to a depth few clinical-HIS vendors carry, because it sits at the intersection of healthcare and complex- enterprise ERP, which is where Deister has lived since 1988.
How it integrates with the clinical record.
HL7 v2 for the installed base. FHIR R4 for the modern surface. IHE profiles for cross-enterprise document and identity flows. Real-time at the engine.
HL7 v2 messages consumed at runtime
ADT (admission, discharge, transfer), ORM (order entry), DFT (financial), MDM (document), SIU (scheduling) — consumed from the clinical HIS as the clinical event happens. The administrative episode reflects the clinical episode in lock-step.
FHIR R4 resources at the modern surface
Patient, Encounter, Coverage, Account, Claim, ExplanationOfBenefit, Practitioner — FHIR R4 resources mapped to the Axional metadata repository at the engine. Bidirectional where the clinical HIS supports it.
SNOMED CT and ICD-10 as bridge codes
Clinical codes carried with the episode and bridged to administrative concepts (billable encounter type, procedure for fee schedule, diagnosis for DRG grouper) at the metadata tier — not in middleware, not in batch reconciliation, not after the fact.
IHE profiles in production
PIX and PDQ for patient identifier cross-reference and demographics query across the hospital and the national-health surface. XDS for cross-enterprise document sharing. ATNA for the audit trail the regulator reads.
The depth of the practice — in production at hospital scale.
Quirónsalud is Europe's largest private hospital group : 50,000+ employees, 58 hospitals across 13 Spanish regions, €5.43B revenue in 2024. Axional Healthcare runs the administrative back-office of that operation in production — procurement of pharmaceuticals and consumables across all 58 hospitals, multi-entity consolidation of fifty-eight separate legal entities into one group view, patient billing with the full Spanish multi-payer landscape (private insurance · mutual societies · MUFACE / ISFAS state regimes · regional health authorities), physician compensation across thousands of specialists on contract, and regulatory submission against the calendar each Spanish autonomous community sets.
That depth was not bought ; it was earned over years of running healthcare in production. Axional Healthcare is that practice expressed as a packaged product — the four modules above being the four surfaces of the administrative engine that survives hospital-network scale.