HospitalsAescia for Hospitals is an investigational Software as a Medical Device under the TGA Class IIa pathway. Not yet available for commercial supply.
ClinicsAescia for Clinics is a workflow and patient-preparation tool. It does not propose clinical decisions and is not a medical device.
The engine underneath both products.
Aescia is one engine with two doorways. The same composable pathway authoring, the same audit trail, the same patient-facing SMS layer, the same team. The regulated posture of the hospital product lifts the standard of the clinic product, and the workflow velocity of the clinic product keeps the hospital product honest about what a busy team will actually adopt.
Five step types. Every pathway, one authoring layer.
A structured patient signal. Photo, scale, questionnaire, vitals. Stored against the patient record and timestamped.
A clinician-authored rule that reads one or more Collect signals and decides whether to flag, escalate, or continue. Every rule is explainable.
A timed outbound SMS or notification. Prep nudges, follow-up questions, confirmation requests.
A PDF, video, or web card delivered at the right moment, in the right language, written by the clinical team.
A structured, consented, time-stamped record of every signal and decision, available to the patient record, the institution, and (under agreement) the sponsor.
- Encryptedin transit and at rest
- Per-tenantdata isolation
- In-regiondata residency
- MFA enforcedon all staff accounts
A pathway engine adapted per therapy area.
The engine already encodes drug-level rules (GLP-1, SGLT2, DOAC, warfarin). Any clinician-authored pathway extends it. The same primitives (structured collection, authored triage, SMS delivery, audit trail, structured export) are the primitives that underpin modern patient support programs, registries, and real-world evidence collection. We design for this extensibility; we do not name therapies we have not deployed.