AZMedAppz
Sign inSet up a practice
The whole clinic

Every module, and what it hands the next one.

333 apps run in clinics today, grouped by the eight jobs a practice does. Open a tab to see that job’s apps, the steps one of them takes you through, and which apps it reads from and hands to. The connections are read out of the code: an app is shown as connected because its service queries the other one’s tables.

An illustration of clinic apps for appointments, records, prescribing and billing, connected in one workspace

Front office — 7 apps live

The desk: who is here, who is waiting, and what happens when they are called.

Patient RegistryRegistration with duplicate prevention that runs before the save.
  1. Register in under a minute. Name, age, phone — the phone number warns about a likely duplicate before you save, not after.
  2. Find anyone from anywhere. The search at the top of every screen takes a name, a phone number or an MRN.
  3. Open the one record. Visits, notes, allergies and bills sit on a single page — the story of the patient, not a filing cabinet.
Live productPatient Registry — Registration — duplicate check runs before the save
Registration — duplicate check runs before the saveCaptured from the running demo clinic

What hands over to what

The busiest four, and the apps on either side of them. Every line here is a query one module makes against another’s tables — read out of the code, not drawn by hand.

286 of the 333 live apps query another app’s tables; the rest stand on their own. Nothing on this page is typed by hand — the lists come from the catalog and the connections from apps/web/src/site/app-graph.json, regenerated from the modules and held to them by a test.