Skip to content

Visits

A visit is the encounter: who was seen, where, by whom, and what was done. Claims are generated from visits, never typed by hand, so a claim can only ever say what its visit says.

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

ColumnWhat it shows
Visit #The visit number
PatientWho was seen
Admit DateWhen the encounter started
Discharge DateWhen it ended, or a dash
StatusWhere the visit is in its life
StatusWhat it means
NewArrived, not yet checked
ReadyReadiness passed; a claim can be generated
Billed (Primary)A claim went to the primary payer
Billed (Secondary)A claim went to the secondary payer
Patient ResponsibilityWhat remains falls to the patient
CompletedNothing further is expected
CancelledThe encounter did not happen, or was withdrawn

Above the list, three figures count the whole client rather than the page you have scrolled to: Total, Unbilled and Cancelled. Unbilled is the one to watch - a visit that is New or Ready and has no claim behind it yet. Clicking it filters the list to exactly those, which is the shortest path from “are we leaving money on the table” to the visits responsible. The filter rail also narrows by Status.

Two tabs, Overview and Claims.

A visit page on its Overview tab, showing the Visit, Admission and Care Team cards

CardFields
VisitPatient, Patient Class, Reason, Admit Date, Discharge Date, Imported, Updated
AdmissionAdmission Type, Admission Source, Discharge Status, Hospital Service, Financial Class, Admit Reason
Care TeamAttending Provider, Admitting Provider, Referring Provider
ServicesThe service lines that become claim lines, each Captured, Billed or Voided

Patient Class is one of Inpatient, Outpatient, Emergency, Preadmit, Recurring, Obstetrics or Unknown.

The Claims tab lists what has already been generated from this visit.

Readiness is a live verdict rather than a status you set. The control beside the visit title counts the checks that are failing, and opening it names each one, why a failing check fails, and where to go and fix it.

A visit readiness verdict reading 2 of 6 failing, listing each check with the two failures explained

A visit that has moved past readiness - one that is already billed, or has a claim - reads Not applicable, because nothing will check it again.

ActionWhat it doesWhen it is offeredWhen it is offered but greyed
Check ReadinessRuns the readiness checksBefore the visit has a verdictWhile a check is running
Generate ClaimBuilds a claim from the visitOn the Claims cardUntil readiness passes, with the tooltip listing what is unmet
Add ServiceAdds a service lineOn an active visit-
EditOpens the visit for changesAlways-
Cancel VisitWithdraws the encounterWhile not already cancelled-
Restore VisitReverses a cancellationOn a cancelled visit-
View HistoryShows what changed and whenAlways-
DeleteRemoves the visitAlways-

Regenerating rebuilds from the visit, so hand-edited claim fields are overwritten with what the visit says. ClaimPod asks before doing that.

  • Not applicable - readiness no longer applies to this visit.
  • Couldn’t generate the claim appears inline with a Retry, rather than as a toast that scrolls away.
  • The visit no longer exists if it was deleted while you were away.
  • Empty - a client with no visits says so. Visits usually arrive through imports rather than typing.
  • Blocked - without the visits module the screen is not in the sidebar, and a saved link to it says the module is not part of your plan.

Related: Patients · Providers · Generate a Claim from a Visit · The Claim Loop