These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Nursing Home / Assisted Living
- Features
- Charges and payments
Charges and payments
Review an encounter charge and a patient payment as distinct records.
OverviewDraft charges×
Nursing Home / Assisted Living · Charges and payments
New
Draft charges
Approval waits for the clinical coordinator
| Id | Encounter | Service description | Amount | Status | |
|---|---|---|---|---|---|
| IDD-970 | ENC-9246 | Draft chr-990 | 320 | Draft | |
| IDD-703 | ENC-7420 | Draft chr-415 | 880 | Draft | |
| IDD-215 | ENC-4286 | Draft chr-631 | 70 | Draft | |
| IDD-140 | ENC-3304 | Draft chr-377 | 620 | Draft | |
| IDD-322 | ENC-8723 | Draft chr-617 | 590 | Draft |
6 of 6 records
IDD-970Charges · CHR-17203
DraftEncounterENC-9246
Service descriptionDraft chr-990
Amount320
What you can do
Keep service and receipt clear
A charge belongs to an encounter. Clinical Coordinator enters the service description and amount, then uses its status to distinguish a draft, approved, invoiced or voided charge. A payment belongs to a patient and carries the received date, amount, reference and confirmation status. These records answer different questions: what service was charged for an episode, and what money was received from a patient.
The separation is useful in residential care where a coordinator may need to review a care episode before its service charge is approved. A patient payment can be confirmed without assuming which particular encounter it settles. Clinical Coordinator uses the receipt reference to investigate the payment against its source.
How the work is organized
- Encounter charge. The service description and amount remain attached to the episode that prompted the charge.
- Charge decision. Draft, approved, invoiced and voided states show where the charge sits in the team’s review.
- Patient receipt. The amount, received date and reference identify a payment, while pending, confirmed and refunded distinguish its current state.
What to agree during setup
Decide which services are entered as charges and how the description should read. Define who checks an amount before moving a draft charge to approved, and who records that an approved charge has been invoiced. If the financial system creates invoices, agree on how the local status is updated after its confirmation. A void should follow the team’s billing correction process so the reason remains understandable.
For payments, agree on the reference format used for matching an external receipt. Identify the person with payment entry access who confirms money received and handles refunds. The charge refers to an encounter while the payment refers directly to the patient; use the receipt reference during reconciliation. The reconciliation report should keep those populations visible separately.
Check the handoff on an actual case
After a completed encounter, the coordinator records a service charge as draft, reviews the description and amount, then approves it. The external billing process issues the invoice and the coordinator updates the local charge state. A payment later arrives for the patient. The coordinator reads the patient payment record and its reference against the receipt source. The team can see both records without assuming that the payment automatically clears that specific charge.
What your team sees
- Draft charges — Review episode-linked service descriptions and amounts before approval.
- Pending payments — Check received amounts and references before confirmation.
Follow the work through
Follow charge and payment review and encounter review.
What it keeps track of
Data model- Charges
- Service charges for encounters
- Payments
- Patient payments received
- Encounters
- Patient visits and care episodes
- Patients
- Patient identity and consent status
Who uses it
PermissionsSet up Nursing Home / Assisted Living your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.