Lifecycle of a Hospital - memeree/TITAN GitHub Wiki

A Worker has many attributes, name, age, dob, location - typical stuff that can be captured on a webfor, or curriculum vitae. A Worker also has Qualifications, which enable them to work with certain countries. they can be approved, or queried or approved. A Worker also has Memberships - to Regulatory bodies (assume we'll do a lookup of a data pull from them) to double check if Membership is Current or Lapsed. Lots of these attributees have expiry dates. so these need to have actions 'before expiry' to ensure they remain compliant. A Worker has a Compliance State (Compliant, Non-Compliant (In Progress), or Non-compliant) which can be like an overall state.

Workers can be internal (Temp/Perm Staff), or externally sourced (employment agencies), the cheapest workers are internal, and the external workers are more expensive, and are charged on rate cards, depending on their skill, and time proximity to a shift.

Hospitals. have a general location (postcode/zipcde etc), and can be made up of 1 or more buildings, of which each building has a number of Departments, which can be made up of 1 or more wards. Departments can be spread across multiple wards/buildings. Departments also can be Patient Facing or non-patient facing (Admin/clerical, HR, IT, etc).

Departments or hospitals release shifts, which can be claimed/filled by workers. Departments require the correct skillset, and so will be matched to workers who have corresponding skills; a shift can be filled by one or more skills.

Workers can see a shift at a hospital if they are Compliant, and if they are in an acceptable distance from a hospital, and have the right skills,.

Hospitals have to make sure that shifts are filled by the cheapest worker possible.

The worker shoudl work the shift, but it's possible that they miss the shift due to illness or something, and this gets recorded.

Hopefully. the shift gets worked, and this gets passed to payroll, to process.