Getting started

Understand dates, times and workflow status

Check when an event happened, recognize local display behavior, and handle date restrictions in encounters, observations, medication and payments.

Current source · source reviewed · 3 min read

Before you begin

Confirm the date, time and timezone set on the workstation or mobile device.
Use the event time from the actual clinical or financial event, following facility policy.

1. Check encounter start and status

Encounter creation accepts a future start only for Planned encounters. In Progress and On Hold encounters need a permitted current or past start. Encounter types and default values depend on deployment configuration.

2. Record discharge separately from completion

Discharge date and time cannot precede encounter start. Discharged and Completed are different workflow states: discharge records departure; completion closes the encounter and releases associated active location stays.

3. Check medication event time before saving

When recording a dose, Start Time and End Time begin at the current date and time. Select the past-time option when documenting an earlier administration. The form validates future time and whether end time precedes start time. An out-of-prescription-window warning is informational; it does not automatically stop saving.

4. Read observation effective times

The Observations list groups entries using each observation’s effective_datetime. Display dates and times are constructed with browser date methods and the browser local date context. When a time appears shifted, verify the workstation timezone before reporting a data error.

5. Use an allowed payment date

Payment Date cannot be in the future. Enter the actual payment date permitted by your facility’s financial policy and verify that the transaction is attached to the correct account.

Saved medication correction

The documented edit-administration dialog allows status and notes, while saved dose identity and start time are not editable in the ordinary dialog. Backend update fields and specialized infusion behavior should not be treated as permission to rewrite a saved clinical event through the UI.

Restart timing

The completed encounter restart window is deployment configured. The audited default is zero hours; a restart may therefore be rejected immediately. A local staff action does not override this policy.

Operational distinction

An appointment’s booked slot, an encounter’s start time, an observation’s effective time and the time a record was created are different events. Read the relevant field label before comparing them.

Troubleshooting

An otherwise valid date is rejected

Check the date rule for the specific workflow and the record’s status. Planned encounters, discharge dates, medication times and payment dates use different constraints.

An observation appears on an unexpected date

Check the observation’s effective time and the local timezone used by the viewing device. The source groups by local calendar date rather than a fixed universal display timezone.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.