Document hub
NextHealth Flow
NextHealth Flow
Flow Documents is sold separately
NXH Flow document hub keeps facility documents, dates and signatures together. Store licences, contracts and other records with their type, issue date, expiry date and version history. Staff can sign documents, while outside parties use a link confirmed with a one-time code. Review and expiry reminders help the facility prepare its next action. Teams can find the record they need and check its history without piecing together copies held in separate folders or email conversations.
Find the document and understand its history
-
Step 1
Record
Add the document and dates
-
Step 2
Review
Check its version and review history
-
Step 3
Sign
Collect staff or outside signatures
-
Step 4
Follow up
Review reminders before the date passes
What your team can do
- Keep licences, contracts and facility documents in one hub.
- Record document types, issue dates and expiry dates together.
- Retain document versions and the history of revision reviews.
- Collect signatures from staff and authorised outside parties.
- Confirm outside signing links with a one-time code.
- Receive reminders before document reviews and expiries fall due.
The right document needs its dates and history together.
Find the document and understand its history
A licence renewal or contract review often begins with a simple question: which copy should we use? When documents sit across personal folders and email threads, finding the answer takes attention away from the review itself. The facility needs the document, its dates and its revision history together.
NXH Flow document hub holds regulatory, commercial and contract documents with version history and recorded reviews. Staff and outside parties can sign through the supported signing workflow. Reminders highlight approaching review and expiry dates, giving the team a practical starting point for organising the next action.
Access follows the permissions the facility grants for viewing and managing facility documents. The facility also sets document types and who receives expiry and review reminders. Each revision is kept as a version with its review history, so the team can see which copy is current. Staff sign inside Flow, and an outside signer opens a link and confirms it with a one-time code.
A signature recorded in Flow shows who signed, by which route and when. Whether that signature is legally accepted for a particular document or in a particular country is for the facility and its legal adviser to confirm. Preparing and approving policy wording is a different task. It sits in Policies and procedures, while this module stores and signs documents such as licences and contracts.
Illustrative example: a supplier agreement
This example uses synthetic data.
A facility manager adds a supplier agreement with its type, issue date and expiry date. A revised version is uploaded, so the record now holds both versions and the review history. The manager signs, and the supplier opens a signing link and confirms it with a one-time code. Flow reminds the team before the review and expiry dates.
Bring a representative licence and supplier agreement to your demonstration. Follow a revision, check the dates and review the outside signing step. If your priority also includes preparing and approving policies, compare the Quality and Documents pairing to see how the two selected modules support different parts of your work.
Related NXH Flow modules
2 more modules
Common questions
-
Document hub sits within Flow Documents, which is sold separately. Flow has no compulsory core package; choose the commercial modules your facility needs.
-
Yes. An outside signer can use a shared signing link confirmed with a one-time code. Staff signing is also supported within the document workflow.
-
Policy preparation, review and approval sit within Flow Quality. Choose Quality alongside Documents when you need both workflows, including through the optional pairing.
-
Bring a representative licence, contract and revision example. Review how the record stores dates, versions and signatures, then inspect the reminders relevant to your team.
Not answered here? Contact the team
