Platform · Garnet Health · 2020

Policy & Procedure Management

Document control for a hospital, with a transactional checkout that makes concurrent editing impossible rather than merely discouraged.

How it works

What this shows

The loop is transactional. A document is held by one named person at a time, so the second writer is refused rather than silently merged.

01 · The problem

Policies lived on a file share. Two departments would edit the same document in the same week and the later save silently won. In a regulated environment, a policy nobody can prove the current version of is worse than no policy at all.
02 · What I decided

A locking convention would have been cheaper and would have failed the first time someone ignored it. I built a real transactional checkout: the document is held, the holder is named, and the write is refused rather than merged. Version history and concurrence routing came with it, because document control without an approval chain is just storage.
03 · The outcome

10,370 active documents under control, a retired third-party licence, and a version question that has a definitive answer.

Anatomy

What a surveyor, or a hiring panel, should hear.

01

A file share with concurrent edits and no authoritative version cannot answer a surveyor who asks which policy was in force on a given day.

02

Transactional checkout instead of a locking convention: refused writes over silent merges, with concurrence routing built into the lifecycle.

03

Document control, version history, and approval state live on hospital infrastructure. The third-party licence is gone.