Skip to content

Patients

The registry for the selected client, and the record every visit, claim and payment traces back to.

The Patients list showing MRN, name, primary insurance, last visit and balance for each patient

User only, when the client is licensed for patients. Administrators and Managers have no access to patient data by design, which Roles and Access explains.

ColumnWhat it shows
MRNThe medical record number, and the identity the registry is keyed on
PatientName
SexAs recorded
Primary insuranceThe coverage claims will bill first
Last visitWhen they were last seen
OpenHow many claims are open for them
BalanceUnpaid claim balances owed by payers
Email, Marital status, City, CreatedAvailable from the column menu, hidden by default

The list filters and searches, and rows can be selected for a bulk Export or Delete.

A patient page: demographics above the Insurances and Visits cards, with Claims, Transactions and Statements below them

No tabs. Demographics sit at the top, with the MRN beside the name, then six cards.

Field
First Name, Middle Name, Last NameName as it will appear on a claim
Date of Birth, Gender, Marital StatusDemographics payers check
SSNMasked, showing only the last four digits
EmailContact
Medical Record NumberThe registry key
CardWhat it holds
InsurancesCoverage in the order it bills: Primary, Secondary, Tertiary
Billing RestrictionsEvery reason this account must not be billed - QMB, deceased, bankruptcy, payment plan or do not bill - with its reason, where it came from and its window. Rows read Proposed when an ERA remark raised them and nobody has confirmed them yet, Active while they stand, Scheduled before they start and Ended afterwards. A Proposed row holds statements just as an Active one does
VisitsEvery encounter for this patient
ClaimsEvery claim tracing back to them
TransactionsThe ledger for this patient, with a running total
StatementsEvery statement generated for this patient, with its stage, amount due, status and a download of the document. A row opens the statement

The Statements card on a patient page: one held statement and the Generate Statement button

Patient data usually arrives through imports rather than typing, but any field can be corrected in place when the source was wrong.

ActionWhat it doesWhen it is offered
Add InsuranceAdds a coverage to the patientOn the Insurances card
Add RestrictionRecords a reason not to bill this patient, with the date it takes effect and, if known, the date it endsOn the Billing Restrictions card
Generate StatementBills this patient now, outside the cycle, from the balance on the ledgerOn the Statements card. Greyed when the patient has no balance to bill, or the account carries a credit, and the tooltip says which
ExportDownloads the selected patientsOnce rows are selected
DeleteRemoves the selected patientsOnce rows are selected

Each insurance row can be edited, deleted, or shown with its history. Each restriction row can be shown with its history; a Proposed row can be confirmed, which records that you agree with the ERA and changes nothing else; and any row that has not ended can be ended, which asks End Billing Restriction? with an optional reason, closes the window today and keeps the row as history. Nothing deletes a restriction.

  • Empty - a client with no patients says so.
  • This patient isn’t in this client if you follow a link scoped elsewhere.
  • No statements for this patient on the Statements card.
  • No billing restrictions on this account on the Billing Restrictions card.
  • This patient already has an open restriction of this type when adding a second one of a kind that still stands; end the first before adding another.
  • Blocked - without the patients module the screen is not in the sidebar, and a saved link to it says the module is not part of your plan.

Related: Visits · Insurance Plans · Claims · Statements · The Claim Loop