For environmental health practitioners
Software for South African environmental health practitioners
Environmental health work is inspection, sampling and enforcement, and its output has to be defensible months later in front of somebody who was not there.
Or talk to us first- POPIA & HPCSA aligned
- We take medical aids
- Built by practising clinicians
HPCSA board
Environmental Health Practitioners
In short
iScript.live provides environmental health practitioners with structured inspection and sampling records captured in the field on a phone, with an immutable audit trail recording actor, timestamp and reason on every entry and export, and role-based access control. It is a records and workflow platform rather than a municipal enforcement system.
iScript.live is a multi-tenant, AI-native healthcare practice platform built in South Africa by Lighthouse iScript (Pty) Ltd. This page is about what iScript.live does for environmental health practitioners practising in South Africa. Environmental health practitioners in South Africa are regulated by the Health Professions Council of South Africa under the Health Professions Act 56 of 1974, through its Professional Board for Environmental Health Practitioners.
An environmental health practitioner protects public health through inspection, monitoring, investigation and enforcement — food and water safety, premises, waste, port health and environmental hazards. The subject of the work is usually a premises, a business or a population rather than an individual patient.
This page is deliberately the most cautious of the twenty-eight. iScript.live is a clinical practice platform, and environmental health practice is not clinical practice. What follows is what genuinely applies and what does not.
At a glance
- Platform
- iScript.live, built by Lighthouse iScript (Pty) Ltd
- Profession this page is about
- Environmental health practitioners
- Regulating council
- Health Professions Council of South Africa
- Governing statute
- Health Professions Act 56 of 1974
- Professional board
- Environmental Health Practitioners
- Country of practice
- South Africa
No registration-number prefix is published here. It could not be verified against an authoritative source, and a wrong one would be worse than none.
What actually gets in the way
Where the day goes in environmental health practitioners' practice
None of this is a software problem in the abstract. Each of these is an hour, a rejected claim or a clinical decision made with less information than it deserved.
Findings recorded on paper in the field
An inspection is written on a form, driven back to an office and typed in, which is where detail and timeliness are both lost.
Evidence that has to be defensible later
An enforcement decision may be challenged long afterwards, and a record without provenance is difficult to defend.
No consistency across practitioners
Different practitioners record the same inspection differently, so findings cannot be aggregated or compared across a district.
A day in the practice
What a working day looks like on iScript.live
The honest starting point is that the object of environmental health work is a premises or a population, and this platform's data model is built around a patient.
Identity and attribution
Own identity with a configured scope
Where you work inside an organisation on the platform, you work under your own identity with attributable activity and a scope the organisation configures, and every read, write and export records actor, timestamp and reason.
LiveWhere the work touches individuals
Occupational and clinical work is supported
Where the practice includes a clinical component — occupational health screening, an examination, an immunisation record for individuals — that is a patient record and the platform handles it in full.
LiveInspections and enforcement
Not what the platform is for
There is no inspection workflow, no premises register, no compliance-notice management and no enforcement case management in iScript.live. Those are the substance of environmental health work and they are not modelled here.
Invoicing an organisation
A non-patient debtor is supported
Where the practice invoices a municipality, an employer or a client organisation, the debtor is a separate record from the patient, so organisational invoicing works even where there is no individual patient in the transaction.
What you get, and what is still being built
The platform, read from your side of the desk
Every capability on this list is in production and in daily use. We keep the roadmap and the reality on separate lists on purpose.
Inspections as structured records
Structured templates capture inspection findings, sampling and follow-up as discrete fields, so findings across practitioners and sites are consistent enough to aggregate.
Structured consultation workflow
Field capture with an audit trail
Mobile-first, designed for low bandwidth, with row-level tenant isolation and an immutable audit trail logging actor, timestamp and reason on every read, write and export.
Multi-tenant clinical core
Notifications and correspondence
WhatsApp Business API messaging, transactional email and voice over IP, so notices and follow-up correspondence are issued from the record that holds the finding.
Telehealth, e-prescribing and messaging
Built today, or being built
What is live, and what is not, in one table
The same list as the cards above, in the form a sceptical reader wants it. Every status in the right-hand column is resolved from the platform roadmap at the moment this page renders. None of it is typed by hand.
| Capability | Platform capability it comes from | Status |
|---|---|---|
| Inspections as structured records | Structured consultation workflow | Live |
| Field capture with an audit trail | Multi-tenant clinical core | Live |
| Notifications and correspondence | Telehealth, e-prescribing and messaging | Live |
3 of these 3 capabilities are in production today. Anything in development is not available to buy, is not in a beta programme, and should not be counted on when you make a decision.
Why this is different
An inspection record is evidence, and evidence needs provenance
Environmental health work is judged retrospectively, which makes provenance the whole point. Capturing findings in structure in the field, with an audit entry on every subsequent read and export, produces a record that can be defended rather than one that has to be explained.
- Structured field capture on a phone, designed for low bandwidth.
- Immutable audit trail on every entry, read and export.
- Consistent templates so findings aggregate across practitioners and sites.
What it replaces
What actually comes out of the practice
Very little, and the table is short because inventing rows would be dishonest.
| What happens today | What it becomes |
|---|---|
| Occupational health screening records kept on paper or in a spreadsheet | Structured clinical records with an audit trail, where the work is clinicalLive |
| Invoices to municipalities and employers typed by hand | An account with an organisation as debtor, produced from the record |
Inspection, premises registers, sampling programmes and enforcement case management are not replaced, because they are not in the platform.
Billing and medical schemes
How environmental health practitioners actually get paid
Environmental health work is typically funded by a municipality, a government department, an employer or a client organisation rather than by a medical scheme, so scheme claiming is usually not the relevant mechanism at all.
Scheme claiming exists on the platform and runs through the live MediKredit integration, but for most environmental health practice it will simply be unused. That is a statement about the funding of the work, not about the platform.
What does apply is organisational invoicing. The debtor is a separate record from the patient, so a municipality, a department or an employer can be invoiced directly, and where the practice has a clinical occupational health component the two sit on the same account.
If your practice is entirely inspection and enforcement with no clinical component, the honest answer is that this platform is not built for your work.
The billing mechanics, and their status
- Organisation as debtor, with no patient in the transaction
- Live.
- Clinical record where the work is clinical
- Live.
- Scheme claiming
- Live, and for most of this practice, unused.
- Inspection and enforcement case management
- Not in the platform.
Who else touches it
Who else in the practice uses this, and what they can see
A practice is not one person, and a clinical record that only the clinician can reach is a record somebody else will keep a second copy of. Roles are configured by the practice, not assumed by the platform, and every role is scoped at row level.
| Role | What they do, and what they can see |
|---|---|
| The practitioner | Consults, records, prescribes where the registration allows it, and submits. Sees the full clinical record for patients within the practice. |
| Reception and front desk | Books, checks members in, confirms eligibility before the appointment and takes payment. Sees the demographic, appointment and account layers, not the clinical note. |
| Billing and accounts | Works claims, item-level rejections, reversals and remittance advice, and reconciles what was paid against what was submitted. Sees coded lines, not free-text clinical content. |
| Practice manager or owner | Configures the practice, the sites, the fees, the templates and who may do what. Sees activity and financial reporting across every site in the group. |
| A supervisor, where the registration requires one | Countersigns and reviews the work of a practitioner practising under supervision, against the same record rather than a printed copy of it. |
| An assistant, associate or locum | Joins the practice as a provider rather than as a shared login, so their activity is attributable to them and ends when their association does. |
Every read, write and export carries the actor, the timestamp and the reason, so who saw what is answerable rather than reconstructed.
Getting started
From registration to a working practice, and what moving across involves
Onboarding is measured in days rather than in an implementation project. Nothing here requires a server, a site visit or a consultant. Migrating history is the separate question, and it is answered below rather than skipped.
Standing the practice up
01
Register the service
Online registration produces a tenant with your branding and subdomain, with practitioners configured as roles.
02
Configure inspection templates
The inspections and sampling protocols you run are set up as structured templates so records are consistent across practitioners.
03
Inspect, record, follow up
Findings are captured in the field on a phone, correspondence is issued from the record, and every access is logged.
Moving off your current system
Moving practice software is the part everybody underestimates, so it is worth being exact about what is quick and what is not. Standing the practice up, as set out above, is quick. Bringing a decade of history across is not, and is scoped as its own piece of work.
Step 1
Run in parallel for a short period
Most practices keep the outgoing system readable while they work live in the new one, rather than attempting a hard cut-over on a Monday morning. Nothing about the platform requires the old system to be switched off first.
Step 2
Bring patients across
Patient demographics, medical-aid details and balances import first, because those are what reception needs on day one. Clinical history follows, and how much of it comes across as structured data rather than as attached documents depends entirely on what the outgoing system will export.
Step 3
Move the money last
Open claims and outstanding debtors are the last thing to move, and usually the cleanest approach is to finish the claim cycle already in flight on the old system while new work starts on the new one.
Historic-data migration is quoted separately from the platform, because its length is a property of the outgoing system rather than of this one. A practice that exports well is a short piece of work. A practice whose history exists only as scanned paper is a decision about how much of it is worth carrying.
Regulation, record-keeping and compliance
What the record has to survive
Clinical software carries the most sensitive data a person has, and a regulator will eventually read what it produced. Compliance is designed into the platform rather than certified around it afterwards.
Registration authority
Professional Board for Environmental Health Practitioners
Health Professions Council of South Africa, under the Health Professions Act 56 of 1974.
Record integrity
Immutable audit trails record actor, timestamp and reason on every read, write and export, which is the property an inspection record needs if it is challenged after the fact.
POPIA
Lawful processing, consent where applicable, data residency and subject-access handling are built into the platform. Personal information gathered during an inspection is processed under the same controls as clinical data.
The record has to be attributable
Every clinical entry carries who made it, when, and against which consent, on an immutable audit trail. An entry that is later corrected shows as a correction rather than replacing what was there, because a record that can be silently rewritten is not evidence of anything.
The record has to be retrievable years later
Clinical records outlive software, staff and sometimes practices. Records are held as structured data with their coding intact and are exportable, so the practice is not dependent on this platform continuing to exist in order to read its own history. Statutory retention periods are set by the regulator and the relevant legislation, not by us, and are not restated on this page.
Consent is part of the record, not a filing cabinet
Consent to treat, consent to a remote consultation and consent to share are captured in the consultation and stored against it, so the consent that applied at the time is retrievable with the entry it applied to.
Where the record is clinical, it is treated as clinical
An occupational health examination or an immunisation record for a named individual is health data with all the obligations that carries — POPIA lawful processing, consent, an immutable audit trail and access scoped by role. Records about premises rather than people are outside what this platform models.
What it costs
How this is priced, and what the quote depends on
The clinical platform is free, on every seat, permanently. You pay only for the medical claims you submit — at a rate that falls as you add modules — and optionally for the two business modules themselves. Every figure is published below rather than quoted on request.
01
CORE — the clinical platform, R0
The record, the diary, the billing, the claims workflow and the AI documentation, on every seat, at no cost and with no expiry. Not a trial and not a cut-down edition. Claims are R9.95 each on CORE, and that is the only charge.
02
R9.95, R8.95 or R7.95 per claim submitted
You pay for claims you actually send, from prepaid credits that never expire. The rate falls as you move up: R9.95 on CORE, R8.95 on STRIDE with one module, R7.95 on SUMMIT with both. Never a percentage of what the claim is worth, and never a percentage of what you earn.
03
STRIDE R699 a module, SUMMIT R1 199 for both
Website and Finance are optional business modules. They do not make you a better practitioner; they make you a better business, and they lower your per-claim rate while they are on. Neither is required to practise on the platform.
What the quote turns on
- How many medical-scheme claims you actually submit in a month — that is the only usage-based charge there is.
- Whether you want the Website module, the Finance module, both, or neither — which also sets your per-claim rate: R9.95 on CORE, R8.95 on STRIDE, R7.95 on SUMMIT.
- Nothing else. Seats are free, sites are free, storage is free, and support is not a tier.
- Migrating historic patient data from an outgoing system is scoped separately and quoted before any work starts.
- Nothing here is indexed to your turnover, your collections or the value of your claims.
For environmental health practitioners specifically
Where the practice has a clinical occupational health component, the per-claim or whole-practice models are the usual fit. Where it does not, there is probably no reason to buy this platform, and we would rather say that.
Every price on this site is published, not quoted. We never charge a percentage of what you earn. Registering a practice does not commit you to a contract.
Ask for a quote for your practiceObjections
The reasons not to do this, answered
Every one of these has been said to us by a practitioner in this profession or one adjacent to it. Where the answer is no, it says no.
Does it manage inspections, premises and compliance notices?
No. There is no inspection workflow, premises register, sampling programme or enforcement case management in the platform. That is the core of environmental health practice, and the platform does not do it.
So why does this page exist?
Because the profession is on an HPCSA board and a set of pages covering every board with one profession quietly missing would be worse. The page exists to tell you accurately where the platform applies — occupational health and clinical work, organisational invoicing, attributable identity — and where it does not.
I run occupational health screening as part of my practice. Is that supported?
Yes, fully. That part is clinical work with individual patients, structured records, consent, audit trail and an organisation as the debtor. It is the part of environmental health practice the platform is genuinely built for.
Questions practitioners actually ask
Environmental health practitioners and iScript.live
Short, direct answers, each written to make sense on its own if it is read without the question above it or the page around it.
Is there software for environmental health practitioners in South Africa?
iScript.live provides structured inspection and sampling records captured in the field on a phone, with an immutable audit trail on every entry and export and role-based access control. It is a records and workflow platform, not a municipal enforcement or licensing system.
Can inspections be recorded offline or on low bandwidth?
The platform is mobile-first and designed for low-bandwidth conditions, so field capture works where connectivity is intermittent rather than requiring a return to an office to type findings into a desktop system. Findings are captured in structure while the practitioner is still on site, which is where detail is otherwise lost.
Which board registers environmental health practitioners in South Africa?
Environmental health practitioners are registered with the HPCSA under the Professional Board for Environmental Health Practitioners. The platform models the role and enforces the permissions the service configures. Registration, scope and continuing-education obligations are set by that board rather than by the platform, which only records what practitioners do.
Does iScript.live replace a municipal licensing system?
No. It records and manages inspection, sampling and follow-up work with a defensible audit trail. Statutory licensing, enforcement registers and municipal systems of record remain separate, and integration with them is not currently offered. It is a records and workflow platform with a defensible audit trail, nothing more.
Does iScript.live manage environmental health inspections and enforcement?
No. There is no inspection workflow, premises register, sampling programme or compliance and enforcement case management in the platform. iScript.live is a clinical record and practice platform built around a patient rather than around a premises or a population.
Can an environmental health practitioner use iScript.live for occupational health work?
Yes. Occupational health screening, examinations and immunisation records for named individuals are clinical records, and the platform handles them in full with structured templates, consent, an immutable audit trail and access scoped by role. A municipality or employer can be the debtor while the record remains the individual's.
Can a municipality or employer be invoiced on iScript.live rather than a patient?
Yes. The debtor is a separate record from the patient, so an organisation can be invoiced directly even where there is no individual patient in the transaction. Where the practice also has a clinical component, both sit on the same account.
The setting
What environmental health practitioners and their practices look like on this platform
Editorial images, chosen to show the setting the software is used in rather than a stock photograph of a laptop.
These are AI-generated editorial images. They depict no real practitioner, patient or premises, and are not photographs of anyone on this platform or of any of the practices named elsewhere on this site.
Bring your practice onto the platform
Register the service and run one inspection in the field
Capture a real inspection on a phone, issue the correspondence, and check the audit trail records what you expect.