Secure handling of inpatient billing information starts with the right process.
Medical billing involves sensitive information. DEVZ keeps general enquiries separate from patient submissions, agrees a secure transfer method with each doctor and processes claims using its own billing software rather than remotely accessing practice systems.
Our operating approach
Business details only
The public form asks for professional contact details and a description of the service required. It is not a patient-document submission channel.
Agree a secure channel
Before sending patient-identifiable lists, doctors agree an appropriate transfer method with DEVZ and receive the relevant submission instructions.
Separate practice systems
DEVZ handles eligible inpatient billing using its own software; it does not ask to remotely log in to a practice's billing or patient-management software.
What happens to the claim payment?
Medicare and participating health funds make payments directly to the doctor's nominated bank account. DEVZ invoices its billing service fee separately. We do not collect, hold or pool the doctor's Medicare or health fund income.
Responsibilities and data accuracy
The treating practitioner remains responsible for clinical services and for authorising accurate billing information. Claim acceptance, eligibility and payment decisions remain subject to relevant Medicare and payer rules. DEVZ's billing administration and follow-up cannot guarantee payment of every claim.
About secure-billing technology
We use our own secure, Medicare- and ECLIPSE-compliant billing software for eligible claim processing. Any doctor-facing app, upload or notification workflow should only be used in accordance with its current approved onboarding instructions. We do not represent a TestFlight or development feature as a guaranteed production service.
Privacy and questions
Read the full Privacy Policy for our published privacy information. For questions about sending inpatient details securely, contact DEVZ without including patient identifiers.
Information on this page describes the billing workflow and precautions that users should follow. It does not claim independent security certification, a particular encryption standard or an audit outcome that has not been independently verified.