Coordinate reception, practitioners, clinical records, billing, insurance, and reporting while keeping each role’s access appropriately separated.
Specialty workflows
Choose a specialty to see the clinical workspace and capabilities available for it.
The operating problem
Connected clinic workflow
Product capabilities
Role-based experience
Registration, appointments and check-in
No protected clinical notesClinical record, prescriptions and plan
Specialty and permission scopedOperations, capacity and reports
Controlled management viewServices, invoices and payments
No clinical notes requiredConfiguration, roles and audit
Governance permissions applyAppointments, invoices, approved documents
No internal clinical recordAnnual Early Access packages
Source prices are in USD and render in your selected currency through the current pricing system. Monthly equivalents are for comparison only; billing is annual.
Annual package price
$899.99 / year
Equivalent to $75/month
Best for: Independent clinics that need a controlled appointment-to-payment workflow.
Annual package price
$1,799.99 / year
Equivalent to $150/month
Best for: Growing clinics that need stronger clinical, operational and financial control.
Annual package price
$2,799.99 / year
Equivalent to $233.33/month
Best for: Clinic groups that need shared standards with branch-level accountability.
Annual package price
$3,599 / year
Equivalent to $300/month
Best for: Organizations that need clinic management inside a broader governed ERP rollout.
These are proposed Early Access packages, not active self-service subscriptions. The demo confirms product scope, timing, and implementation before commitment.
Complete comparison
“Add-on” means separate pricing; “Custom scope” means discovery and a quote before implementation.
| Capability | Clinic Launch | Clinic Growth | Clinic Network | Enterprise |
|---|---|---|---|---|
| Staff users | 8 | 25 | 60 | 100 |
| Branches | 1 | 3 | 10 | Enterprise scope |
| Practitioners | 5 | 20 | 60 | Enterprise scope |
| Active patient records | 5,000 | 25,000 | 100,000 | By agreement |
| Storage | 30 GB | 100 GB | 300 GB | 500 GB |
| Patient management | Included | Included | Included | Included |
| Appointments and queue | Included | Included | Included | Included |
| Encounter records | Basic | Included | Included | Included |
| Protected clinical notes | Not included | Included | Included | Included |
| Documents | Not included | Included | Included | Included |
| Billing and payments | Included | Included | Included | Included |
| Core Accounting | Not included | Included | Included | Included |
| Multi-branch dashboard | Not included | Not included | Included | Included |
| Developer/Mobile API | Not included | Not included | Included | Custom scope |
| Data exports | Not included | Not included | Included | Custom scope |
| Audit trail | Not included | Included | Included | Included |
| Priority support | Not included | Not included | Included | Included |
Swipe horizontally to see every package.
Implementation and onboarding
Configure clinic, branches, services, users, and permissions.
Import agreed patient and service data after a quality review.
Test booking, check-in, encounter, invoice, and payment with real roles.
Launch one branch or team first, then expand after adoption stabilizes.
Advanced data cleanup, custom integrations, and historical medical-record migration require separate scope and pricing. Enterprise implementation receives a custom quote.
Enterprise: custom implementation quote
Add-ons and expansion
| Add-on | Price or status |
|---|---|
| Extra user | Clinic Launch: +$42 / user / yearClinic Growth: +$36 / user / yearClinic Network: +$30 / user / yearEnterprise: +$30 / user / year |
| Extra storage | Clinic Launch: +$18 / 10 GB / yearClinic Growth: +$60 / 50 GB / yearClinic Network: +$96 / 100 GB / yearEnterprise: +$96 / 100 GB / year |
| Advanced data migration | From $500 one time. |
| Laboratory integration | Custom quote. |
| Insurance and payers | Policies, payer price lists, and authorization codes are available; external insurer integration is custom scope. |
| Pharmacy or inventory extension | Requires Inventory or a custom scope. |
| Clinical prescriptions | Supported in the clinic; external e-prescription integration is custom scope. |
| Communication channels | Email uses configured SMTP. SMS and WhatsApp require a supported provider adapter and may carry separate charges. |
| Patient Portal and online booking | Available as optional features and remain disabled until configured. |
Privacy and purpose-aware access
Each customer must confirm the privacy, medical-record retention, and regulatory obligations that apply in its country. This page does not claim legal compliance or medical certification.
Patient records are separated by purpose from customer and billing records.
Reception, practitioners, and finance receive different access based on responsibility.
Sensitive reads, edits, and exports can be audited within the agreed scope.
Standard invoices should contain services and amounts, not clinical diagnoses.
Amending a finalized clinical record requires a separate permission and creates an audit event.
Protected document downloads are permission controlled and activity logged.
Retention can be configured; each customer must approve the period appropriate to its country and policy.
The Patient Portal exposes only documents explicitly approved for patient access.
Questions before the demo
No. It is designed for outpatient clinics and clinic networks, focusing on appointments, visit workflow, billing, and operating control. Inpatient, emergency, operating-theatre, and specialist hospital functions are outside the published scope.
Yes. Starting with one branch or team is the recommended way to validate registration, booking, check-in, encounter, and invoice scenarios before expanding.
Yes. The patient record remains separate, while the payer may be the patient, a guardian, a company, or an insurer according to the configured workflow.
Yes. Clinic services map to Xfatora items and services, while Xfatora invoices and payments remain the financial source of truth.
Not by default. Clinical and financial access are separated, and a standard invoice should not expose a diagnosis or protected clinical note.
Yes. The product supports English and Arabic, including RTL-aware Arabic interfaces.
Yes for agreed core fields after column, quality, and authorization review. Advanced cleanup and historical medical-record migration require separate scoping.
No. Email uses the configured Xfatora SMTP service. SMS and WhatsApp require a supported provider adapter and may involve separate provider charges.
Insurance policies, payer price lists, authorization codes, and service packages are available. External insurer and laboratory integrations require custom scope.
Yes, within package capacity and the current Xfatora user and storage expansion rules. Moving to a higher tier or Enterprise scope may be clearer than adding fragmented capacity.
Billing is annual. The monthly equivalent is shown only for comparison and budgeting; it is not a separate monthly subscription.
Bring one real patient-to-payment scenario covering registration, appointment, check-in, encounter, services, invoice, and payment, plus required roles and a sample data structure without sensitive medical data.
Yes. It includes structured OD/OS examinations, visual acuity, IOP, refraction, optical prescriptions, trends, and multiple ophthalmology templates.
Yes. It includes an FDI odontogram, tooth and surface findings, procedures, phased treatment plans, consents, and attachments.
Yes. New outpatient specialties can use the shared record and configurable templates, while practitioners can work across specialties and branches subject to permissions and schedules.
No. Both are available optional features and remain disabled until an administrator configures access and approved patient-facing content.
Yes, according to package and scope. Scoped API keys and HMAC-signed Webhooks are available; enterprise integrations require review and an agreed scope.
Bring one scenario, the responsible roles, and a minimal non-sensitive data sample. We will show what is ready to evaluate, what needs custom scope, and what remains planned.
Real product interface
Actual Xfatora test-environment screens using synthetic QA data—not real patient information.