Skip to main content
AnyVet
Back to docs

Inpatient Care

Admit a Patient from OPD

How to convert an outpatient case into an inpatient admission with room, dates, and initial orders.

Section: Inpatient Care
Updated: 2026-03-09
Tags: ipd, admit, opd, reservation

Admit a Patient from OPD

In AnyVet Smart, admission is not a separate disconnected system. It runs as a Medical Admit flow linked to the outpatient chart. Once admission is confirmed, the chart continues in IPD mode with bed assignment, initial orders, and flowsheet context attached.

How Admission Starts

The admission modal can open in two common ways:

  • from OPD, where the patient and medical record already exist
  • from the IPD area, where the user begins from patient selection

If the patient and record are already known, the flow can skip select-patient and jump directly to admit-details.

Medical Admit Steps

The modal is structured as:

  • select-patient
  • admit-details
  • initial-order
  • summary
  • checkout

For a new admission, the first four steps are the main ones.

Step 1. Select the patient

This step is required when the admission starts without OPD context.

Typical cases:

  • admission starts directly from IPD
  • the user needs to search the customer and pet first

Step 2. Enter admit details

This is the core bed-booking step.

Main fields

  • start date
  • start time
  • end date
  • end time
  • room
  • ward type
  • chief complaint / comment

Ward type to reservation type mapping

The UI ward type maps internally to:

  • ipd -> ReservationType.IPD
  • icu -> ReservationType.ICU
  • iso -> ReservationType.ISOLATION

How room selection works

The system proposes rooms from current ward and room data. Availability depends on ward type, species context, and current room occupancy.

Handle Room Conflicts

If the selected room is already at capacity or conflicts with another reservation, RoomConflictDialog may appear.

Practical response order

  1. Confirm whether the same room is really necessary.
  2. Re-select another room if possible.
  3. Use forced admission only as an exception.

Warning: Forced admission affects actual ward safety and occupancy control. Do not use it casually for convenience.

Step 3. Review initial orders

The initial-order step is where the OPD plan is reviewed before inpatient continuation.

Items that can flow forward automatically

  • non-voided items
  • items linked to branch service or branch item

What to review

  • whether the order is still needed at admission start
  • whether an OPD-only completed treatment is being duplicated
  • whether quantity and total still make sense

Treat this step as an operational cleanup step, not just a confirmation screen.

Step 4. Review the summary

Before admission is confirmed, review:

  • patient context
  • admission period
  • selected room
  • order or service summary

Selecting Confirm Admit completes the admission handoff.

What the System Does After Admission

After success, the system refreshes related data:

  • ward data
  • appointment and queue data
  • medical record caches

The user is then routed into the inpatient treatment context. In practice, admission changes the clinical mode, not just the bed assignment.

Checkout Context

The same modal family also supports checkout-related timing. That is why admission and discharge should be understood as different lifecycle moments for the same reservation entity.

Practical Tips

  • Clean up the OPD plan first so the initial-order step stays readable.
  • Choose the ward type before choosing the exact room.
  • After admission, confirm that IPD mode, flowsheet, and live tasks are all connected correctly.