Nem is a practice management system with AI built into it rather than bolted beside it. This article is the map: what the parts are, which are included, which are separate, and what Nem deliberately is not.

The shape of it

Everything sits on one record. A patient's demographics, appointments, treatments, invoices, care plans, notes and documents live in one place, and every module reads that same data rather than syncing copies of it. That is why the voice agent can quote a real balance and the scribe can file into a real chart. They are not integrations with the clinic system, they are the clinic system.

An organization contains clinics. Staff hold membership in the clinics they work in and switch between them. Scoping between clinics is enforced when the query runs rather than assumed.

Included in every plan

The clinic system. Patients with a nine-tab detail page, a multi-provider week calendar, treatments against your own procedure catalogue, invoicing with A/R aging, twenty reports that all export, employee records with shifts, equipment and consumables, and a custom role builder across twelve modules where anything not positively granted is denied.

Read "How practice management works in Nem" for the detail, including the limits worth knowing before a demo.

A separate subscription

Care Management. The engine for the programs that pay for care between visits: Chronic Care Management, Principal Care Management, Advanced Primary Care Management, Transitional Care Management, Remote Physiologic Monitoring, Remote Therapeutic Monitoring and Behavioral Health Integration. Consent capture, care plans, time logging, stage gates and a month-end sweep that produces one reviewable line per patient per month.

It is priced on the patients you actually bill for rather than the patients you enrol. Read "How Care Management works in Nem".

Add-ons

The voice agent. Answers your clinic's phone, verifies the caller against the patient record before discussing anything about them, books and reschedules against live availability, and answers balance, insurance and treatment questions from your own data. Inbound calls only. Read "How the Nem voice agent works".

Nem Scribe. Records a visit, produces a transcript and a draft note in five sections, suggests codes checked against the real code catalogue, and files nothing until a clinician reviews and signs. Read "How the Nem clinical scribe works".

What Nem is not

This list matters more than the one above, because it is the part a demo will not tell you.

• Nem is not a certified electronic health record. No certified EHR capability, no e-prescribing, no prescription monitoring query, no electronic lab ordering or results, no quality measure reporting, no telehealth, no immunization records, no referral management and no fax.
• There is no patient portal. No patient can sign in. No self-scheduling, no online bill payment, no patient document upload, no patient messaging. Nem is staff-facing throughout.
• There is no claims submission and no real-time eligibility check. Nem produces a CMS-1500 worksheet as a CSV for your biller to work from.
• Patients are not notified by Nem. Appointment reminders reach your staff. They do not go to patients, by email or by text.
• Remote monitoring has no device integration. The billing engine is complete and correct, but a reading reaches Nem only when a staff member types it in, and a typed reading does not support a device-day claim.
• Reporting is per clinic. An organization with several locations cannot roll its reports up into a group view.
• There is no dental charting, periodontal charting or imaging.

Every line above was searched for by name in the code before it was written here. They are stated up front on purpose: a prospect who finds a gap after being told everything works has a reason to doubt the rest of the page.

Getting your data in, and out

CSV import covers nine kinds of record: patients, patient demographics, employees, doctors, procedures, procedure categories, assets, care conditions and care plans. A demographics export from Tebra can be imported without editing it first, and Tebra is currently the only incumbent system with a supported migration path.

On the way out, an administrator can request a full export of your organization's data, which runs in chunks and arrives as a zip with a manifest and an expiry. Nem can also produce a C-CDA summary of care document covering problems, medications, allergies, care team and goals.

Security, in one paragraph

Two-factor authentication using an authenticator app, with single-use backup codes, enforced centrally rather than page by page. Password history and policy. Session lock on inactivity. An audit log covering thirty-seven kinds of action. Role-based access where anything not granted is denied. Retention schedules with destruction certificates. A runtime guard that checks every query stays inside the right clinic. Nem runs on HIPAA-eligible cloud infrastructure, with a BAA signed with your clinic before any patient data is processed.

Where to go next

1. "How practice management works in Nem", for the day-to-day clinic system.
2. "How Care Management works in Nem", if you run chronic care programs or plan to.
3. "How the Nem voice agent works", if the phone is the problem you are trying to solve.
4. "How the Nem clinical scribe works", if documentation time is the problem instead.

Each of those articles ends with a section stating plainly what is not built. Read those sections first if you are evaluating Nem against another system.