Skip to content

Support filing: recording, worklist & strictness

A support shift gets filed with MOHW by the clinic; the app just records the outcome, flags what's still unfiled, and decides how strict to be about it.

Updated View as Markdown
For humans

When someone is rostered outside their own branch — covering another clinic — the clinic is required to file that support arrangement with the Ministry of Health and Welfare (MOHW). The app never does the filing for you: what it does is record the outcome — who, which branch they’re covering, the date range, a reference number (filed under “Reference”) — and flag support shifts on the roster that still have no filing recorded.

Who records it

Branch ▸ Filings, entered by the covered person’s HOME branch manager, or by HQ. There’s no “mine” tab here — filing is the clinic’s obligation, not something an employee reports themselves, unlike leave or claims, so there’s no employee-facing version of this screen.

Only a branch HQ has granted. Who may cover which branch is decided by HQ on the person’s assignment (“Also covers”). When recording a filing, the supporting-branch picker lists only the branches HQ has granted that person; someone with no grant at all sees a note to ask HQ first. A filing never grants coverage — granting is HQ’s act, the filing is the home branch recording the outcome.

The unfiled worklist

The top of the page is the Needs filing worklist: shifts where one of your people is rostered at another branch and the covering period has no filing recorded yet. It reads “Nothing waiting to be filed.” once it’s clear. Recording starts from the Record filing button at the top of the page — a whole month’s worth of support rows can be filled in and saved in one request — and each row of the list carries its own File this, which starts the recording from that shift.

Recorded filings sit in the table below it — open one to view it, edit its dates or reference, attach the filing document, or delete the record entirely.

The dot on the roster

The scheduling board doesn’t re-decide whether a shift counts as unfiled support — it reads the same judgment this screen does. A support cell whose position requires filing, with no matching filing recorded for that period, carries a “Support not filed” dot; the dot clears itself the moment the filing is recorded, with nothing to double-check by hand.

Which positions need it

Decided by position, not by person. Company ▸ Settings ▸ Positions (under Organisation in the settings list) gives each position a “Requires MOHW support filing (醫事人員)” toggle: turned on, a position’s people show up in the unfiled worklist and get checked against recorded filings whenever they cover another branch. Left off, cross-branch cover for that position is outside this rule entirely.

What happens when nothing’s filed: three strictness levels

Company ▸ Settings ▸ Support filing (under Policy in the settings list) holds one org-wide setting for how strict the roster should be about an unfiled support shift:

  • Advisory — “Unfiled support shifts are flagged in the picker and on the roster, never blocked.”
  • Override — “The scheduler may proceed but must type a reason, and the shift stays flagged.”
  • Hard block — “The roster cannot create an unfiled support shift at all.”

The default is Advisory. It’s a single org-wide value, changeable only by org-wide scheduling admin — the same reach as the organisation template beside it, not something any one branch decides for itself.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close