Health screening
Fitness-for-work and fatigue screening results, by worker and project.
Part of Workforce in the register catalog.
- Register ID
health_screeningUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- An eventSomething that happened at a point in time.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1Current version.
Standards
This register holds records these standards and laws ask for. Holding them does not by itself certify compliance.
- ISO 45001Occupational health and safety management systems
- Fair Work Act 2009National employment standards and modern awards
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- SignOnSitePartial
- SitematePartial
Fields
13 fields: 5 required, 7 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- external_idText
Stable identity of the source record (Assignar form-result id, cast to text).
Example:
HS-2026-3301- source_systemText
Originating system;
ASSIGNARtoday and the only system column the frozen universe names.Example:
ASSIGNAR- occurred_atDate and time
When the screening record was submitted; the event time and the retention clock start.
Example:
2026-07-14T22:00:00Z- workerNumber
The worker the screening is about; the required subject anchor.
Example:
5504- form_titleText
The matched Assignar form's title — which screening instrument this fact is.
Example:
Fatigue and Fitness for Work Declaration
Optional
Present when the source system records them.
- form_idNumber
The Assignar form-template id (87, 430, 211 for the three title patterns), the stable twin of
form_title.Example:
87- projectNumber
The project the screening was recorded against, where the source gives one.
Example:
8101- financial_periodDate
The accounting period the screening falls in, derived from
occurred_at.Example:
2026-07-01- screened_onDate
The screening's own date where the form states one (the reader's
dateanswer /diary_datefallback).Example:
2026-07-14- fatigue_self_assessment_scoreNumber
The fatigue self-assessment value, where the form carries one.
Example:
2- control_measures_requiredText
Control measures the screening identified as required.
Example:
None required- confirmationTrue or false
Whether the worker confirmed the declaration on the form.
Example:
true
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- attributesGroup of fields
Every remaining form answer, keyed by the tenant's own question text, plus
_raw_metadataat rest.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "confirmation": true, "control_measures_required": "None required", "external_id": "HS-2026-3301", "fatigue_self_assessment_score": 2, "financial_period": "2026-07-01", "form_id": 87, "form_title": "Fatigue and Fitness for Work Declaration", "occurred_at": "2026-07-14T22:00:00Z", "project": 8101, "screened_on": "2026-07-14", "source_system": "ASSIGNAR", "worker": 5504}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/health_screening/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.