(opens in a new tab)Amazon Web Services
Australian cloud hosting on AWS infrastructure designed for high availability and scale as your clinic grows.
Trust & security
Confidence in the care.
Trust in the record.
Security, privacy and clinical-record safeguards for cosmetic, aesthetic and laser clinics in Australia.
Security & privacy
Protecting your clinic’s information.
Encryption, access controls and regular security testing help protect your clinic’s data and patient records.
Hosted in Australia
Your clinic’s DappleOS data is stored in Australia on AWS infrastructure, with encryption at rest and in transit.
(opens in a new tab)
(opens in a new tab)Cloudflare
Web application firewall (WAF) protection to help filter malicious web traffic.
Encrypted data
Your clinic’s data is encrypted at rest and in transit, protecting it while stored and as it moves between systems.
Access controls you manage
Set user and location permissions around each team member’s work. Multi-factor authentication adds another layer of protection. Trusted-device and clinic-IP controls depend on enabled access features and your clinic’s configuration.
Security audits and breach response
Security audits help us review how information is protected. We assess suspected data breaches and provide notifications where required.
Annual penetration testing
We carry out penetration testing every year to identify security weaknesses. Ask our team about the testing scope and available evidence.
Data ownership & service commitments
Clear commitments to your clinic.
Your data belongs to you. We protect your information and keep working to support and improve the software your clinic relies on.
Your data stays yours
Your clinic’s data belongs to you. Using DappleOS does not change that.
Your information is confidential
We treat your clinic’s information as confidential and take steps to protect it from unauthorised use or sharing.
Regular updates and improvements
Your clinic gets ongoing software updates, fixes and improvements, so DappleOS keeps getting better as you use it.
Built for reliable uptime
DappleOS runs on AWS infrastructure designed for high availability, helping keep your clinic connected throughout the working day.
Clinical notes
Clinical notes that lock automatically.
Create clinical notes with a defined editing window. The author can edit a note on the day it is created. At midnight in the clinic’s local time, the note becomes read-only.
This helps your clinic maintain the integrity of its clinical records. The original remains in place, with later corrections or additions recorded separately as traceable amendments.
Explore clinical notes and markings
Australian compliance support
Supporting your compliance responsibilities.
Your clinic’s responsibilities reach beyond software. See how DappleOS supports the records behind them, with direct links to the guidance.
These are workflow connections, not regulator approval or a guarantee of compliance.
For registered medical practitioners
Make the treatment record tell the whole story.
What’s expected
The Medical Board’s cosmetic-procedure guidance addresses assessment, consent and records detailed enough for another practitioner to understand the care provided.
How DappleOS helps
Bring clinical notes, treatment details and images together. Finalise a note when it is ready, preserve the original and record later corrections as traceable amendments.
How DappleOS supports your compliance work
- Document the assessment and clinical context
- Keep treatment details and images in the patient record
- Preserve dated notes and traceable amendments
Your clinic’s responsibilities
The treating practitioner remains responsible for the assessment, the accuracy of the record and the care delivered.
Guidance for your registered profession
Keep the consent conversation connected to care.
What’s expected
Ahpra and the National Boards publish profession-specific guidance on cosmetic procedures, including informed consent and permission for patient photographs and videos.
How DappleOS helps
Keep patient forms and consent alongside the treatment record, with clinical notes and images available in the same patient context.
How DappleOS supports your compliance work
- Keep patient information and forms together
- Document the consent discussion alongside care
- Record image permissions and intended use
Your clinic’s responsibilities
A signed form supports the record of consent. It does not replace the practitioner’s discussion with the patient. Apply the guidance for your profession.
Therapeutic goods and advertising
Keep the product details within reach.
What’s expected
The TGA publishes product recalls, alerts and corrections. It also regulates therapeutic-goods advertising, including public booking content that promotes prescription-only medicines.
How DappleOS helps
Keep recorded product, batch and expiry information with the treatment, so the team has that context when reviewing a product alert or recall.
How DappleOS supports your compliance work
- Record the product and batch used
- Keep expiry information with the treatment
- Review product details in the patient’s clinical record
Your clinic’s responsibilities
Your team reviews safety notices and public advertising. This is not automatic recall matching, product approval or a guarantee that booking or marketing copy is compliant.
For conversations with your insurer
Be ready to explain what happened, and when.
What’s expected
Insurer guidance emphasises clear clinical records and documented informed consent when responding to a complaint or claim. The requirements of an individual policy must be checked with that insurer.
How DappleOS helps
Use the clinical record, patient forms, images and traceable amendments to assemble the treatment history for your review. Preserve the original entry when recording a later correction.
How DappleOS supports your compliance work
- Retain the documented discussion and patient forms
- Bring treatment notes and images together for review
- Trace the original entry and later amendments
Your clinic’s responsibilities
Your insurer determines cover. DappleOS does not guarantee a claim outcome, satisfy every policy condition or imply insurer endorsement.
Responsible AI
Helpful assistance.
Human accountability.
AI can help with documentation. Your practitioner reviews the content and remains responsible for the clinical decisions.
Understand AI data handling
Review the processing, retention and model-training terms for the AI services your clinic uses. Our team can help you confirm the relevant providers and settings.
Professional review
AI-generated clinical content requires review and validation by a healthcare professional.
Clinical decisions stay with you
Practitioners review AI-generated clinical content and retain responsibility for diagnosis, prescribing and care.
Policies & evidence
Go straight
to the source.
A clear starting point for clinic owners, clinical leads and the people reviewing your software.
Detailed trust centre
Detailed security and infrastructure information, available to approved users.
Visit trust centreOpens in a new tabPrivacy Policy
Information handling, access, retention and breach response.
Read policyReport a security issue
Report a suspected vulnerability to our security team.
security@dappleos.comFAQs
How does DappleOS help with Australian compliance requirements?
DappleOS supports the documentation behind clinical care: patient forms and consent, clinical notes, treatment details, images and traceable amendments. This page maps those workflows to Medical Board, Ahpra and National Board guidance, TGA product-safety context and professional indemnity considerations. Practitioners remain responsible for care, consent and accurate records. Clinics must apply the rules relevant to their profession, services and state or territory.
Where is our clinic’s data hosted?
DappleOS is hosted on Amazon Web Services infrastructure in Australia. Platform hosting is distinct from processing by connected services and other providers: the Privacy Policy also describes overseas processing. If you have a strict residency requirement, ask for the relevant service and processor details before making a decision.
Which security measures does DappleOS publish?
The Privacy Policy describes encryption of health information at rest and in transit, authorised access controls, multi-factor authentication, security audits and breach assessment and notification where required. Use the security portal and a demo to review the scope and evidence for your specific requirements.
Can we control access from clinic devices?
Where enabled, trusted-device controls let your clinic apply access rules to recognised devices. Configured clinic IP addresses can also support device trust. These controls depend on your access features and settings, so review user permissions, device approval, blocked devices and session behaviour with our team before relying on a particular setup.
How can we confirm certification requirements?
This page does not claim independent certification. If your procurement process requires certification, a particular audit report or another formal assurance, confirm that requirement with DappleOS before proceeding.
Does using DappleOS satisfy my professional indemnity policy?
No software can determine your insurance cover. DappleOS’s documentation workflows can help you retain a clear treatment record and review its history. Confirm your insured activities, record-keeping obligations, notification requirements and any other conditions with your professional indemnity insurer. This page does not imply endorsement by an insurer.
How can we review AI processing, retention and model training?
Confirm the model-training, processing and retention terms for each AI service your clinic intends to use, including its providers and settings. Ask the DappleOS team for the relevant documentation before sending patient information. Practitioners review AI-generated clinical content and retain responsibility for clinical decisions.
Can a completed clinical note be changed without losing its history?
The author can edit a clinical note on the day it is created. At midnight in the clinic’s local time, it becomes read-only. The original record is preserved, with subsequent corrections or additions recorded separately as traceable amendments. The practitioner remains responsible for making an accurate record and explaining a later change.
Can we review backups, exports, retention and incident response?
Yes. Bring your required retention periods, export requirements, recovery expectations and incident-response questions to the DappleOS team. Review the Privacy Policy and current security portal first, then confirm the relevant arrangements and supporting documentation. Do not assume a particular recovery time, export format or deletion timetable without that review.
Ask DappleOS
Ask DappleOS about your clinic’s documentation and security questions, or book a demo to review specific requirements.
Amazon Web Services, AWS and the AWS logo are trademarks of Amazon.com, Inc. or its affiliates. Cloudflare and its logo are trademarks of Cloudflare, Inc.