Enterprise DNA

Instead of RiskMan

RiskMan is asking you to migrate. Move to an incident system you own.

We build your version around your services, your forms and the rules you report under, bring your RiskMan incident and feedback registers across and run it for you. Your quality team keeps every incident, every complaint and every review.

RiskMan has no public price: RLDatix quotes each service privately, and now offers RiskMan customers a move to RiskMan Cloud or to DatixCloudIQ. Either way you are changing systems.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription charges for

A private quote for screens over ordinary records

RiskMan is sold on quote by RLDatix to mid-market and enterprise health providers, sized by your services, users and modules. Its own page now lists migration options: a hosted RiskMan Cloud, or DatixCloudIQ when the time is right for you. Before you sign either, look at what the quote pays for.

request_quote

A price you only see in a quote

There is no published price. Each service negotiates its own, and a new hospital, day surgery or module goes back into the quote.

sync_alt

A migration you did not ask for

RiskMan customers are offered a hosted move or a new platform. Either is a project, a new contract and retraining, paid for by you.

dynamic_form

Paying for the forms and screens

Much of what you rent is the reporting form, the menus and the report builder. The records underneath are ordinary: incidents, people affected, ratings, reviews, actions, complaints and risks.

timer

The clocks you still work out by hand

Right 10 working days, the duty of candour steps and HQSC Part A and B dates depend on how your site set up its forms. Quality staff often keep their own spreadsheet of what is due.

bar_chart

The reports someone has to build

Each committee report is a report built in the system, exported and tidied in a spreadsheet. A new question means a new report.

lock

Your safety history in a system you rent

Years of incidents, reviews and complaints sit in a system you pay for every year. Leaving means asking for exports and hoping they are complete.

Your own quality office

Start with the clocks your quality team chases every week

Clocks

Every deadline worked out for you, in working days

Each service runs on its own region: New Zealand complaints on the HDC Code of Rights, Right 10; Victorian serious events on the statutory duty of candour; New Zealand SAC 1 and 2 events on the HQSC Part A and Part B dates. Weekends, public holidays and the New Zealand Christmas break are skipped.

  • check Acknowledge in 5 working days, decide in 10, tell the person when more than 20 more are needed, and update them every month
  • check Apology, meeting arranged, meeting held and the final written report, each with its date
  • check HQSC Part A and Part B due dates from the day the event was reported
  • check The law shown first, then national policy, then your own rules

Incidents

From the report to a clean close

Log what the reporter says, then a manager rates it. Rating starts every clock that applies. Reviews, actions and outside reports hang off the same record, and nothing closes while something is owed.

  • check Severity 1 to 4, harm, the Australian sentinel events list and the HQSC Always Report and Review list
  • check RCA, London Protocol or case review with a lead and a due date
  • check Actions marked done only with the evidence
  • check Closing early needs a reason, and the reason is kept

Feedback

Complaints that never slip past the rule

Every complaint shows the step it is at and how many working days it has been open. Compliments and suggestions are kept beside them, and complaints link to the incident behind them.

  • check The acknowledgement letter drafted with the advocacy service named
  • check Complaints linked to the incident, with whether disclosure came first
  • check Working days to close a complaint, by service
  • check Nothing is sent: a person checks every letter

Governance

The committee pack in one question

Ask for this month's report and get incidents by service, every legal and policy timeframe met or missed, six-month trends, feedback, the highest risks and what needs a decision.

  • check A risk register scored likelihood by consequence, with review dates
  • check Open risks matched to the incidents that keep happening
  • check Late reporting by ward and incidents at night by category
  • check The HQSC Part A brief and the final written report drafted from the record

Make it yours

Design your own RiskMan replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from RiskMan. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your RiskMan replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your RiskMan data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from a fictional health group with a private hospital in Auckland, a day surgery in Melbourne and a community nursing team in Brisbane. Your quality team asks the question and checks the records behind the answer.

forum

Clinical Incidents for Claude Code

Connected to your own database

What needs my attention across our services today?

Progress update (at least monthly while open)

Ref
FB-303
Service
TW-AKL
Kind
law
Standing
15 days over
Rule
HDC Code of Rights, Right 10(4)

Duty of candour: apology given

Ref
INC-1004
Service
TW-MEL
Kind
law
Standing
5 days over
Rule
Health Services Act 1988 (Vic) Part 5A; Duty of Candour Guidelines

Complaint acknowledged in writing

Ref
FB-301
Service
TW-AKL
Kind
law
Standing
5 days over
Rule
HDC Code of Rights, Right 10(6)(a)

Decision made (justified, not justified, or more time)

Ref
FB-302
Service
TW-AKL
Kind
law
Standing
5 days over
Rule
HDC Code of Rights, Right 10(7)

Duty of candour: meeting arranged

Ref
INC-1004
Service
TW-MEL
Kind
law
Standing
1 days over
Rule
Health Services Act 1988 (Vic) Part 5A; Duty of Candour Guidelines

Open disclosure started

Ref
INC-1002
Service
TW-AKL
Kind
policy
Standing
50 days over
Rule
HDC Code of Rights, Right 6; HDC guidance on open disclosure

Open disclosure started

Ref
INC-1005
Service
TW-BNE
Kind
policy
Standing
13 days over
Rule
Australian Open Disclosure Framework; NSQHS Action 1.12

HQSC Part A brief sent

Ref
INC-1002
Service
TW-AKL
Kind
policy
Standing
9 days over
Rule
National Adverse Events Policy 2023 (HQSC)

Review started

Ref
INC-1002
Service
TW-AKL
Kind
house
Standing
45 days over
Rule
House rule: SAC or ISR 1 and 2, and sentinel events, get a formal r...

Risk reviewed: Opioid dosing errors after verbal handover

Ref
RSK-22
Service
TW-AKL
Kind
house
Standing
31 days over
Rule
House rule: the risk's own review cycle

Risk reviewed: Missed home visits when the roster changes

Ref
RSK-25
Service
TW-BNE
Kind
house
Standing
15 days over
Rule
House rule: the risk's own review cycle

Action done: Stop verbal dose handovers for controlled drugs; chart...

Ref
ACT-504
Service
TW-AKL
Kind
house
Standing
15 days over
Rule
House rule: the action's own due date

Review started

Ref
INC-1005
Service
TW-BNE
Kind
house
Standing
8 days over
Rule
House rule: SAC or ISR 1 and 2, and sentinel events, get a formal r...

Action done: Run the controlled drug double-check refresher for all...

Ref
ACT-507
Service
TW-AKL
Kind
house
Standing
8 days over
Rule
House rule: the action's own due date

Action done: Audit bed alarm use on Ward 3 nights for four weeks

Ref
ACT-503
Service
TW-AKL
Kind
house
Standing
4 days over
Rule
House rule: the action's own due date

Severity rated

Ref
INC-1006
Service
TW-AKL
Kind
house
Standing
3 days over
Rule
House rule: every incident rated by a manager

Duty of candour: meeting held

Ref
INC-1003
Service
TW-MEL
Kind
law
Standing
due 2026-10-29
Rule
Health Services Act 1988 (Vic) Part 5A; Duty of Candour Guidelines

Ask it anything

Questions answered from your incident records

These examples combine your own records across every service at once. They are not a claim that RiskMan cannot produce a similar report.

chat_bubble Which legal or policy deadlines did we miss or meet late this year, and by how many days?
chat_bubble How long does each service take to rate a new incident?
chat_bubble Which units report late, more than a day after the event?
chat_bubble Which categories are rising: the last two months against the four before?
chat_bubble Which complaints are linked to an incident, and was disclosure done before the complaint arrived?
chat_bubble Who owns the most overdue actions, and how old is the oldest?
chat_bubble Which open risks have had matching incidents in the last 90 days?
chat_bubble How many working days does each service take to close a complaint?
chat_bubble Which incidents with harm have no review, no action and no disclosure recorded?
chat_bubble What share of incidents happen at night, by service and category?

Switching

How to switch from RiskMan

A move usually involves exporting each service’s incident and feedback registers, mapping your fields, testing the imports, then running both systems side by side before you switch.

  1. 1

    Export the registers

    For each service, use RiskMan reports to export the incident register and feedback register. RiskMan reports save as CSV. If your account does not offer that export, use the format it allows, usually CSV or Excel, and check with RiskMan about your options. Keep each service’s exports separate so you can load its records into the matching service in the new system.

  2. 2

    Prepare each service

    Set up each service in the new system before importing its records. Work out which incident and feedback exports belong to each service, and keep them clearly separated. The free import covers the incident register and feedback register. Your own forms, investigation fields and risk register may need mapping, so note how your current setup uses those before you load records.

  3. 3

    Test, then load the records

    Use the import’s test run before loading records. Test the incident register and feedback register for each service separately, then review the results before running the actual imports. Once the test looks right, load those registers into their matching services. Imports are atomic, so one bad row stops the whole file, and repeated rows are skipped.

  4. 4

    Review results and run both

    Check what the test run reports, including any rows or fields it flags, and resolve mapping or data issues before relying on the imported records. Confirm the records you need are present in the new system. Then keep RiskMan and the new system running side by side for a short period, so your team can check that the new records and workflows meet its needs.

  5. 5

    Switch off RiskMan

    When your team is satisfied with the records and the new system is ready to use, make the new system your working record for incidents and feedback. Agree internally when staff should stop updating RiskMan, and keep access to it until you have confirmed the move is complete. Then arrange to switch off RiskMan under your existing agreement.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much history to bring across. Each site may use different forms, investigation fields and risk register setups, so the mapping needs to match your records. If you have Enterprise DNA install and run the system for you, Enterprise DNA does this migration work as part of the setup.

Not ready for a call?

Get your RiskMan switch plan by email

We will send you the step-by-step plan for moving your business off RiskMan, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Start with the free quality office or have your version built

Open source

Do it yourself

Free code

  1. 1 Clone the repo and run npm install, npm test and npm run demo.
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Save your RiskMan incident register and feedback register reports as CSV, one per service, and import them with a dry run first.
  4. 4 Add your services and next year's public holidays, then run /compliance and /attention.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your services, categories, rating scale and house timeframes built in
  • check A two-minute reporting form for ward staff, anonymous if you want it, writing straight into your records
  • check Your RiskMan incidents, feedback, investigation forms and risk register brought across and checked
  • check Your incident reports, letters and committee pack in your brand

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Access for your whole quality team with no charge per user, plus backups and restore checks
  • check Overdue clocks raised every morning and the committee pack drafted each month
  • check Timeframes kept current when a policy or the law changes
Book a call with Sam

Questions

Instead of RiskMan, answered

Does this replace everything RiskMan does? expand_more

The free version covers the quality office: incidents and ratings, open disclosure and the duty of candour, reviews, actions, outside reports, complaints and compliments, the risk register and the committee report. It has no staff reporting form, anonymous reporting or phone app. Reports are entered by the quality team, or we build your staff a two-minute form that writes into the same records.

Can we trust the Right 10, duty of candour and HQSC dates? expand_more

Each clock comes from a rule written down with its source: the HDC Code of Rights and HDC's timeframe fact sheet, the Victorian Health Services Act and its Duty of Candour Guidelines, and the HQSC National Adverse Events Policy 2023. Every timeframe is a setting your team can see and change when a rule changes. It is a records check, not legal advice.

What happens to the incidents and complaints already in RiskMan? expand_more

Your incident register and feedback register come across from RiskMan reports saved as spreadsheets, one service at a time, with a test run first. Open incidents get their clocks straight away. Each site sets up RiskMan differently, so mapping your own forms, investigation fields and risk register is part of what Enterprise DNA does.

We run services in New Zealand and Australia. Will it handle both? expand_more

Yes. Each service has its own region, its own public holidays and its own rules: Right 10 and HQSC in New Zealand, the duty of candour in Victoria, the sentinel events list and open disclosure in Australia. One register covers the whole group.

What do we pay Enterprise DNA? expand_more

The code is free. A version built and run for your services has one setup fee, then a retainer, with no charge per user or per service. Sam reviews your RiskMan setup, your forms and your committee reports before agreeing the scope.

Own the records behind every incident you learn from

Take 30 minutes with Sam to go through your RiskMan setup, the migration you are being offered and the timeframes you report under. We map your services and agree what your version needs before you change systems.

Book a 30-minute call with Sam Get the free version

Clinical Incidents for Claude Code is free and open source, published by Enterprise DNA.

Done paying for RiskMan?

Get your version built