The functions every providers of ambulatory health care company runs on. It has no schema of its own: companies here are mapped on the Healthcare practices schema, and what it does not cover is recorded as gaps.
© 2026 System Atlas · Built by MIOSA
Free to map your own company · Members $300 a yearHow automatable each primitive is, estimated from the 0 organizations mapped in public on the Healthcare practices schema, which this industry inherits: the share of those with the primitive that run it on software. Estimate from public data: the share of mapped organizations that run this on software. Not a recommendation.
| Primitive | Layer | Automation | Peers on software | Software parts named most |
|---|---|---|---|---|
Specialties and catchment Demand: winning customers | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Patient acquisition Demand: winning customers | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Front desk and patient coordinators Demand: winning customers | People | LowLayer only | 0 of 0 mapped; too few to read | — |
Fee schedules Demand: winning customers | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Treatment plans and cost estimates Demand: winning customers | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Consents and financial agreements Demand: winning customers | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Referrals Demand: winning customers | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Payer contracts Demand: winning customers | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Services and care pathways Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Appointment scheduling Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Procurement Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Suppliers and partners Supply: making or delivering the offer | People | LowLayer only | 0 of 0 mapped; too few to read | — |
Clinical care Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Clinical quality and outcomes Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Supplies and equipment Supply: making or delivering the offer | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Logistics and fulfilment Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Clinical records Supply: making or delivering the offer | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Orders and prescriptions Supply: making or delivering the offer | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Patient registration Customers: keeping them | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Patient communication Customers: keeping them | People | LowLayer only | 0 of 0 mapped; too few to read | — |
Care coordination Customers: keeping them | People | LowLayer only | 0 of 0 mapped; too few to read | — |
Patient demographics and cover Customers: keeping them | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Recall and continuity of care Customers: keeping them | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Intake and eligibility checks Customers: keeping them | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Patient billing Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Receivables Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Payments and payables Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Payroll Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Accounting and close Money: getting paid and paying | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Budgeting and forecasting Money: getting paid and paying | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Cash and treasury Money: getting paid and paying | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Coding and claims Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Prior authorisation Money: getting paid and paying | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Org structure People: who does the work | People | LowLayer only | 0 of 0 mapped; too few to read | — |
Hiring People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Onboarding and training People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Performance and pay People: who does the work | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Clinician schedules People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Policies and culture People: who does the work | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Provider credentialing People: who does the work | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Provider productivity People: who does the work | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Core system of record Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Communication tools Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Integrations Systems: tools and data | Software | HighLayer only | 0 of 0 mapped; too few to read | — |
Reporting and dashboards Systems: tools and data | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Data management Systems: tools and data | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Security and access Systems: tools and data | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Practice and provider licences Control: rules the company runs under | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Patient privacy and healthcare compliance Control: rules the company runs under | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Insurance and risk Control: rules the company runs under | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Legal and contracts administration Control: rules the company runs under | Data | MediumLayer only | 0 of 0 mapped; too few to read | — |
Infection control and patient safety Control: rules the company runs under | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Strategy and goals Direction: deciding where it goes | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Governance and decision rights Direction: deciding where it goes | Decisions | LowLayer only | 0 of 0 mapped; too few to read | — |
Management cadence Direction: deciding where it goes | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
Learning and improvement Direction: deciding where it goes | Process | MediumLayer only | 0 of 0 mapped; too few to read | — |
The rule, the same for every industry: with 5 or more organizations having the primitive, 50% or more of them on software is high, 20% or more medium, below that low. With fewer, the level rests on the primitive's layer alone and says "Layer only". Software parts are counted once per organization; a detected technology is named by its product. See the blueprint for which organizations run each.
Focused research on the organizations with the fewest mapped parts in providers of ambulatory health care; what it finds is public for everyone.