OWHS

The entity map

spec v0.2 draft · nineteen names on one page · drawn from the specification's data model

The data model as one picture. Read it left to right: the organisation and what it provides, the pseudonymous worker and every record that hangs off that pseudonym, the shared definitions those records point at, and on the right the report used for employer-visible aggregate results.

figure · the entity map, drawn for v0.1 and unchanged in v0.2seventeen entities · two reserved names
OWHS entity map, drawn for v0.1 and unchanged in v0.2 Nineteen boxes on a grid: organisation-level entities across the top, the worker pseudonym and its individual-level records in the middle, the shared definitions along the bottom, the aggregate report and benchmark release on the right, and two reserved names. Solid lines are structural references, dotted lines are the aggregation flow into the report, dashed lines mark reserved names. has scopes groups reports provides used via subject of resolved by recommends informs enacted in measures, scores produced under tagged with aggregated into aggregated into composed from scoped to references maps reserved reserved Organisation the employer, outer boundary OrgUnit team; smallest unit reported BenefitEntitlement what support the workforce has BenefitUtilisation counts per service per period WorkerPseudonym opaque, per employer, banded AbsenceEpisode one sickness absence ReturnToWorkOutcome what happened after WorkplaceIncident reserved, no fields yet OHEpisode referral to fitness opinion ReasonableAdjustment Equality Act s.20 adjustment AggregateReport aggregate results for release DisabilityParticipation org level, banded, n at least 10 InstrumentAdministration scores and band, never items WellbeingObservation one item, one occasion BenchmarkRelease comparison set, composition shown RiskAssessment reserved, no fields yet Crosswalk to HSE MS, ISO 45003, whiu: ConstructDomain one health-domain vocabulary MeasurementContext what makes scores comparable
organisation level individual records; field-level disclosure rules apply aggregate reporting output shared definitions reserved, no fields yet structural reference aggregation flow

Individual instrument results are never employer-visible. Only the expressly classified individual-employer fields may be disclosed at individual grain under the specification's independent-legal-basis condition. The diagram does not grant permission to disclose a record.

one pseudonym, five records

Absence, occupational health, adjustment, observation and instrument result all hang off WorkerPseudonym: opaque, per employer, banded demographics only. Nothing individual is ever employer-visible at that grain.

one vocabulary for both sides

What a survey measures and what a benefit targets are tagged with the same ConstructDomain, so provision and measurement can finally be read against each other. Crosswalk maps it to the HSE Management Standards, ISO 45003 and the WHIU's reserved namespace.

one door out

Absence, outcomes, observations and benefit usage reach the employer only through AggregateReport, with its floor, interval and suppression metadata, and from there into a BenchmarkRelease with its composition disclosed.

The relationships are those of the specification's entity catalogue, section 2; the Mermaid source is in the bundle. The entity table with each purpose and cardinality is on Inside the standard; field tables, privacy classes and code lists are in the full specification.