VEMD Editor
VEMD Editor: per-record corrections, no portal round-trip.
Devinium's record editor for the Victorian Emergency Minimum Dataset. It pulls from the patient administration system and emergency-department clinical sources, validates each record against the live data dictionary, and lets clinical-informatics staff fix what the state collection rejects without going back through the manual portal each time.
Built by Devinium in Melbourne. We've shipped database-first software since 2007.
What VEMD Editor does.
Three jobs the clinical-informatics team used to do in the portal, on the schedule the service controls.
HL7 integration
Pulls from your PAS and ED clinical sources.
Per-record edits
Each record is editable against the live dictionary.
Queue and audit
Tracks every submission and return.
Why not the manual VEMD portal loop for record corrections?
Per-record corrections through the state portal eat clinical-informatics time, and rejections come back after the encounter staff have moved on.
Most Victorian emergency departments we sit down with are running VEMD the same way: the submission goes out at the end of the period, the state collection comes back with rejections, and a clinical-informatics analyst opens the portal and fixes records one at a time, sometimes weeks after the encounter happened. Three places this loop breaks:
- Per-record corrections through the portal eat informatics time. One analyst, one record, one screen at a time. The work does not scale across a metropolitan emergency department running thousands of presentations a month, and the same field rules break on the same returns each period.
- Data quality queries arrive after the encounter staff have moved on. By the time the state collection returns a rejection, the triage nurse, the treating clinician, and the admitting officer are working the next period. Reconstructing what happened from the EMR slows every correction.
- Batch corrections that should run nightly run by hand each morning. When a data-dictionary update changes a field rule, the same correction has to land on hundreds of records. Doing that one record at a time is the wrong shape of work for a clinical-informatics team.
The pattern repeats across Victorian public health software wherever a state collection meets a manual portal. VEMD Editor is one shape of fix: built for the Victorian Emergency Minimum Dataset reporting tail, refined each time the data dictionary updates, deployed at a Victorian emergency department whose informatics team wanted the per-record portal grind off the calendar. Where a service runs the same shape of problem on a different state collection (VINAH on the non-admitted side, on-call payment calculations, the executive view of throughput by ward), the database-first foundation underneath VEMD Editor is the same pattern adapted to the dataset.
Who VEMD Editor is for.
Victorian public health services running VEMD reporting. Single-tenant managed deployment.
Tier 3: enterprise managed hosting
Victorian public health services running VEMD reporting.
Metropolitan emergency departments and regional services with their own clinical-informatics function. 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.
Talk to us about a deploymentRecent work
A week of clinical-informatics time per period, back.
A Victorian emergency department was correcting VEMD records through the state portal, one at a time, for weeks after each period closed. Hours of clinical-informatics time every reporting period, the same field rules breaking on the same returns each month, and rejections landing after the encounter staff had moved on to the next period. They had tried checklists, dedicated weekly portal sessions, and a homegrown tracker that one analyst maintained. The per-record portal step was the problem.
We deployed VEMD Editor. Pulls from the patient administration system and ED clinical sources run overnight. Validation runs against the live data dictionary, per-record edits and batch corrections happen in one screen, and the corrected records queue for resubmission by morning. The week of clinical-informatics time per period came back. Rejections that used to land a fortnight after the period closed now get caught the night the data fails validation. Actor, timestamp, and purpose are captured for every read, write, and submission event in the audit trail, so a data quality query from the department gets answered with a query against the trail, not an analyst reconstructing the period from logs.
VEMD Editor came out of the same body of regulatory-reporting work. Read the regulatory reporting automation case study for the full before-and-after.
Deploying VEMD Editor at your service.
VEMD Editor is a Devinium product for Victorian emergency departments done with the per-record portal grind. Talk to us about a deployment and we will tell you honestly whether VEMD Editor fits, or whether the broader integration work serves you better.