The application is already in the ward. We audit what happens next.
Query Engine Core sits with the people who click through a live system — nurses, clerks, covering officers — and writes down where the software parts from the work.
How an audit actually starts
We do not begin with a feature list. We begin with a named ward, a named shift, and permission to watch ordinary work: searching for a patient, entering vitals, placing an order, printing a label, handing over.
Workarounds are treated as evidence. A photocopied fluid chart, a WhatsApp group for results, a shared login in a drawer — these tell us more about the application than a demonstration environment ever will.
“Live” often means the login screen works. It does not mean the discharge summary, the night printer, and the float nurse agree with each other.
What you can request
Scoping is a conversation, not a catalogue. Most first engagements are a ward workflow audit. Privacy, access, go-live readiness, and vendor assurance sit beside it when the setting needs them.
We work with hospitals, specialist centres, clinic groups, and the vendors who sell into them. Reports are written in English for operators in Malaysia. We are not a law firm and we do not sell software.
Ward workflow audit
Two to four weeks on site. We attend agreed shifts, including at least one night or weekend block. We sample admissions, administrations, and discharges against a protocol written before fieldwork starts.
You receive a plain-English report, a findings workshop with the people who run the wards, and a short list of changes ordered by clinical risk — not by vendor ticket volume.
Related work we take on
These sit beside the ward audit when a clinic, hospital, or vendor needs a narrower reading of the same application.
Health data privacy review
A review of how patient data actually leaves the application — exports, screenshots, shared inboxes, and vendor access — not only what the privacy notice claims.
Access and privilege audit
A role-by-role reading of the application: shared accounts, leftover locum logins, and privileges that outrank the job on the roster.
Go-live readiness review
An independent reading of whether the application, the training, and the paper fallback can survive the first seventy-two hours.
Vendor application assurance
A structured reading of a healthcare application you are buying or already running, written for the people who will live with it — not for the sales cycle.
From a medical director after a night observation
We had been told the nursing documentation module was complete. Query Engine Core spent two nights on Ward 3 and brought back a printer tray, a shared desktop password, and a discharge screen that cannot be finished with one hand. The report named shifts, not “adoption”. That is what we needed in order to change the roster and the vendor ticket in the same week.
Specialist centre, Johor Bahru — name withheld by agreementBring the application, the roster, and the floor
A scoping call is enough to see whether a ward audit, a privacy review, or a go-live note is the right first piece of work.