Skip to main content

VINAH Manager

VINAH reporting that runs nightly, unattended.

VINAH Manager is our product for VINAH (Victorian Integrated Non-Admitted Health) reporting. It pulls from your patient administration system and clinical sources, validates against the data dictionary in the 2026-27 VINAH manual, queues the submission, then tracks the return. Your HIM team reviews a dashboard instead of preparing the file.

Built by Devinium in Melbourne. We've shipped database-first software since 2007.

Rather pick a time now? Book a 30-minute call.

What VINAH Manager does.

Three jobs the HIM team used to do by hand, on a schedule the service controls.

HL7 integration

Pulls from your PAS and clinical sources.

HL7 v2 message generation from the patient administration system, the electronic medical record, and the departmental clinical systems that hold the encounter. No manual extract, no spreadsheet stitch.

Live data dictionary

The data dictionary is live, not a snapshot.

Validation runs against the current VINAH data dictionary, not a quarterly export. When the rules update, validation updates with them. Field rules that used to break each period now surface the night the message fails, not a fortnight later.

Queue and audit

Tracks every submission and return.

Submissions queue overnight. Returns get tracked back to the source records with actor, timestamp, and purpose for every read and write. The HIM team reviews a dashboard instead of reconstructing what happened from logs.
A schematic of the VINAH Manager dashboard: submission queue with validation status against the live data dictionary, and return tracking back to source records. Drawn from the live product.

Why not the manual VINAH portal loop?

Hours of HIM time per period, validation drift each month and rejections landing a fortnight after the period closed.

Most Victorian public health services we sit down with are running VINAH the same way: a person in HIM or decision support stitches the submission together from spreadsheets, runs it through a validator, fixes what breaks, submits, waits for the return, fixes again. Three places this loop breaks:

  • Hours of HIM time, every reporting period. One person on the spreadsheet-and-validate loop instead of the work the service hired them to do. The work does not scale across a rural alliance feeding multiple member services through one HIM team.
  • Validation drift across data-dictionary updates. The state collection updates the data dictionary. The local validator does not, until someone notices the same fields breaking on the same returns each month. VINAH Manager validates against the live dictionary, not a snapshot.
  • Returns land a fortnight after the period closed. Data quality queries arrive after the staff who entered the source data have moved on to the next period. VINAH Manager catches the failure the night the message fails validation, while the source is still warm.

The pattern repeats across Victorian public health software wherever a state collection meets a manual extract. VINAH Manager is one shape of fix: built once for the non-admitted side, refined each time the data dictionary updates, deployed at Victorian public health services that wanted their HIM team off the loop. Where a service runs the same shape of problem on a different state collection (VEMD on the emergency-department side, on-call payment calculations, the executive view of throughput by ward), the database-first foundation underneath VINAH Manager is the same pattern adapted to the dataset.

The 2026-27 VINAH manual.

The Department of Health publishes a new VINAH manual for each financial year, and validation has to change with it.

The department publishes the VINAH manual for each financial year, along with the proposed changes for the year ahead, which take effect from 1 July. A new edition can add or change data elements, code sets, and business rules. A local validator written for last year's edition can keep passing records that the state collection now rejects, and the HIM team finds out when the returns come back.

The 2026-27 edition is the current one, and its rules have applied to submissions since 1 July 2026. The department lists each year's changes, and the proposals for the year after, on its annual changes page.

We update VINAH Manager's validation for each new edition, so your HIM team starts the financial year on the current rules. Read the 2026-27 VINAH manual on the Department of Health's site, or find the previous editions on its VINAH page.

Who VINAH Manager is for.

Victorian public health services running VINAH reporting. Single-tenant managed deployment.

Enterprise managed hosting

Victorian public health services running VINAH reporting.

Metropolitan hospitals, regional services, and rural health alliances feeding multiple member services through one HIM team. Single-tenant managed deployment on infrastructure your service controls: on-premise in your datacentre, in your tenancy of an Australian-region cloud, or in a hosted environment we manage to your security baseline. Health data does not leave your network.

Pricing scales with deployment scope.

Talk to us about a deployment

Recent work

Hours of HIM time per period, back.

A Victorian public health service was submitting VINAH reports manually through the state portal. Hours of HIM time every reporting period, compliance risk on every submission, and the same fields breaking on the same returns each month. They had tried checklists, dedicated admin staff, and a homegrown Access database that one person maintained. The manual step was the problem.

We deployed VINAH Manager. Pulls from clinical and admin systems run overnight, validation runs against the live data dictionary, the submission queues, and the return tracks back to the source records by morning. The hours of HIM time per period came back. Returns that used to land a fortnight after the period closed now get caught the night the data fails validation. Every read, write, and submission event lands in the audit trail with actor, timestamp, and purpose, so a data quality query from the department gets answered with a query, not a reconstruction.

VINAH Manager grew directly out of that engagement. Read the regulatory reporting automation case study for the full before-and-after.

How to start.

You can stop after any of these.

  1. A 30-minute call. Tell us how your service prepares VINAH today: the source systems, who runs the submission, and where the returns come back with errors.
  2. Whether it fits. We tell you whether VINAH Manager fits, or whether a smaller fix or our broader integration work would serve you better.
  3. A scoped deployment. Which systems it reads from, where it runs (on-premise, in your cloud tenancy, or hosted by us to your security baseline) and the price for that scope.

Book a free discovery call

Deploying VINAH Manager at your service.

VINAH Manager is a Devinium product for Victorian public health services done with the spreadsheet-and-validate loop. Talk to us about a deployment and we will tell you honestly whether VINAH Manager fits, or whether the broader integration work serves you better.