05: Filling in forms

Purpose

Every form in CS Logbook follows the same layout and uses the same two tags, so you can tell at a glance what a form needs before it will save and what it will flag for follow-up.

The two tags

Next to a field's name you may see one of these:

• Needed to save: the form will not save until this field is filled in.
• Expected: you can leave it blank and the record still saves. An amber note under the field says what is missing, so it can be completed later.
• No tag: the field is optional.

A line at the top of each form repeats this. The tags describe how the form behaves. They are not a statement of what your state or the DEA requires; check the requirement that applies to your clinic.

The layout

• Each field's name sits above the field, on every screen size.
• On a tablet or desktop, short fields (dates, numbers, pickers) sit two to a row. Notes, reasons and other long fields take the full width.
• On a phone, every field takes the full width, one per row.
• A form opened in a pop-up window follows the width of that window.

The bar at the bottom

On full-page forms, the bar holding Cancel and the save button stays at the bottom of the screen while you scroll. It also shows how many tagged fields are still blank, for example "2 Needed-to-save fields blank · 1 Expected field blank".

That count only checks for blank fields. It does not check whether a value is valid, and it never stops you from pressing the save button; if something needed is missing, the form tells you when you save.