Opens in a new tab

RACGP F8 and APP 11: A Practice Manager’s Guide to Security Responsibilities

  Published · Updated

What Australian businesses say about Netluma IT

  • Liv Fit’s Avatar Liv Fit ★★★★★ 7 months ago
    We recently partnered with Netluma during our acquisition of an existing gym, and their expertise was invaluable. Zachary managed the entire transition … Read more of our IT infrastructure, ensuring a seamless switchover while significantly streamlining our operational systems. His professional approach and technical proficiency turned a complex integration into a smooth, efficient process. I highly recommend Netluma for any business looking for technical support and reliable IT solutions
  • Danny Taylor’s Avatar Danny Taylor ★★★★★ 3 months ago
    Exemplary customer service - Zach from Netluma IT is an absolute life saver when it comes to our business IT and communication needs. His foresight and … Read more knowledge puts us ahead of the curve instead of just being reactive. Outstanding work Zach, thank you.
  • Marcus Rouhana’s Avatar Marcus Rouhana ★★★★★ 4 months ago
    I've had the pleasure of working with Zach and can confidently say he's one of the rising stars among IT Providers in Surfers Paradise.He's … Read more professional, proactive, and committed to delivering outstanding client outcomes, consistent service, and building strong partnerships.Highly recommended.

Start with responsibilities, not a compliance label

A practice manager can buy security software and IT support, but cannot buy a transfer of the practice’s governance or legal obligations. The useful question is not “Is this package compliant?” It is “Which activities will each party perform, who makes the decisions, and what evidence will show that the arrangements work?”

This guide accompanies our healthcare IT support page. It explains selected information-security issues for general practices and questions to discuss with any prospective provider. Other healthcare services should check their own accreditation framework rather than assume RACGP general-practice standards apply to them.

Netluma IT does not certify compliance or confer accreditation. Buying IT support does not guarantee accreditation or legal compliance. Practice governance and legal duties are not transferred to the provider. This is general information, not legal advice or an exhaustive compliance checklist.

Which RACGP edition and standard are we discussing?

Sources were checked on 26 October 2026. The RACGP has published its Standards for general practices (6th edition). The relevant standard is F8 – Information security, within Foundations of general practice. This is published material, not a consultation draft.

Publication and accreditation transition are different things. The RACGP’s What practices need to know about the sixth edition says further transition information, including timing and accreditation requirements, will be communicated by the Australian Commission on Safety and Quality in Health Care. Confirm with your accreditation agency which edition applies to your next assessment; do not assume every practice is already assessed against the sixth edition.

F8.A calls for a documented and regularly tested ICT continuity, protection and recovery plan, including a cyber security incident response plan. It includes a backup log, up-to-date protection, secure offsite or cloud backups and the ability to restore information. Its supporting Table 6 describes daily (or more frequent) critical-data backups, regular backup testing, timely software patches, staff training and written provider agreements. Those are standards and guidance expectations, not a statement that Netluma IT performs every activity in a standard package.

F8.B addresses secure electronic systems and ICT. Where the person with primary technical-security responsibility is an external contracted provider, at least one practice team member must still have primary responsibility for digital governance. F8 also addresses digital communications, social media and record storage, retention and destruction. This guide is not a complete assessment of F8 or the wider Standards; F8.F is expressly labelled aspirational in the published standard.

APP 11: legal duties that continue when IT is outsourced

OAIC’s Chapter 11: APP 11 Security of personal information, updated 3 October 2025, explains the Australian Privacy Principle separately from RACGP accreditation.

APP 11.1 requires an APP entity to take reasonable steps in the circumstances to protect personal information it holds from misuse, interference and loss, and unauthorised access, modification or disclosure. The measures depend on the circumstances, including the sensitivity and volume of information and the possible consequences for individuals. A small practice should not treat sensitive patient records as low risk simply because its team is small.

APP 11.3 makes clear that reasonable steps include technical and organisational measures. Examples of technical measures include encryption, access controls and protective software; organisational measures include policies, staff training and procedures. Neither software alone nor a policy that staff cannot follow demonstrates that the arrangements are adequate.

The OAIC explains that “holds” includes possession or control. A practice that outsources storage but retains the right to deal with records can still hold that information. Outsourcing does not erase its duties, and a provider may also have its own obligations depending on the arrangement.

APP 11.2 requires reasonable steps to destroy or de-identify personal information once it is no longer needed for any purpose for which it may be used or disclosed under the APPs. The exceptions are information contained in a Commonwealth record, or information required to be retained by or under Australian law or a court/tribunal order. Do not interpret this as permission to delete clinical records after an arbitrary backup period. Obtain appropriate advice about health-record retention and legal holds, and document the practice’s decision before anyone implements deletion.

Access: the provider can configure, the practice must approve

The RACGP’s access and administration-rights guidance discusses individual logins, access matched to roles, audit logs and disabling access when staff leave. That supporting resource still refers to the fifth-edition indicator C6.4.C; it is useful operational guidance, not a sixth-edition indicator number.

Provider activities to agreeWhich party creates accounts, applies approved permissions, configures remote access and removes access across the clinical system, email, cloud storage and remote tools? Agree how multi-factor authentication and privileged accounts will be handled where supported. Include systems managed by the clinical vendor rather than assuming one provider controls everything.
Practice responsibilitiesDecide what each receptionist, clinician, locum and contractor needs to see. Approve access changes and tell the relevant parties when someone joins, changes role or leaves. Train staff to use individual logins and report suspected compromise. The IT provider cannot reliably infer an employment change it has not been told about.
Evidence and questionsAsk for an access register tied to approved roles and records of completed removals. Can the provider demonstrate who can administer the system? What do available audit logs show, who reviews them and how long are they retained? Agree review arrangements rather than assuming a frequency is included.

For an illustrative role/access matrix, shared mailboxes and staff-change checks, use the clinic Microsoft 365 permissions guide. For recurring login failures without weakening MFA, see safe diagnosis of clinic staff lockouts.

Backups: coverage and a successful job are not the same as recovery

RACGP F8.A and Table 6 address backup logs, secure offsite/cloud storage, regular testing and the ability to restore. The separate Validate and test your backups guidance explains checking accuracy, completeness and readability against the live system, and consulting the clinical software vendor about its backup functions.

Provider activities to agreeDefine coverage for the clinical database, attachments, appointment and billing data, shared files and relevant cloud systems. Agree backup frequency, retention, protection, monitoring, ownership of failure alerts and restore-test scope and frequency. Name the party responsible for each vendor-hosted system.
Practice responsibilitiesIdentify the information needed to continue safe care and how much downtime and data loss the practice can tolerate. Approve recovery priorities and test windows. Have an authorised practice representative check that recovered clinical information is usable, not merely that a server starts.
Evidence and questionsRequest a coverage map, backup logs and a dated restore report. What was restored, from which point in time, and into what environment? Were records and attachments readable and complete? How long did recovery take, what failed and who owns the corrective action? A green backup status alone does not answer those questions.

Recovery time and recovery point objectives describe agreed aims for downtime and data loss; they are not automatically guaranteed outcomes. This guide does not set a Netluma IT restore-testing schedule, recovery SLA or retention promise.

Planning a server replacement or hosting change? Use the clinic migration preflight, cutover and rollback checklist to separate clinical databases from file and email moves.

For the software-specific detail, including how Best Practice, Genie, MedicalDirector, Pracsoft and Zedmed each treat backups and server moves, and what a restore test of the clinical database should check, read IT support for Best Practice, Genie, MedicalDirector and Zedmed.

Patching: make clinical-vendor constraints visible

The supporting guidance in F8 Table 6 includes timely software patches and updates preferably outside practice hours. An operating-system update, clinical application release and medical-device firmware change can have different owners and compatibility constraints.

Provider activities to agreeKeep an agreed asset inventory, identify supported versions, apply in-scope updates and report failed or deferred patches. Agree how urgent security fixes are prioritised, how compatibility is checked with clinical vendors and who follows up exceptions. Do not assume “managed patching” includes every specialist application or medical device.
Practice responsibilitiesApprove maintenance windows and arrange appropriate clinical checks after changes. Ensure the vendor can be contacted and licences or support arrangements needed for updates are available. Decide on funding and replacement of unsupported systems, with advice about the risk.
Evidence and questionsAsk for a patch-status report and an exception register with a reason, accountable owner and review date. If the vendor blocks an update, what temporary protections are proposed and who accepts the residual risk? An indefinite “the vendor said no” is not a recovery or replacement plan. Compatibility concerns require a documented decision, not an assumption that the security risk disappears.

Incident planning: technical response and legal decisions are different

F8.A and F8.B connect incident response, continuity and governance. A workable plan should still be accessible when email, phones or the clinical system are unavailable.

Provider activities to agreeDetection, technical investigation, containment, restoration and preservation of useful logs are possible contracted activities, not assumed inclusions. Set escalation contacts, authority to isolate systems, availability, third-party forensic support and costs in writing. Identify gaps between provider coverage and practice operating hours.
Practice responsibilitiesName an internal digital-governance lead and a backup contact. Ensure staff know how to report an incident, who can authorise disruption to systems and how care will continue safely. Oversee the assessment of affected information, patient communications and legal notification decisions with appropriate privacy, legal and clinical advice.
Evidence and questionsRequest a written response plan, a contact tree and evidence of a practice exercise. Who contacts the insurer or specialist investigator? Who records decisions? What happens if the usual decision-maker cannot be reached? A provider’s technical alert is not the same as a completed breach assessment.

For patient-communication continuity, see the clinic dropped-call diagnostic and provider checklist. Compare setup, overlap, connectivity and support using the separate hosted VoIP cost guide for clinics, with a hypothetical AUD example rather than a provider quote.

Breach notification is a separate legal question

The OAIC’s Notifiable Data Breaches scheme guidance explains that regulated entities must notify the Commissioner and relevant individuals of eligible data breaches. Broadly, this involves unauthorised access or disclosure, or qualifying loss, likely serious harm and the inability to prevent that likely harm through remedial action. Exceptions can apply. Not every security incident is an eligible breach.

The scheme also requires assessment of suspected eligible breaches. Do not wait for a routine service review to raise a suspected exposure. Agree prompt escalation and assessment arrangements in advance, without treating this article as a substitute for advice on the incident.

Where practice and provider jointly hold information, both may have obligations. The OAIC explains how assessment and notification can be coordinated so one entity acts for the group; this is not a general transfer of liability to the IT provider. Record who will do what, and make sure the agreed response actually occurs.

Retention and disposal: decide first, implement second

APP 11’s destruction and de-identification guidance and RACGP F8.E address record handling beyond live clinical systems. Paper files, exports, backup copies and retired printers or drives also need attention.

Provider activities to agreeImplement authorised retention settings, secure deletion or de-identification and device disposal, with suitable evidence. Explain technical limits on removing individual records from backup sets and how retained copies are protected and eventually handled.
Practice responsibilitiesDetermine what must be retained and for what lawful purpose, including applicable legal holds. Approve a retention schedule after appropriate advice, and make sure it covers clinical vendors and former providers as well as local equipment.
Evidence and questionsAsk for the approved retention decision, a map of copies and disposal records. What remains after a contract ends? Can records be exported in a usable form? Who authorises destruction, and how is completion verified without exposing patient information in the evidence itself?

Turn the conversation into an agreed scope

Use these questions to start a documented discussion, not as an exhaustive compliance checklist. For each activity, record the responsible party, practice approver, covered systems, frequency or trigger, evidence to receive, exclusions, costs and escalation route. Resolve “someone else does that” gaps before relying on an arrangement.

Ask to see redacted sample reports and explain how unresolved failures are brought to the practice’s attention. Review the arrangement when staff, vendors, systems or practice risks change. Keep the full official standards and guidance available to the people responsible for governance.

For a conversation about your practice’s IT needs, see Netluma IT healthcare IT support. Any company-specific service commitment must be confirmed in the written agreement; this guide adds no new contractual duties or service inclusions.

Netluma IT does not certify compliance or confer accreditation. Buying IT support does not guarantee accreditation or legal compliance. Practice governance and legal duties are not transferred to the provider. This is general information, not legal advice or an exhaustive compliance checklist.

Need Help With Healthcare IT Security?

Discuss your practice’s systems, security priorities and agreed support scope. Netluma IT does not certify compliance or confer accreditation; practice governance and legal duties remain with the practice.

Related Services

CybersecurityPriority-based remote responseLocal Gold Coast team

Zachary French, Director, Netluma IT

Written by

Zachary French

Director, Netluma IT

Zachary has 15 years of IT experience across education, Youth Justice, residential and business IT support and managed services, including supporting medical and allied health practices across South East Queensland. He founded Netluma IT to give businesses one accountable team for IT, phones, internet and security.

This article is general information, not legal or compliance advice.

Related Articles

Ready to End the IT Frustration?

Let's have a quick chat. No pressure, no sales pitch — just honest advice about whether we're the right fit for your business.

Phone

1300 521 162

National — fastest way to reach us

Gold Coast(07) 3179 6849

Melbourne(03) 4421 6601

Remote Helpdesk

Mon–Fri 6:30am – 6pm

Remote Monitoring

24/7

Ready to talk?

Speak with an IT specialist about your business.

Call 1300 521 162