PRACTICE OPERATIONS
Current platform scopeFive clinics.
One operating system.
From the moment a patient books, every handoff stays on one thread. Patient services sees readiness. The care team inherits context. Billing receives completed work. Follow-up has an owner—and leadership can see what is stuck across every location.
5clinics connected
- North
- Downtown
- West
- East
- Specialty
PATIENT 0247One visit. Every handoff.Cardiology follow-up · Downtown
SHARED VISIT CONTEXT
- Schedule
- 09:00 · Ready
- Record
- Sources attached
- Owner
- Care team
- Next step
- Visible
TODAY'S THREADWork follows the patient
IN PROGRESS- ✓
PATIENT ACCESSBooking confirmedPatient services
DONE - ✓
CAREEncounter startedClinical team
ACTIVE - 03
DOCUMENTATIONNote ready for reviewClinician
REVIEW - 04
REVENUEInvoice preparedBilling team
READY - 05
FOLLOW-UPOutcome assignedCare coordinator
QUEUED
Same patient. Same source. One accountable next step.
REPLACE THE PATCHWORK
Every team sees its work.
The practice sees one system.
Front desk, care team, billing staff, administrators and practice leaders work from different views of the same patient and operating record—not separate tools that have to be reconciled later.
i“Current platform” means the software exists in MatariHealth today. MatariHealth remains in development; configured services, regional rollout and general availability vary.
ONE CONNECTED WORKDAY
The handoffs are where
systems come apart.
Choose a workflow to see how Matari keeps the patient, the work, and the accountable next step in the same operating context.
01 · PATIENT ACCESS
From request to a ready visit.
Booking requests, patient records, scheduling context, reminders and arrival status stay visible to the team running the day.
- 01Request received→
- 02Patient matched→
- 03Visit booked→
- 04Reminder tracked
One accountable thread. Each transition stays tied to the patient, practice, facility, role and source workflow.
SPECIALTY-AWARE CARE
Current platformOne operating system.
The right clinical shape for each specialty.
39
specialties and care disciplines across medicine, rehabilitation, diagnostics, procedural care and allied health.
A practice can operate as generalist, single-specialty or multi-specialty; enable the disciplines it provides; and give each clinician primary and secondary specialties, facility assignments and their own template defaults.
Cardiology
Chest symptoms and exertion, rhythm and syncope, cardiovascular risk, ECG, imaging and anticoagulation.
Physical Therapy
Systems review, tests and measures, impairment and function, diagnosis, goals, plan and response.
Family Medicine
Prevention, family and social context, and connected acute and chronic care.
Pediatrics and Adolescent Medicine
Growth, development, immunization, caregiver context and confidential adolescent history.
Psychiatry and Behavioral Health
Mental status and function, sleep, substance use, treatment response and safety.
Orthopedics and Sports Medicine
Anatomy and laterality, function, neurovascular status, range, strength, imaging and restrictions.
Dermatology
Lesion evolution, exposure and risk, morphology, distribution, photography and biopsy.
Nutrition and Dietetics
Diet pattern and access, clinical findings, goals, intervention and monitoring.
ONE SPECIALTY PER ENCOUNTER
Use the most specific clinical context available.
Matari resolves the encounter in a consistent order, then keeps the selected clinical structure stable for the life of that visit.
- 01Appointment specialtyWhen explicitly selected
- →02Provider primary specialtyWhen the visit has a provider
- →03Practice defaultThe governed fallback
Matching assessment and documentation templates are pinned by version. Later template changes do not silently reshape an encounter already in progress.
Current platform Curated specialty content is a reviewable baseline and still requires practice- and jurisdiction-specific validation.
Configured service Transcript-assisted assessment suggestions require the configured intelligence capability and clinician review before finalization.
EXAMPLE FIVE-CLINIC VIEW
See the work before
it becomes a surprise.
Synthetic operating data shaped like a realistic multi-location week. No patient data and no claimed customer results.
BOOKED VS COMPLETEDOne week by clinic
SYNTHETIC Booked Completed
OPEN WORKWhat needs an owner
38 ACTIONS- 9Due todayFOLLOW-UP
- 14Notes awaiting reviewDOCUMENTATION
- 8Patient replies unresolvedMESSAGING
- 6Billing exceptionsREVENUE
REVENUE FOLLOW-THROUGHDelivered work stays connected
USD · SYNTHETICCHARGES CAPTURED$139,700
INVOICES SUBMITTED$128,400
PAYMENTS POSTED$114,900
OPEN BALANCE$13,500
MULTI-LOCATION BY DESIGN
A clinic is a location.
The practice is the system.
Parent and child organizations, facilities, local defaults, clinician assignments and facility-scoped reporting let each clinic run its day without separating the operating record.
- ✓ Organization and facility ownership
- ✓ Location-specific schedules and defaults
- ✓ Role- and permission-based access
- ✓ Facility and clinician reporting filters
- ✓ Audited security-sensitive actions
ORGANIZATIONConnected care groupOne governed operating context
CAPABILITY STATUS
What exists now.
What still depends on rollout.
Built product surfaces stay separate from configured services and unfinished regional connectivity, so a discussion can begin with the actual practice environment.
Patients, booking and schedules
Patient creation, responsible contacts, booking requests, appointment status, clinician and room context.
Encounters and documentation
Encounter workspaces, clinical capture, templates, care plans, diagnostic workflows and finalized-record protection.
One patient-linked inbox
Consent-aware conversations, reminders, delivery state, unread work and masked contact display.
Billing, payments and inventory
Invoices, estimates, payment and refund workflows, inventory movements, reporting definitions and operational queues.
Organizations, facilities and access
Parent-child organizations, practice locations, facility defaults, staff roles, permissions and audited access.
Multi-specialty clinical workflows
Practice-enabled specialties, provider clinical profiles, encounter-level specialty resolution, and version-pinned assessment and documentation templates.
Payments, calendar and meetings
External payment, calendar, meeting and intelligence services are available only when their required providers are configured.
US and India clinical integrations
FHIR, SMART, HL7, C-CDA, ABDM and vendor-specific production adapters remain in development.
Regional delivery and video visits
India production messaging routes and video visits require unfinished adapters or rollout work.
A STAGED TRANSITION
Replace the patchwork
without hiding the seams.
Matari includes migration-job creation and tracking plus canonical synchronization foundations. Production connector coverage varies by region and vendor, and regional EHR and HMIS adapters remain in development.
- 01MapIdentify the systems, owners and records in scope.
- 02ValidateReview source data, permissions and workflow dependencies.
- 03StageTrack migration work without pretending every connector is ready.
- 04MovePlan cutover by practice, facility and supported capability.