Health (Rheumatic Heart Disease Register of Western Australia) Regulations 2015

The Regulations define and operationalise a set of interlocking concepts: prescribed conditions, mandatory notification duties, the scope and content of notices, the register as a curated dataset, disclosure controls and patient rights. Each concept appears in a specific provision and together they structure the regulatory regime.

Prescribed conditions: acute rheumatic fever and rheumatic heart disease are declared prescribed conditions for the operation of Part IXA of the Health (Miscellaneous Provisions) Act 1911 (reg 4). The Regulations define acute rheumatic fever as an illness caused by an autoimmune response to group A streptococcus (GAS) (reg 3), and rheumatic heart disease as heart damage resulting from one or more episodes of acute rheumatic fever (reg 3).

Notifiers and duty to give notice: Regulation 5 lists who must give notice. This captures institutional heads (chief executive officers of hospitals and medical centres) and treating clinicians (medical practitioners and nurse practitioners who diagnose or treat the patient). An obstetrician who becomes aware that a pregnant patient has the condition also has a duty (reg 5). Duty mechanics are in regulation 6: duties are discharged by causing the required information to be provided to the Chief Health Officer and carry specified monetary penalties for non‑compliance (reg 6(1)). The Regulations exclude retrospective duties for diagnoses, tests or specialist reports that occurred before commencement (reg 6(2)).

Scope and content of notices: The information required varies by condition and timing. For acute rheumatic fever the notifier must provide personal identifiers, demographic data including ethnic origins and Aboriginal/Torres Strait Islander status, a diagnosis/treatment summary in a Chief Health Officer‑approved form, copies of relevant medical tests and specialist reports (reg 8). "Acute phase" is defined as diagnosis until three months later, and the timing obligations differ if material was produced during the acute phase (reg 7, reg 9). For rheumatic heart disease the required material is similar but the standard timeframes are generally 30 days (reg 10, reg 11).

The register and its permitted contents: Regulation 13 establishes the Rheumatic Heart Disease Register of Western Australia to contain all information notified under Part 2 (reg 13(2)), optionally additional material provided by corresponding officers from other jurisdictions and material from the repealed 2007 Regulations, and any other information the Chief Health Officer deems appropriate given the register purposes (reg 13(3)). The purposes are listed in reg 13(4) and include surveillance, monitoring secondary prophylaxis adherence, improving clinical follow‑up and access to specialist services, research, statistical reporting, and supporting a national data collection (reg 13(4)(a)-(h)).

Disclosure controls and patient protections: The Regulations make unauthorised disclosure by someone with access in the course of duty an offence with fines (reg 14). The Chief Health Officer may authorise disclosure in writing in specified scenarios: to treating clinicians or hospital staff for clinical history if consent cannot reasonably be obtained (reg 15(1)(a)); for NHMRC‑approved research (reg 15(1)(b)); to the Australian Institute of Health and Welfare if satisfied the information will be used only for register purposes (reg 15(1)(c)); to corresponding officers in other States/Territories where residence or treatment links exist (reg 15(1)(d)); and to the National Coordination Unit for inclusion in the national collection (reg 15(1)(e)). However, identifying information cannot be disclosed under (a) or (d) where the person has requested limited disclosure under regulation 17(1) (reg 15(2)). The Chief Health Officer may also authorise disclosure of non‑identifying information for register purposes (reg 15(3)). Authorisations must be in writing and may be general or specific (reg 15(4)).

Individual rights and legal capacity: Persons can request and obtain information the register holds about them (reg 16). They can request limited disclosure of identifying information (reg 17). Parents or guardians may exercise consent and request rights on behalf of persons under a legal disability (reg 18).

Definition and operational terms: The Regulations define several operational terms at reg 3, including "identifying information", "medical test", "medical specialist", "Aboriginal health worker" and "medical centre", each shaping who participates and what is captured by the notice requirements. For example, "medical centre" spans centres administered by the Department, health service providers, the Prisons Department, local governments and Aboriginal health services (reg 3).

Interjurisdictional and national integration: The text explicitly contemplates sharing with corresponding officers in other jurisdictions and with the National Coordination Unit for an Australia‑wide dataset (regs 13(3)(a) and 15(1)(d)-(e)). The Chief Health Officer’s satisfaction is a precondition for some disclosures (reg 15(1)(c),(d)), inserting an operational check.

Administrative discretion and format: The Chief Health Officer determines the manner and form of keeping the register (reg 13(5)) and approves the form for the diagnosis/treatment information to be provided under reg 8(b)(v). The Chief Health Officer also has discretion to decide what additional information is "appropriate" in reg 13(3)(c), and whether a request for further information is consistent with Part IXA objects (reg 12(2)(b)).

Enforcement levers: The regime uses criminal penalties as the primary enforcement tool for failing to provide notice and for unauthorised disclosure, with graduated minimum penalties for repeat offences specified in several provisions (regs 6(1), 12(3), 14). The Chief Health Officer may issue written requests for additional information and set a 14‑day compliance deadline for those requests (reg 12(3)).

Together, these concepts create a statutory surveillance, case management and data‑sharing framework focused on improving identification, treatment follow‑up and research into rheumatic fever and rheumatic heart disease, while imposing confidentiality duties and narrow, written authorisation routes for disclosure.

The Regulations touch a set of actors across clinical, administrative and research domains. Primary obligated actors are health employers and clinicians, but the rules extend to other persons with information, the Chief Health Officer as data custodian, interstate public health authorities and national bodies. The legal status and definitions in reg 3 determine the universe affected.

Obligated notifiers: Regulation 5 identifies who must give notice. The chief executive officer of a hospital must notify if the patient is a hospital patient; the chief executive officer of a medical centre must notify if the patient is a centre patient (reg 5(a)-(b)). Medical practitioners and nurse practitioners who diagnose or treat the patient for acute rheumatic fever or rheumatic heart disease must notify (reg 5(c)). Obstetricians are required to notify when they are responsible for treatment of a pregnant patient who becomes known to have one of these conditions (reg 5(d)). The definition of chief executive officer is role‑based and linked to the hospital or medical centre context (reg 3).

Health service organisations and centres: The definition of medical centre is broad and includes centres administered by the Department under the Health Services Act 2016, health service providers, the Department under the Prisons Act, local governments, the Aboriginal Health Council of Western Australia and members of that Council (reg 3). That means hospitals, community clinics, prison health services, local government clinics and Aboriginal community health services may all have notification obligations through their chief executives.

Clinicians and allied staff: The text requires treating clinicians to provide diagnostic information and copies of tests and specialist reports (regs 8, 10). Medical specialists and dentists are not listed as default notifiers under reg 5, but reg 12 allows the Chief Health Officer to request information from a dentist or "any other person" with relevant information where notice has already been given (reg 12(1)(b)-(c)). Persons with access to the register in the course of duty are subject to disclosure offences (reg 14).

Patients and their families: Patients are the subject of the data collected. The Regulations require demographic data including ethnicity and Aboriginal and Torres Strait Islander status (regs 8(b)(iv), 10(b)(iv)). Patients have rights under reg 16 to obtain information held about them and under reg 17 to request limited disclosure of identifying information. Parents and guardians can exercise these rights and give consent for persons under a legal disability (reg 18).

Chief Health Officer and Departmental staff: The Chief Health Officer is the data custodian, maintaining the register (reg 13), deciding forms and formats (reg 13(5)), approving disclosure authorisations (reg 15), requesting further information (reg 12), and deciding whether certain disclosures are appropriate (reg 15(1)(c)-(d)). Staff who have access to the register in the course of duty are constrained by the non‑disclosure offence and penalties (reg 14).

Interstate and national bodies: Corresponding officers in other States and Territories may exchange information where the patient’s usual residence or treatment links warrant it (reg 15(1)(d)). The National Coordination Unit and the Australian Institute of Health and Welfare are identified recipients for national compilation or analytical purposes, subject to the Chief Health Officer’s satisfaction about use and written authorisation (reg 15(1)(c),(e)).

Research community and ethics bodies: The Regulations permit disclosure for research approved under NHMRC‑compliant guidelines (reg 15(1)(b)). That links the register to academic or programmatic research subject to standard human research ethics requirements; approval is a statutory precondition for that category of disclosure.

Organisational compliance officers and legal advisers: Because the duties fall on institutional chief executives and treating clinicians and the register supports surveillance and secondary prophylaxis monitoring (reg 13(4)(c)-(d)), hospital compliance teams, electronic health record managers and legal advisers will need to operationalise notice pathways, data extraction and secure transmission, and manage consent and limited disclosure requests.

Broader public health system: The register’s enumerated purposes include monitoring occurrence, tracking prophylaxis adherence, improving clinical follow‑up and facilitating a national collection (reg 13(4)(a)-(h)). Those functions implicate public health planners, program managers and funders who rely on the data produced by notifiers and curated by the Chief Health Officer.

In short, the Regulations allocate burdens primarily to institutional managers and treating clinicians, while empowering the Chief Health Officer to collect, curate and share data with defined recipients for surveillance, treatment optimisation and research. The reach is both local (hospital and clinic personnel) and systemic (state data custodian, interjurisdictional officers, national units).

The Regulations lay out specific statutory duties for designated persons, with clear content and timing requirements, and balanced rights for individuals to access and limit the disclosure of their data. Below are the principal duties and statutory rights with their regulatory sources.

Duties to notify:

• Who must notify: Chief executive officers of hospitals and medical centres where a patient is under care, medical practitioners and nurse practitioners who diagnose or treat the patient for acute rheumatic fever or rheumatic heart disease, and obstetricians treating pregnant patients who become aware of the condition (reg 5). The chief executive officer definitions link responsibility to day‑to‑day operational control (reg 3).
• What must be provided: For acute rheumatic fever, the notifier must provide their own contact details and specified information about the patient: identifiers and contact details, parent/guardian details for minors, sex and date of birth, ethnic origins including Aboriginal and Torres Strait Islander status, a diagnosis/treatment summary in a form approved by the Chief Health Officer, and copies of relevant medical tests and medical specialist reports (reg 8). For rheumatic heart disease, similar personal and demographic information is required, together with copies of relevant tests and specialist reports (reg 10).
• Timing: The Regulations set explicit timeframes. For tests and specialist reports relating to an acute phase diagnosis, suppliers must provide copies within 14 days of receiving results or finalising reports; otherwise the timeframe is 30 days for non‑acute‑phase materials; and basic notification information must be supplied within 14 days of diagnosis or treatment for acute rheumatic fever and within 30 days for rheumatic heart disease (regs 7-9, 11). Obstetricians have a 14 day window for acute rheumatic fever notifications when no test or specialist report is being supplied (reg 9(4)), and a 30 day window for rheumatic heart disease in analogous circumstances (reg 11(4)). Regulation 6(3)(a) exempts a person from giving notice when they reasonably believe the Chief Health Officer already has the information.
• Compliance with requests: The Chief Health Officer may issue a written request for additional information to any notifier, a dentist, or any other person who appears to have relevant information, but only where notice has already been given and the Chief Health Officer is satisfied the collection is consistent with Part IXA objectives (reg 12(1)-(2)). Recipients of such a request must comply within 14 days (reg 12(3)).

Duties concerning the register and confidentiality:

• The Chief Health Officer must keep the register and include all notices (reg 13(1)-(2)). The register must be kept in a manner and form the Chief Health Officer determines (reg 13(5)). The Chief Health Officer has discretionary power to include additional information where appropriate for the enumerated purposes (reg 13(3)(c)).
• Persons who have access to the register in the course of their duties may not disclose information unless either they have the written consent of the affected person, disclosure is authorised under regulation 15, or disclosure is authorised or required under another written law (reg 14). This is a statutory confidentiality duty with associated penalties (reg 14).

Rights and protections for individuals:

• Right to know: Any person may request in writing that the Chief Health Officer search the register for information relating to them; the Chief Health Officer must then either state there is no information or provide a copy of the information as soon as reasonably practicable (reg 16). The standard is not time‑bound but is framed by reasonableness.
• Right to limited disclosure: Persons may request in writing that only limited disclosure of identifying information about them be made from the register. A successful request blocks disclosure of identifying information under certain authorisation routes in regulation 15, specifically subparagraphs (1)(a) and (1)(d) (reg 17(1)-(2)).
• Capacity proxies: Parents or guardians of persons under a legal disability may provide written consent where consent is required for clinical disclosures and may exercise rights under regs 16 and 17 on behalf of the person (reg 18).

Authorised disclosure pathways:

• The Chief Health Officer may authorise disclosure in writing where it is not reasonably practicable to get the patient’s written consent, to provide clinical history to treating clinicians and their employing/practising staff (reg 15(1)(a)). Written authorisation can be general or case‑specific (reg 15(4)).
• Disclosure for research is authorised where research is approved in accordance with NHMRC guidelines (reg 15(1)(b)).
• Disclosure to the AIHW is permitted if the Chief Health Officer is satisfied the AIHW will use the information solely for purposes mentioned in reg 13(4) (reg 15(1)(c)). Disclosure to corresponding officers in other jurisdictions and to the National Coordination Unit is authorised subject to satisfaction of statutory triggers (reg 15(1)(d)-(e)).
• Identifying information remains protected where a person has requested limited disclosure (reg 15(2)).

Enforcement and penalties:

• Failure to provide notice as required by regulation 6 carries a fine up to $1,000 with graduated minimum penalties for subsequent offences, specifically $100 for a first offence, $200 for a second and $500 for later offences (reg 6(1)).
• Failure to comply with a written information request from the Chief Health Officer (reg 12(3)) attracts the same penalty scale (reg 12(3)), subject to the statutory defence that the person did not possess the requested information at the time (reg 12(4)).
• Unauthorised disclosure from the register by a person with access in the course of duty is an offence carrying the same monetary penalty and graduated minimums (reg 14).

Ancillary duties/constraints:

• The Regulations do not require disclosure of pre‑commencement diagnoses, tests or reports (reg 6(2)).
• Notifying duties apply even if the patient was previously diagnosed or treated in another State or Territory (reg 6(3)(b)).
• The Chief Health Officer’s powers to request additional information are conditioned on the prior giving of notice and on consistency with Part IXA purposes (reg 12(2)).

These duties and rights create a structured reporting chain from front‑line clinicians and institutional heads to a central data custodian, with defined statutory protections for patient data and limited, written‑authorised disclosure options.

The Regulations rely on monetary fines as the principal enforcement instrument, coupled with administrative authorisation powers vested in the Chief Health Officer. Enforcement provisions are specific about penalty amounts, minimums by offence repetition, timelines for compliance with requests, and defences.

Penalty structure:

• For failure to perform the duty to give notice under regulation 6(1), the maximum penalty is a fine of $1,000, with legislated minimums: $100 for a first offence, $200 for a second offence, and $500 for a subsequent offence (reg 6(1)). The provision describes the penalty as "a fine of $1 000, but the minimum penalty" with the graduated minima listed.
• For failure to comply with a written request from the Chief Health Officer under regulation 12(3), the penalty mirrors reg 6(1): a fine of $1,000 with minimum penalties of $100, $200 and $500 for repeated offences (reg 12(3)). Regulation 12(4) provides a defence that the person did not have the requested information at the time the request was made.
• For unauthorised disclosure by a person who has access to the register in the course of the person’s duty, regulation 14 prescribes the same penalty regime: a fine of $1,000 with minimums of $100, $200 and $500 for first, second and subsequent offences respectively (reg 14).

Enforcement mechanisms and administrative levers:

• The Chief Health Officer acts as the primary administrative enforcer: receiving notices and requests for information, maintaining the register, approving forms and formats for submissions, and making written authorisations for disclosure under regulation 15 (reg 13, reg 15).
• The Chief Health Officer may require further information in writing from notifiers, dentists, or any other person who may have relevant information about a person who has had an episode of acute rheumatic fever or has rheumatic heart disease, but only where notice has already been given and the Chief Health Officer is satisfied that collection is consistent with the objects of Part IXA (reg 12(1)-(2)). The 14‑day compliance period for such requests imposes an enforceable administrative deadline (reg 12(3)).
• The Chief Health Officer’s written authorisations for disclosure are the statutory means by which otherwise confidential register information may be shared (reg 15(4)). Authorisations can be general or specific, enabling flexible operational sharing while maintaining a written record.

Limits on enforcement reach:

• The Regulations explicitly exclude an obligation to provide information about diagnoses, tests or reports that predate commencement (reg 6(2)), limiting enforcement to post‑commencement events.
• The Chief Health Officer cannot request additional information under reg 12 unless notice has already been given under reg 6 and the proposed collection aligns with Part IXA objects (reg 12(2)(a)-(b)). This is both a procedural and substantive precondition before enforcement of a reg 12 request is possible.
• The statutory defence in reg 12(4) prevents penalties where the requested information was not in the possession of the recipient at the time of the request, placing a burden on enforcement agencies to prove possession at request time.

Practical enforcement implications:

• The fine quantum is modest in absolute terms, and the graduated minima indicate a legislative intent to penalise repeat non‑compliance progressively. The maxima and minima are set uniformly across notice failures, failure to comply with information requests, and unauthorised disclosure, pointing to a consistent enforcement scale across data collection and confidentiality offences (regs 6(1), 12(3), 14).
• Enforcement will require administrative processes: logging notices, tracking timeframes for 14‑day and 30‑day windows, recording requests and responses to reg 12 notices, and maintaining audit trails for any authorisations under reg 15. The Chief Health Officer’s written authorisation requirement creates a recorded chain of lawful disclosures that can be reviewed in enforcement contexts (reg 15(4)).
• The requirements for the Chief Health Officer to be satisfied about certain disclosures (for example, to the AIHW or corresponding officers) introduce subjective checkpoints that enforcement bodies will need to document, to demonstrate lawful decision‑making in the face of subsequent challenge (reg 15(1)(c)-(d)).

Interaction with other written laws and external enforcement: Regulation 14(c) allows disclosure if authorised or required under another written law, signalling that statutory compulsion elsewhere (for example, a warrant or court order under other legislation) can supersede the confidentiality duty. The Regulations do not identify specific external enforcement agencies, but the Chief Health Officer as custodian will be the central administrative actor in enforcement, with offences likely to be prosecuted under the Health (Miscellaneous Provisions) Act 1911 framework.

Overall, enforcement combines modest monetary penalties for non‑compliance and unauthorised disclosure with administrative oversight by the Chief Health Officer, dependent on record‑keeping, written authorisations and procedural checks linked to Part IXA objects and external written laws.

The Regulations are drafted to work within an existing statutory and administrative ecosystem. They reference multiple other written laws for definitions, research approval standards and interjurisdictional data sharing. The text contains express interaction points and preconditions where other statutes or standards come into play.

Statutory hooks and definitions:

• The Regulations operate under the Health (Miscellaneous Provisions) Act 1911 by prescribing conditions to which Part IXA applies (reg 4). The mechanics of Part IXA are outside this instrument, but the Regulations explicitly make acute rheumatic fever and rheumatic heart disease subject to Part IXA, and several provisions (for example reg 12(2)(b)) condition actions on achieving Part IXA’s objects, thereby tying administrative discretion to that parent Act (reg 4; reg 12(2)(b)).
• Several defined terms derive from other statutes: "Aboriginal health worker" references the Vocational Education and Training Act 1996 (reg 3); "health service provider" and "hospital" are defined by the Health Services Act 2016 (reg 3); "dentist", "medical specialist" and "obstetrician" are defined by reference to the Health Practitioner Regulation National Law (Western Australia) (reg 3). These cross‑references ensure that professional registration, institutional responsibilities and workforce definitions remain consistent with broader health law frameworks.

Research approvals and human research law:

• Regulation 15(1)(b) permits disclosure for research that is approved in accordance with guidelines for medical research involving humans issued under the National Health and Medical Research Council Act 1992. This means that standard human research ethics frameworks (NHMRC guidelines) are a statutory gatekeeper for research‑use of register data (reg 15(1)(b)). Research access is therefore tied to established human research ethics requirements.

Data sharing with national and interjurisdictional bodies:

• The Regulations authorise disclosure to the Australian Institute of Health and Welfare (AIHW) where the Chief Health Officer is satisfied the AIHW will use the data solely for register purposes as listed in reg 13(4) (reg 15(1)(c)). The AIHW itself is established under the Australian Institute of Health and Welfare Act 1987 (Commonwealth), which the Regulations reference in the definitions (reg 3).
• The Regulations facilitate interstate exchange by allowing disclosure to a corresponding officer in another State or Territory if the Chief Health Officer is satisfied the person’s usual place of residence is or was in that jurisdiction or the person has been diagnosed or treated in Western Australia (reg 15(1)(d)). The definition of corresponding officer is jurisdictionally comparative, relying on the other State/Territory law to identify persons with comparable functions (reg 3).
• Disclosure to the National Coordination Unit for inclusion in the national data collection is expressly permitted (reg 15(1)(e)), tying the state register into the national Rheumatic Fever Strategy framework referenced in reg 3 and Schedule E of the National Partnership Agreement on Specified Projects. The Regulations therefore anticipate and enable national dataset aggregation.

Privacy and other written laws:

• The confidentiality offence in regulation 14(c) allows disclosure where authorised or required under another written law. That creates a statutory interface where external laws, subpoenas, court orders or statutory reporting obligations may supersede the register’s confidentiality obligation. The Regulations do not mention the Commonwealth Privacy Act or State privacy regimes explicitly; their disclosure rules stand on their own and allow for necessary compliance where other written law requires disclosure (reg 14(c)).
• Research disclosure is governed by NHMRC requirements which often include privacy protections and de‑identification as part of ethics approvals. The Chief Health Officer’s satisfaction prerequisites for AIHW and corresponding officer disclosures place an administrative control around cross‑system data linkage that is sensitive to other legal constraints (reg 15(1)(c)-(d)).

Pre‑existing regulations and repeal:

• The Regulations repeal the Health (Notification of Acute Rheumatic Fever) Regulations 2007 (reg 19). The register may contain information provided under the repealed regulations (reg 13(3)(b)), indicating continuity of historical data but a forward shift in statutory design and purposes.

Administrative law and discretion:

• The Chief Health Officer’s discretions,determining register form and manner (reg 13(5)), approving diagnostic information forms (reg 8(b)(v)), deciding whether collecting further information is consistent with Part IXA (reg 12(2)(b)), and being satisfied before disclosing to AIHW or corresponding officers (reg 15(1)(c),(d)),create points where administrative law principles may be engaged. The Regulations specify procedural requirements (for example, written authorisations), but do not themselves set judicial review mechanisms; those will be provided by general administrative law.

Clinical and professional regulation alignment:

• Definitions and duties draw on the Health Practitioner Regulation National Law (Western Australia) to identify medical specialists, dentists and obstetricians, thereby aligning professional duties under these Regulations with national registration standards (reg 3). This linkage can affect professional practice obligations and workplace reporting protocols.

In sum, the Regulations embed the state register within an interlocking framework of state and Commonwealth health, research ethics and interjurisdictional data sharing laws. They rely on cross‑statutory definitions, require congruence with NHMRC standards for research, allow data flows to national bodies and corresponding interstate authorities subject to Chief Health Officer satisfaction, and carve out exceptions where other written laws require disclosure. The legal architecture is purposefully connected to broader health governance instruments while keeping administrative control with the Chief Health Officer.

The Regulations were originally made in 2015 and have been amended since. The compilation table and embedded amendment notes give the concrete dates and instrument sources for the changes recorded in the text.

Original instrument and commencement:

• Health (Rheumatic Heart Disease Register of Western Australia) Regulations 2015 were gazetted on 19 May 2015 (Gazette p. 1771‑92). Regulations 1 and 2 (citation and commencement) commenced on 19 May 2015 (gazettal day). The remaining regulations commenced on 18 June 2015, the day after the period of one month following gazettal (reg 2; compilation table).

Subsequent amendments and their commencement:

• Health Services (Consequential Amendments) Regulations 2016, Part 3, were gazetted on 24 June 2016 (p. 2311-15) and commenced on 1 July 2016. The edition of regulation 3 bears an amendment note showing it was amended by Gazette 24 Jun 2016 p. 2312‑13, and this aligns with the compilation table which lists the 2016 instrument (reg 3 amendment note; compilation table).
• Health Regulations Amendment (Public Health) Regulations 2016, Part 20, were gazetted 10 January 2017 (p. 237‑308) with commencement of the amendments on 24 January 2017. The text shows amendment notes referencing Gazette 10 Jan 2017 p. 278 for several provisions including reg 3 amendments and other schedule updates (reg 3 and multiple regs note amended: Gazette 10 Jan 2017 p. 278, regs 8, 9, 10, 11, 12, 13, 15, 16, 17).

Text‑level amendment notes:

• Regulation 3 (Terms used) shows amendment notes: "Regulation 3 amended: Gazette 24 Jun 2016 p. 2312‑13; 10 Jan 2017 p. 278." Several other provisions include editorial amendment annotations such as "[Regulation 8 amended: Gazette 10 Jan 2017 p. 278.]" and similar notations for regs 9, 10, 11, 12, 13, 15, 16 and 17. These indicate textual adjustments made by the 2016 and 2017 amendment instruments.
• The compilation table at the end of the Regulations records the gazettal and commencement details for the base instrument and the two amending instruments (2016 and 2017). It reproduces the gazettal pages and commencement dates: base regulations gazetted 19 May 2015 and commencing 19 May/18 June 2015; 2016 amendments gazetted 24 Jun 2016, commencing 1 Jul 2016; 2017 amendments gazetted 10 Jan 2017, commencing 24 Jan 2017.

Repeal of predecessor regulations:

• Regulation 19 expressly repeals the Health (Notification of Acute Rheumatic Fever) Regulations 2007 with the repeal operative under these Regulations. Regulation 13(3)(b) permits the register to contain information provided under the repealed regulations, indicating preservation and incorporation of historical data into the new register framework (reg 19; reg 13(3)(b)).

Practical consequence of amendments recorded in the text:

• The amendments reflected in the 2016 and 2017 instruments appear to have been incorporated throughout the Regulations, with repeated inline notes referencing the Gazette entries. The text as compiled includes those amendments. Notably, the definition section (reg 3) was updated, which can materially affect who is captured by the regime (for example, changes to the definition of medical centre, Aboriginal health worker or other defined terms).
• Readers needing to track changes to specific clauses should consult the cited Gazette pages for the detailed amending instruments, and the dates in the compilation table to understand the operational effect of those amendments.

Limitations of the compilation notes:

• The compilation table provides the statutory record of gazettal and commencement for the base regulations and their amendments. It does not provide a line‑by‑line amendment history within this text beyond the marginal notes that identify the Gazette pages and dates. Practitioners requiring the precise wording changes or the policy intent behind the amendments should consult the amending regulation texts, associated explanatory memoranda and the Gazette entries referenced.

In short, the Regulations were introduced in 2015 and have been amended by instruments in 2016 and 2017. The statutory compilation and marginal notes in the published text record those amendments and provide the formal commencement timeline, while reg 19 records the repeal of the 2007 notification regulations and preserves data continuity by allowing transfer of earlier reported data into the new register (reg 19; reg 13(3)(b)).

The Regulations as provided contain no case law, judicial decisions, or recorded litigation outcomes. The text includes no references to any judicial interpretation, court challenges, or administrative tribunal rulings. The compilation notes and the body of the Regulations list only statutory amendments and gazette references (compilation table, reg 3 amendment notes).

What the source shows:

• The Regulations make no mention of litigation, judicial review, or precedent cases. There are no case citations, no reported determinations of offences created by the Regulations, and no entries indicating that the provisions have been the subject of judicial clarification in published decisions.
• The absence of litigation references in the Regulations means that the statutory language, administrative discretions vested in the Chief Health Officer, and the enforcement mechanisms set out in the text remain to be interpreted by courts if disputes arise. Administrative decision points susceptible to challenge include the Chief Health Officer’s satisfaction thresholds for disclosure (reg 15(1)(c)-(d)), decisions about whether secondary information collection is consistent with the objects of Part IXA (reg 12(2)(b)), and determinations about appropriate register content (reg 13(3)(c)).

Implications for practitioners and litigators:

• Because no litigation history is recorded in the text, practitioners must treat the statutory provisions as not yet authoritatively construed by courts. Where legal questions hinge on the meaning of phrases such as "reasonably practicable" in reg 15(1)(a), "as soon as reasonably practicable" in reg 16(b), or the Chief Health Officer’s subjective "satisfaction" in reg 15, those are open to interpretation under general principles of statutory construction and administrative law.
• Enforcement matters (penalty imposition for non‑compliance or unauthorised disclosure) may present early testing grounds for judicial review or criminal prosecutions, but the source does not record any such matters to date.

Recommended approach where litigation risk exists:

• Because the Regulations create multiple administrative discretions and privacy‑sensitive authorisations, agencies and private parties should document decision‑making processes to create an administrative record that can be reviewed if any dispute progresses to litigation. This includes written reasons for disclosure authorisations, records of consent efforts, logs of notices received and transmitted, and compliance checks concerning reg 12 requests.
• Legal practitioners advising clients should note the lack of adjudicated interpretations in the cited text, and where contested matters arise relating to the scope of disclosure authorisations, timing obligations or enforcement, expect to rely on general administrative law principles and the exact statutory wording in the Regulations.

In summary, the provided Regulations contain no litigation history. The text sets out statutory obligations and administrative discretions that may present litigation or review opportunities, but no judicial resolution of such disputes is recorded within the instrument.

The Regulations contain several operational and drafting particulars that can produce compliance surprises. These are practical pitfalls and points of legal ambiguity that affect notifiers, data custodians and patients. Each item below is grounded in the text and cites the relevant provision.

1. Duty applies even if prior diagnosis in another jurisdiction:

   • Regulation 6(3)(b) expressly states that a person has a duty to give notice even if the patient has been previously diagnosed with, or treated for, acute rheumatic fever or rheumatic heart disease in another State or Territory. That means clinicians cannot assume interstate diagnosis removes the obligation to report to the Western Australian Chief Health Officer if the patient is being diagnosed or treated in WA (reg 6(3)(b)).

2. Exclusion for pre‑commencement material:

   • Regulation 6(2) excludes obligations to report diagnoses, tests or specialist reports that occurred before commencement. Practitioners must therefore distinguish between pre‑ and post‑commencement records; only post‑commencement events trigger notice obligations (reg 6(2)).

3. Reasonable belief that CHO already has the information:

   • Regulation 6(3)(a) excuses a person from giving notice if they reasonably believe the Chief Health Officer already has the information. This introduces a factual test of "reasonable belief" which may be difficult to establish operationally. Notifiers should establish reliable internal checks against the register or an administrative confirmation protocol to avoid liability (reg 6(3)(a)).

4. Form approved by Chief Health Officer:

   • Regulation 8(b)(v) requires provision of diagnosis/treatment information "in a form approved by the Chief Health Officer". The absence of a published, specific template in the Regulations means that compliance requires obtaining or using the CHO‑approved form and keeping proof of the form used (reg 8(b)(v), reg 13(5) where CHO controls form and manner). Failure to use the approved form could render notices non‑compliant.

5. Timeframes differ by phase and document type:

   • The acute phase is defined as diagnosis until three months later (reg 7). For tests and specialist reports produced during the acute phase, the deadline is 14 days; otherwise the timeline is 30 days (reg 9(2)-(3)). Notifiers must track dates of testing and consultation carefully; delivering materials late can attract penalties under reg 6(1) and reg 12(3).

6. Obstetrician special rules:

   • Obstetricians have specific notification triggers if the patient is pregnant and the information being provided does not include a test or specialist report: 14 days for acute rheumatic fever (reg 9(4)) and 30 days for rheumatic heart disease (reg 11(4)). Obstetricians need workflows to identify pregnant patients with these diagnoses to meet these deadlines (reg 5(d), regs 9(4), 11(4)).

7. Broad definition of medical centre:

   • "Medical centre" includes centres administered by the Department under the Health Services Act 2016, health service providers, the Prisons Department, local governments, the Aboriginal Health Council and its members (reg 3). This expands institutional responsibilities beyond private GP clinics to include local government and prison health services; chief executives of these entities must ensure reporting systems are in place.

8. Chief Health Officer discretion and subjective satisfactions:

   • Several provisions hinge on the Chief Health Officer being "satisfied" about matters such as whether AIHW will use data solely for register purposes or whether collecting additional information is consistent with Part IXA (regs 12(2)(b), 15(1)(c)). These are subjective thresholds. Agencies should document assessments and reasons for satisfaction to reduce challenge risk.

9. Limited disclosure request creates an absolute block for some disclosures:

   • Regulation 17 allows individuals to request limited disclosure of identifying information. If made, reg 15(2) prevents disclosure of identifying information under reg 15(1)(a) (clinical history to treating clinicians where consent is impracticable) and reg 15(1)(d) (to corresponding officers). This can restrict clinical information flows the healthcare system might expect; clinical staff should check the register for limited disclosure flags (reg 17(1)-(2), reg 15(2)).

10. Penalties are modest but have minimums for repeats:

    • The enforcement fines are relatively small in absolute terms (up to $1,000) but have legislated minimums for repeat offenders (reg 6(1), reg 12(3), reg 14). Organisations should not assume low fines mean low risk; repeated non‑compliance escalates minimums and carries reputational and operational consequences.

11. "Subsequence offence" wording inconsistencies:

    • The Regulations include the term "subsequence offence" in reg 12(3) and elsewhere. This appears to be a drafting irregularity; for enforcement interpretation rely on the substantive graduated minima set out, but be aware of possible textual errors in prosecution materials and raise drafting queries if needed (reg 12(3), reg 14). Practitioners should not treat this as altering the legislative effect.

12. Access to the register by non‑medical persons:

    • Regulation 12 allows the Chief Health Officer to request information from "any other person" who, in the Chief Health Officer’s opinion, has information about a person who has had an episode of acute rheumatic fever or has rheumatic heart disease (reg 12(1)(c)). This opens the potential for requests to non‑clinical entities, but only where notice has already been given and the collection aligns with Part IXA objects (reg 12(2)). Organisations should be prepared for such requests and ensure they have processes to locate and deliver relevant records within the 14‑day statutory window (reg 12(3)).

13. Timing standard: "as soon as reasonably practicable":

    • Regulation 16(b) requires the Chief Health Officer to either say there is no information or give a copy of information to a requester "as soon as reasonably practicable" after a written request. That is a non‑specific timing standard, creating uncertainty for individuals seeking records and for the CHO’s resourcing; agencies should adopt internal SLAs to manage expectations (reg 16(b)).

14. Register may include information from repealed regulations:

    • The register may contain information provided under the repealed 2007 Regulations (reg 13(3)(b)). Practitioners and auditors should be aware that historical entries may exist and may be managed differently, for example in provenance or completeness.

Each of the above points can produce operational friction if not anticipated. Systems, record‑keeping, and administrative documentation (especially for CHO satisfaction determinations and written authorisations) are crucial to mitigate these "gotchas."

To operationalise compliance with the Regulations, institutions and clinicians should adopt documented workflows, data capture templates, record retention practices and governance checks aligned to the statutory provisions. The following practical checklist is grounded in the text and designed for health service providers, hospital administrators, clinicians and compliance officers.

1. Establish who internally holds the statutory duty to notify:

   • Identify the designated notifier at each site: the chief executive officer of the hospital or medical centre should be the institutional point person (reg 5(a)-(b)). Clinicians who diagnose or treat patients with acute rheumatic fever or rheumatic heart disease (medical practitioners and nurse practitioners) must also be aware of their personal reporting obligations (reg 5(c)). Obstetricians must be included in the communications chain for pregnant patients (reg 5(d)).

2. Obtain and adopt the Chief Health Officer‑approved form(s):

   • Regulation 8(b)(v) requires diagnosis/treatment information in a form approved by the Chief Health Officer. Contact the Chief Health Officer’s office to obtain the authorised forms or templates and ensure electronic health record (EHR) systems can generate those forms (reg 8(b)(v), reg 13(5)). Retain evidence of form use in audit logs.

3. Implement a timed workflow for document capture and transmission:

   • Set deadlines to ensure tests and specialist reports are transmitted within statutory timelines: 14 days for materials produced during the acute phase, 30 days for other materials (regs 7, 9(2)-(3), 11(2)-(3)). For basic notification data: 14 days after diagnosis or treatment for acute rheumatic fever and 30 days for rheumatic heart disease (regs 9(5), 11(5)). Build EHR triggers and task assignments to meet these deadlines.

4. Ensure completeness of required information:

   • Notices must include the notifier’s contact details, the patient’s full name, phone and residential and email address, parent/guardian contact for minors, sex and date of birth, and the patient’s ethnic origins including Aboriginal/Torres Strait Islander status (regs 8(a), 8(b)(i)-(iv), 10(a)-(b)(iv)). Also prepare copies of each medical test and specialist report relevant to diagnosis or treatment (regs 8(c)-(d), 10(c)-(d)). Record consent where applicable.

5. Develop a process to check the register before re‑notifying:

   • Regulation 6(3)(a) provides a reasonable belief defence where the notifier reasonably believes the Chief Health Officer already has the information. Establish an internal check with the public health unit to confirm whether the CHO has already received notice, and document the check to evidence reasonable belief where relied upon (reg 6(3)(a)).

6. Prepare for reg 12 written requests:

   • The Chief Health Officer can request further information where notice has been given and the collection aligns with Part IXA objectives (reg 12(1)-(2)). Designate staff to receive written requests, search records promptly and comply within 14 days. Maintain logs demonstrating searches and the absence of information, to rely on the statutory defence in reg 12(4) if necessary.

7. Register access, privacy and disclosure governance:

   • Limit access to the register to staff with a work need. Train staff on the non‑disclosure offence in reg 14 and secure the register to prevent unauthorised disclosures. For authorised disclosures under reg 15, keep written authorisations and a disclosure log (reg 14-15). Ensure any disclosure to researchers meets NHMRC approval criteria (reg 15(1)(b)) and document the CHO’s satisfaction determinations for AIHW or corresponding officer disclosures (reg 15(1)(c)-(d)).

8. Implement patient rights workflows:

   • Establish procedures for handling written requests under reg 16 to search and provide copies of register information to the person concerned, and set internal targets to respond "as soon as reasonably practicable" (reg 16). Create a system to accept and record written limited disclosure requests under reg 17 and flag the record to prevent unauthorised identifying disclosures blocked by such a request (reg 17(1)-(2)).

9. Consent processes and parental/guardian actions:

   • For persons under a legal disability, ensure that parents or guardians can give written consent for clinical disclosures and make requests under regs 16 and 17 on behalf of the person (reg 18). Verify documentary proof of legal guardianship in such cases.

10. Documentation and record retention:

    • Keep an audit trail for all notices, copies of tests and specialist reports transmitted, written requests from the Chief Health Officer, and written CHO authorisations for disclosure. Retain evidence of internal checks showing whether the CHO already held information for reg 6(3)(a) reliance. Ensure EHR metadata captures timestamps to demonstrate compliance with 14/30 day windows.

11. Interjurisdictional and national data sharing:

    • If a patient has a usual residence outside WA, or has treatment links elsewhere, be prepared to assist CHO assessments about notifications to corresponding officers. For data sharing with AIHW or the National Coordination Unit, ensure the CHO is provided with necessary assurances about purpose limitations and data use (reg 15(1)(c)-(e)).

12. Training and policy updates:

    • Train clinicians and administrative staff about definitions in reg 3 (for example, what constitutes a "medical test", "medical specialist", "medical centre", and "Aboriginal health worker") so that teams recognise reportable events and capture the specified ethnicity data fields (reg 3, regs 8 and 10).

13. Compliance monitoring and internal audit:

    • Run periodic audits to check that notices were made, that timeframes were met, and that requests from the CHO were responded to within 14 days. Use audit results to refine workflows and to update forms and EHR templates. Maintain a register of internal compliance breaches and corrective actions.

14. Legal and policy escalation:

    • For ambiguous situations,such as where "reasonable belief" or "as soon as reasonably practicable" are in play,escalate to legal counsel or the CHO for clarification and, where necessary, obtain written confirmation to mitigate enforcement risk.

15. Prepare for low‑threshold penalties but reputational oversight:

    • Although monetary penalties are modest, repeated non‑compliance increases minimum fines. Treat statutory compliance as an operational requirement with reputational and public health consequences and ensure governance oversight.

Following these steps will align institutional processes to the statutory requirements in regs 5-13 and 15-18. Because several provisions require the Chief Health Officer’s forms and satisfactions, maintain active lines with the CHO’s office to obtain templates, authorisations and procedural clarifications, and document all interactions to create a robust compliance trail.