Health & Safety

Denise Okafor works the front desk at Claymont. Jordan Price, 14, carries a rescue inhaler, registered on his record months ago with its route recorded as Oral, because Inhaler was rejected the day it was entered. His parent's authorisation is on file, so Can Administer already reads yes.

This afternoon Jordan uses the inhaler after gym, with Denise watching. She opens Medications On-Site to write down that it happened: what was given, when, and who saw it. There is nothing there to open. No form exists anywhere in PTRS for recording that a dose was given, so Denise writes it in the paper binder Claymont has kept since before PTRS arrived.

Read this before anything else on this page

A medication cannot be recorded as given, by anyone, anywhere in PTRS. The screen, the button and the record it would create all exist, correctly built. Nothing calls any of them, so the Administration Log table can only ever say there is nothing to show.

The certification that would let a staff member give a dose under her own name cannot be created either. The Add Certification form offers eight kinds of certification. Seven of them are refused the moment they are saved, including the one the form starts on. The certification this module actually checks for is not one of the eight choices.

Both are set out in full below and in what this module can and cannot record.

What Health & Safety is for

Delaware licensing treats a stored medication as a controlled item, not a convenience. A club holding Jordan's inhaler is holding a prescription drug on behalf of his family, and an OCCL inspector expects the club to show who gave it, to whom, when, on whose authority, and whether the person holding it was certified to. The same standard covers sending a sick child home, an emergency action plan for a seizure or a severe allergy, and whether every staff certification on site is still current.

Kept on paper, none of that can be checked before an inspection, cannot warn anyone that a physical exam lapses in three weeks, and cannot itself stop an uncertified staff member from giving a dose. That is the gap this module exists to close.

Who uses it

Who can do this

• Front-line staff
• Site director
• Regional director
• Organisation admin
• Super admin

The screen checks nothing beyond being signed in. It shows every button, on all eleven tabs, to a staff member and a regional director too, and both are refused every one.

Reading is open to all five roles above. Saving almost always needs a narrower group: site directors, organisation administrators and super admins. Two things break that pattern in opposite directions. A regional director can read everything in the module except a member's emergency action plans, which are hidden from that role alone. And the one save a staff member is genuinely allowed to make, recording that a dose was given, has no button anywhere in PTRS.

An OCCL auditor's account has nowhere to go here at all: the one screen meant for that role is reachable from nothing in the product, and every other tab in the module shuts the role out before it gets that far.

Every button is shown to two roles who cannot use it

The widest gap found anywhere in the portal between what a screen shows and what it allows

A staff member or a regional director signed in to Health & Safety sees the same Register Medication, Edit, Return, Record New Illness, Add Certification, Renew, Create, Activate and Deactivate buttons a site director does, across all eleven tabs. Every one of them refuses the two roles, with a message saying the account cannot do this.

The one exception runs the other way. Recording that a dose was given is the single save in this module a staff member's account is genuinely allowed to make, and it is the one save with no button at all.

A day in the life

Later, Tom Bradley, the site director, tries to fix the problem underneath Denise's afternoon. He wants to give her the certification that would let her give a dose under her own name. He opens Staff Certifications, selects Add Certification, and picks the form's own first choice, OCCL Medication Administration. PTRS refuses it. He tries CPR. Refused. He tries five more of the eight choices on offer. Only First Aid is accepted, and it is not the certification that matters here.

What PTRS does for you

• Keeps a full record of every medication stored at a site: its name, dosage, storage location, expiry, prescriber, pharmacy, and the parent's and physician's authorisation
• Blocks a dose on four separate conditions and names the exact one that failed: not active, expired, no parent authorisation on file, or, for a prescription, no physician authorisation on file. This is the most carefully built check anywhere in PTRS, even though no screen can reach it yet. See what this module can and cannot record
• Checks a medication's type against the site's own medication policy before accepting the record, provided the site has set one
• Records an illness with its symptoms, the first aid given, and whether a parent was told
• Genuinely stops a child returning to the club the same day after a pickup was recorded, checked automatically the next time that child is checked in. It is the one safety rule in this module that runs start to finish, across two different parts of PTRS
• Holds a full emergency action plan for an allergy, asthma, diabetes or seizure, with triggers, mild symptoms, severe symptoms and response steps as their own required fields. No other module in PTRS asks for this much structure
• Holds an individualised care plan with its own note for what a staff member on the floor should watch for
• Marks a staff certification Expired or Expiring Soon on its own, worked out from today's date each time the page loads

A check this list would otherwise include

A once-a-day check meant to flag a physical exam, a consent form or a certification before it lapses has never actually run, on any organisation, since the day PTRS was built. See what happens on its own.

What stays your job

• Record on paper that a dose was actually given, with the time and a witness, since PTRS has no screen for it at all
• Get the certification that would authorise someone to give medication recorded somewhere outside PTRS, since only First Aid can be added here
• Know that a rescue inhaler and an auto-injector cannot be filed under their real route. PTRS will only accept oral, topical, nasal or rectal
• Record and act on a hospital transport outside PTRS, and raise it as an incident too, since neither that outcome nor a refused entry can be saved on an illness record
• Check a family's signed consent against what a specific medication needs yourself. PTRS works out which consents a medication requires and never compares that against what is on file
• Correct a mistyped chronic condition, medication or physical limitation by removing it and adding it again. Nothing on a member's health record can be edited
• Add or correct an immunisation record or a health document outside this module. Neither can be added from any screen here
• Watch for a lapsing physical exam, consent form or certification yourself, since the one check built for this has never run
• Tell Delaware's Division of Public Health about a contagious illness yourself, by phone or letter. PTRS keeps a private note and tells no one
• Keep your own record of a site's AED location, its last radon test and its last safety assessment date. PTRS stores these fields and nothing ever reads them back

What has been built

Eleven tabs make up Health & Safety, plus two more that appear on a member's own record.

Screen	What it is	What it can do today
Dashboard	Summary cards: active plans, expiring medications, certification coverage, urgent actions	Loads. The certification coverage card stays near zero because two of the three certifications it tracks cannot be created
Medications On-Site	Register, edit and return a medication; read the administration log	Registering, editing and returning all work for four of nine routes. The administration log can never be written to
Expiring Alerts	Medications within a set number of days of running out	Works, computed live. No screen lets you change the window from 30 days
Illness Records	Record an illness and its outcome; record parent notification and pickup	Works for three of five outcomes. The two most serious are refused
Emergency Plans	Create, edit, activate and archive a plan for an allergy, asthma, diabetes or seizure	Works in full
Care Plans	Create, edit, activate and archive an individualised care plan	Works, but is never shown on a member's own record
Staff Certifications	Add and renew a certification	Adding works for one of eight certification types. Renewing works for any certification already on file
Staff Training	A compliance matrix by staff member	Belongs to Staff, not this module. See below
Site Health Profile	A site's medication policy, safety equipment, nearest hospital and licensing details	Works. Only the medication policy tier changes anything else on screen
Enrollment Readiness	Whether a member's paperwork is complete enough to enrol	Works
Member Health	A member's chronic conditions, medications, physical limitations, immunisations and documents	Adding and removing work for three of five record types. Nothing can be edited. Immunisations and documents can only be read

What happens on its own

One check exists in this module, and it has never run. PTRS is meant to look, once a day at 1 am in winter and 2 am in summer by Delaware time, for a physical exam, a consent form or a certification about to lapse, and for a member whose immunisations are not marked up to date.

The daily check cannot start

The check was never finished being wired into PTRS. It is scheduled and shows up in the technical dashboard nobody in a club looks at, and it fails every single time it tries to run, silently, for a reason no screen in the product reveals.

It is one of only two places in PTRS that could ever raise an urgent compliance warning. The other is inside the Compliance module's own engine, which fails before it gets there for its own reasons, so no warning of this kind has ever been raised, anywhere in PTRS.

The consequence shows up outside this module entirely: the Urgent Actions strip on the main dashboard reads this same warning list, and it is permanently empty in every installed copy of PTRS. Not because nothing is expiring, but because nothing can ever write the line that would say so.

One thing does happen on its own. Recording an illness marked contagious quietly writes a private note naming "Delaware Division of Public Health" as the authority to tell. Nobody receives it. See what actually happens.

What it connects to

Connects to	How
Staff	The certification check on giving a dose reads a certification kept here, entirely separate from Staff's own credential tracking and its own expiry check
Members	Chronic conditions, immunisations and health documents hang off a member's record, and enrollment readiness feeds into check-in
Attendance	Recording an illness pickup here is what the next morning's check-in refuses against. It is the one safety chain in this module that runs start to finish across two modules
Compliance	Through the one shared warning list, which neither this module's own check nor Compliance's own engine can ever write to
Centers	A site's medication policy, held on its profile in Centers, is checked the moment a medication is registered here, the only place in PTRS that check runs

Not yet available

Recording that a dose was given

The write, its check, its record of who gave it and its place in the product all exist, correctly built, on the server. Nothing in the product calls any of them. There is no form, no dialog and no button anywhere that records a medication administration.

Seven of the eight choices on the Add Certification form

The form offers OCCL Medication Administration, CPR, First Aid, AED, Concussion Protocol, Bloodborne Pathogens, Food Safety and Other. Only First Aid is saved successfully. The other seven, including the form's own default choice, are refused the moment they are submitted. The certification this module's dose check actually looks for is not offered at all.

Five of the nine medication routes, including an inhaler and an injection

The Route choice on register and edit offers nine options. Only oral, topical, nasal and rectal are saved successfully. An inhaler and an injection, the two forms a club is most likely to hold, are both refused, along with eye drops, ear drops and a nebuliser.

The most serious illness outcome

The Disposition choice on an illness record offers five options. Two are refused: a hospital transport, and a refused entry. A hospital transport is the outcome a licensing inspector is most likely to ask to see, and it is the one this form cannot save.

The Adverse Reaction column

The Administration Log table shows an Adverse Reaction column. The value it reads was never sent by anything on the server, so the column reads "None" for every row it could ever show, whether or not one occurred.

Editing a member's health record

Chronic conditions, current medications and physical limitations can be added and removed, never edited. Immunisation records and health documents can only be read: neither can be added or edited from any screen.

A place for an OCCL auditor to work

One screen in this module is meant for an OCCL auditor's account and is reachable from nowhere in the product. Every other tab in the module refuses the role before it gets that far, so an auditor signing in to PTRS has no Health & Safety screen at all.

Where to go next

Do a task:

• Work the medication screens, register, edit and return a medication, and see which routes are refused
• Work the illness, emergency plan and care plan screens
• Work the certification, site health and member health screens

Look something up:

• Medication and certification fields, every field on the safety-critical screens, with what it actually requires
• Who can do what with health and safety records, and whether anything in the product actually reaches it

Understand why:

• What Health & Safety can and cannot record

When something goes wrong: Health & Safety troubleshooting.