Patient and identity
Registration, identifiers, preferences, consent and a longitudinal administrative timeline.
Capability architecture
Every clinic capability has a place, purpose and status.
AFIYORA is organized into eight connected product suites and three operating levels. This gives patient, clinical, operational, financial and trust concerns enough visibility without fragmenting the clinic journey.
CAPABILITY HIERARCHY01Growth & patient access4 connected capabilities02Clinical care4 connected capabilities03Care coordination4 connected capabilities04Clinic operations4 connected capabilities05Revenue & commerce4 connected capabilities06Workforce & enterprise4 connected capabilities07Intelligence & automation4 connected capabilities08Platform & trust4 connected capabilities
Eight connected suitesA complete clinic product direction
Role-aware designContext follows responsibility
Three operating levelsOperate, automate and assist
Status on every capabilityAvailable scope separated from roadmap
ONE OPERATING PICTURE
Great clinic software starts with the work between people.
The capability architecture follows real clinic handoffs—from scheduling and care to stock, payment, follow-up and management review.
Capability register
Eight suites. One connected clinic direction.
Only Inventory Operations is currently marked Available Now. All other capabilities remain Coming Soon, Roadmap, Research Concept or Optional Integration until verified for commercial use.
Growth & patient access
From first interest to a prepared arrival.
Demand, identity, capacity and communication stay connected so the clinic can prepare for the person—not just the appointment slot.
Coming soon
Scheduling, resources and waitlist
Provider, room, device and service availability with cancellation recovery.
Digital intake and consent
Mobile forms, document collection, versioned consent and reviewable evidence.
Engagement and growth journeys
Consent-aware reminders, recalls, messaging, lead follow-up and self-service.
Clinical care
Specialty-aware context inside the encounter.
Planned clinical capabilities protect authorship and judgment while reducing friction around documentation, orders and plans.
Clinical workspace
Encounters, notes, problems, plans, documents and controlled amendments.
Specialty packs
Versioned templates, diagrams, outcomes, protocols and specialty-specific journeys.
Orders and results
Laboratory, diagnostics and imaging workflows with acknowledgement controls.
Medication and prescribing
Legally reviewed medication reconciliation, prescribing and dispensing pathways.
Care coordination
Move every clinical handoff to accountable closure.
Referrals, results, tasks and follow-up keep a visible owner, due time, source and completion evidence.
Referral closure
Inbound and outbound referral triage, acceptance, missing information and outcome.
Results acknowledgement
Routing, abnormal-result escalation, review and patient-notification evidence.
Tasks and handover
Assignment, delegation, service levels, escalation and multidisciplinary handover.
External continuity
Approved telehealth, document and information-exchange pathways.
Clinic operations
Run the physical clinic with one operating picture.
People, rooms, stock, equipment and unfinished work become visible at the level where teams can act.
Inventory Operations
Batch, expiry, FEFO, kits, treatments, reusable assets and traceability.
Procurement and suppliers
Purchase requests, approvals, receipt, replenishment and supplier performance.
Rooms and resources
Clinic locations, rooms, devices and shared-resource readiness.
Operational workflows
Defined work queues, service levels, exceptions and approval paths.
Revenue & commerce
Keep commercial work connected to delivered services.
Pricing, payment and payer workflows retain the operational context needed for review and reconciliation.
Billing and estimates
Approved services, estimates, invoices, adjustments and account balances.
Payments and reconciliation
Receipts, refunds, settlement and exception-led reconciliation.
Claims and authorisation
Eligibility, approvals, claim validation, remittance and denial paths by market.
Pricing, packages and memberships
Controlled price lists, packages, discounts and organization agreements.
Workforce & enterprise
Scale standards without erasing local control.
Teams, credentials, branches, catalogues and policies remain visible at both enterprise and clinic level.
Workforce readiness
Roles, credentials, training, rosters, tasks and structured responsibility transfer.
Enterprise hierarchy
Organizations, branches, departments, locations and local operating scope.
Shared and local control
Enterprise catalogues, templates and policies with approved branch variation.
Branch intelligence
Consistent performance definitions with branch comparison and drill-through.
Intelligence & automation
Turn connected work into guided action.
Insight, automation and agent assistance are organized as governed services—not detached AI experiments.
Reports and intelligence
Role-specific metrics, defined calculations, freshness context and exception views.
Workflow automation
Rules, triggers, routing, service levels, approval and attributable execution.
Governed Agentic AI
Scoped assistants that prepare actions for human review, with monitoring and audit.
Role-based mobile experiences
Planned patient, doctor and staff access matched to responsibility.
Platform & trust
Make control part of the shared foundation.
Identity, configuration, integration operations, reliability and AI governance support every product suite.
Identity, permission and audit
Planned tenant boundaries, role scope, provenance and reviewable access.
APIs and interoperability
Approved FHIR, HL7, DICOM and provider integrations with verified scope.
Platform administration
Tenants, plans, entitlements, support access and service visibility.
Configuration and reliability
Versioned forms, rules and catalogues with recovery and operational monitoring.
THREE OPERATING LEVELS
Features become more useful when responsibility stays clear.
AFIYORA separates connected operational work, rules-based automation and governed AI assistance so clinics can adopt each level deliberately.
Explore the operating modelPRODUCT CLARITYRegulated functionality requires separate review.
Insurance, pharmacy, diagnostics, telehealth, interoperability, clinical AI and other regulated capabilities depend on implementation, provider capability, licensing and the applicable country. AFIYORA does not present configuration readiness as regulatory approval.
Ready for a clearer view?
Build a requirements map around your clinic.
Tell us your clinic type, branches, roles and priority workflows. We will separate available scope from planned capabilities before proposing a solution.