Technology and delivery
Built for the realities of hospital environments
Designed to suit your infrastructure.
Medtasker is designed flexibly, so it can be deployed to fit your IT environment while supporting your teams and adapting to the way they already work.
Cloud or on-premise
Run Medtasker as a managed cloud service or deploy it within your own hospital-managed environment (on-premise or cloud).
WiFi and/or cellular
Medtasker can operate over WiFi only or support both WiFi and cellular connectivity, depending on your infrastructure requirements. The mobile apps switch seamlessly between available networks.
Hospital devices and/or BYOD
Can be deployed on staff or hospital-issued devices through your existing Mobile Device Management (MDM) environment, with desktop access for coordination and management teams.
Native and web browser
Medtasker apps run on Android and iOS devices, as well as in browsers on desktops or laptops. The apps are available in the Google and Apple stores, certified as compliant with their standards.
Secured to health standards.
Medtasker is built to the security standards Australian and New Zealand health services expect. From data storage and transmission to independent security testing, data sovereignty and robust security controls, we take the protection of your environment and information seriously.
Authentication and access
Role-based access through Active Directory ensures users only access what their role requires.
No data on devices
No patient data (including photos within the app) is stored on mobile devices or desktops.
Data sovereignty
Data held in-region across Australian and New Zealand deployments.
Audit
Actions within the system are captured as time-stamped, traceable records.
Information security
ISO/IEC 27001:2022 aligned practices.
Data security
Data is encrypted in transit and at rest.
Security testing
Regular independent application and penetration testing.
Privacy
Compliant with the Australian Privacy Principles and the New Zealand Privacy Act 2020 (plus HISO 10029:2015 for New Zealand deployments).
Delivered the way healthcare projects should be.
Every Medtasker implementation is led by a PRINCE2-certified project manager working alongside your team. With experience delivering projects across Australian and New Zealand health services, we understand the technical, operational and change management challenges involved in successful deployments.
Staged rollout
Start with one module, prove the value, then expand at your own pace.
Structured, repeatable framework
Each rollout runs through a consistent set of stages, templates and checkpoints, the same way every time.
Tailored to your hospital
Configuration, integrations and training are shaped around your clinical and operational priorities.
Train-the-trainer approach
Role-based training, enabling your internal team to train end users, with onsite or remote support provided before go-live.
Built for expansion
Once live, hospitals extend Medtasker into new teams and use cases through a repeatable expansion-planning approach.
Support you can rely on.
Once you’re live, ongoing support continues as part of your Medtasker service.
Structured, escalation-based support
Your IT help desk manages day-to-day requests, with Medtasker’s Australasia-based team providing specialist escalation support 24/7/365. All activity is logged and tracked.
Built in resilience
Medtasker is designed to keep running. Inbuilt microservice management, message retries and high availability failover deliver a system that our customers rate as their most reliable.
Proactive monitoring and maintenance
Medtasker continuously monitors server and network performance, reporting exceptions to our team. We’re often the first to let you know if your environment has issues.
Regular upgrades
Server software upgrades run at agreed times to minimise disruption for your users. When using a high availability environment, there is usually zero downtime as we cycle through upgrading each server.
Disaster recovery readiness
Backups, failover capabilities and documented recovery procedures support continuity of service during major outages or incidents.
Designed to integrate
Interoperability built in,
not bolted on
Medtasker is designed to be interoperable from the ground up. As one part of your broader technology ecosystem, it’s built to work alongside the systems your teams rely on.
HL7 and FHIR are core to Medtasker’s architecture, enabling secure connections with clinical and operational systems that turn information into structured, routable workflows.
Support when you need it
Need support now?
General support
Contact your health service’s IT team during business hours.
Urgent support
Contact your IT team at any time. They have direct access to the Medtasker support team for immediate assistance.
IT staff
Log a support request directly via our support portal: https://support.medtasker.com
Frequently asked questions
How does Medtasker integrate with our existing systems?
Medtasker is designed to integrate with existing hospital systems using secure APIs and healthcare interoperability standards. It can connect with systems such as patient administration systems, electronic medical records and Emergency Department platforms to provide relevant patient, location and clinical context. Integrations help reduce manual data entry and support automated workflows across the health service.
Where is Medtasker hosted, and does our data stay in our region?
Medtasker supports in-region hosting across Australian and New Zealand deployments. It can be delivered as a managed cloud service or deployed within hospital-managed environments where required. Data remains hosted within the relevant region to support data sovereignty and healthcare governance requirements.
What security standards and controls does Medtasker meet?
Medtasker follows ISO/IEC 27001:2022 information security practices and complies with applicable privacy requirements, including the Australian Privacy Principles and New Zealand Privacy Act 2020. Access is controlled through role-based permissions, data is encrypted in transit and at rest, and no patient data is stored on user devices. Medtasker also undergoes regular, independent application and penetration testing.
Does Medtasker support single sign-on and BYOD?
Medtasker integrates with your existing Active Directory for single sign-on and role-based access. The mobile apps support both hospital-issued and personal devices and can operate within your existing Mobile Device Management environment. No patient data is stored on user devices.
What does a typical Medtasker deployment look like?
Medtasker implementations are typically staged, starting with priority workflows or teams before expanding across the organisation. Timelines depend on the scope, technology requirements and change management approach of each health service. Medtasker’s delivery and support teams are based in Australasia, with no offshoring.
What does ongoing support and product development look like?
Medtasker partners with health services to provide ongoing support and continuous product improvement. Day-to-day support is managed through your existing help desk, with escalation support available from our Australia-based team 24/7/365. Product development is guided by customer feedback, user groups and evolving healthcare needs, with regular releases to enhance the platform over time.
Find out how Medtasker can help your hospital
The fastest way to see how Medtasker can support your teams is a conversation.
Tell us what you’d like to improve and we’ll show you how Medtasker works for hospitals like yours.