CareFlow is an early preview of a practice-operations platform for Australian general practice, hosted on premises at the clinic. Everything it does today runs on invented data. It is not a diagnostic system, not a prescribing system, and not a source of clinical truth.
We publish these limits deliberately. A preview that overstates its own readiness is worse than no preview, because a practice could make a clinical decision on the strength of a marketing claim.
No real patient information should be entered, and none is authorised. Clinical, privacy, safety, terminology, accessibility, backup and incident-response approvals must each be recorded against registered evidence before real-data mode is permitted.
Electronic prescribing exists only as a local conformance harness. It cannot transmit a prescription, cannot reach a pharmacy, and makes no claim of conformance with any Australian ePrescribing framework. There is no national pharmacy connectivity.
There is no regulatory approval, clinical safety case, independent penetration test or privacy impact assessment. Those are the next steps, not completed work.
Billing, claims, card and EFTPOS processing are deliberately disabled and cannot be enabled.
The value of the preview is that the safety boundaries are real and testable, not simulated. Each item below is enforced in code and covered by automated tests.
Multi-tenant scheduling with practitioner and room conflict protection, authorisation-required capacity overrides with immutable records, check-in, communication preferences and an append-only audit trail.
Clinician-authored record drafts that remain inactive until a prescriber with a verified second factor signs them, purpose-specific consent records, and prescription drafts that produce watermarked, non-dispensing previews only.
Uploaded documents are quarantined and malware-scanned before anyone can read them, and a scanner failure keeps them locked rather than admitting them. Documents are encrypted with per-document keys wrapped by an independently managed key.
Six roles with enforced boundaries: a nurse cannot sign a clinical record, reception cannot open the clinical workspace, and release approvals require named authorised roles rather than a single administrator.
Every role boundary is asserted, not assumed. Automated tests confirm that a nurse cannot sign a clinical record, that reception and audit roles cannot read clinical records, and that release approvals follow a role matrix instead of a single administrator permission.
Each status below changes only when there is evidence for the change, not when there is an intention to change it.
Why the status is public. Prospective users and reviewers need to know these limits before a demonstration, not after. Publishing them is the same principle as publishing a clinical safety case: the claim and its limits travel together.
The preview is demonstrated to interested practices and reviewers under a demonstration agreement, on synthetic data only. Access is granted per organisation.
Commercial discussion about future availability is welcome, but payment is not taken for clinical use before the approvals listed above exist. If that timeline does not suit your practice, we would rather say so now than take a deposit against a capability we cannot yet deliver safely.
Bring your clinical, privacy, security and intended-use requirements and we will show exactly where the system stops, who is accountable for each decision, and what remains outstanding.