Policies and procedures
NextHealth Flow
NextHealth Flow
Flow Quality is sold separately
NXH Flow policies and procedures gives each policy a named preparation, review and approval route. Start from category templates, record the relevant dates and collect signatures at each stage. Staff can request a change when the document no longer reflects practice, with a change log retained and approved policy PDFs available. The workflow supports policy ownership and revision, but it does not record staff acknowledgement that they have read a policy or replace the organisation’s responsibility for its content.
Keep policy ownership visible through every revision
-
Step 1
Prepare
Choose a template and prepare wording
-
Step 2
Review
Have the named reviewer sign
-
Step 3
Approve
Record approval and the relevant dates
-
Step 4
Revise
Review requests and policy history
What your team can do
- Start policy preparation from templates organised by relevant category.
- Assign named people to prepare, review and approve policies.
- Collect a signature at each policy approval stage.
- Record policy issue, review and expiry dates together.
- Accept staff change requests and retain a policy change log.
- Keep policy PDFs with their recorded approval information.
A policy needs accountable ownership as working practice changes.
Keep policy ownership visible through every revision
A policy becomes difficult to maintain when nobody can tell who prepared the current wording or approved the latest change. The facility needs an understandable history of decisions, especially when a practical change in the department means the document needs another review.
NXH Flow provides policy templates by category and a preparation, review and approval sequence signed by named people. Issue, review and expiry dates sit with the policy. Staff can request changes, and the change log preserves the revision history alongside policy PDFs and their approvals.
An approved policy is available to staff who hold permission to view facility policies, and those with the download permission can download the approved PDF. Flow does not push a policy to staff or record that they have read it. Use Document hub to store and sign licences, contracts and other facility documents.
Illustrative example: a policy revision
This example uses synthetic data.
A nurse submits a change request because a hand hygiene policy no longer matches ward practice. A user with the right permission approves the request. The preparer updates the wording, and the named reviewer and approver sign in turn. Flow records the new issue and review dates, adds an entry to the change log and keeps the approved PDF with its approvals.
Bring a policy that your team is actively reviewing to the demonstration. Follow the named stages, inspect the dates and submit a sample change request. Treat templates as a starting point for professional review. The workflow does not record whether every staff member has read a policy; plan that separate organisational process without assuming approval signatures provide evidence of staff acknowledgement.
Related NXH Flow modules
2 more modules
Common questions
-
Policies and procedures sits within Flow Quality, which is sold separately. Flow has no compulsory core package; choose the commercial modules your facility needs.
-
No. Staff acknowledgement that they have read a policy is not recorded. Preparation, review and approval signatures serve a different purpose in the policy workflow.
-
Yes. Staff can request a change when a policy needs revision. A change log helps the team follow the policy’s recorded history.
-
No. Templates provide a starting point. The facility’s named preparers, reviewers and approvers remain responsible for adapting, checking and approving the policy content.
Not answered here? Contact the team
