A hospital administrator account approved for your hospital
For hospital administrators
Operate your hospital console
Manage people, wards, access and integrations inside one hospital boundary. Platform-wide controls remain out of reach.
- Staff
- Enrolment
- Wards
- Usage
- Records
Before you begin
Three things to have ready
Your authenticator or current security setup
Authorisation from your hospital for staff and integration changes
Know the workspace
The screen at a glance
The navigation and information shown here mirror the role you selected. Your permissions determine which actions are available.
Staff directory
- 01
Sign in and confirm the hospital banner
Open the shared console URL. Your session determines which console appears. Confirm the teal Hospital console label and hospital name before making changes.
CheckpointThe banner names the hospital you intend to administer. - 02
Invite or approve staff
Use Enrolment to create a single-use code, approve a pending join request or perform a controlled bulk import. Share codes through your approved channel; they cannot be recovered after display.
- 03
Maintain the staff directory
Use Staff to reset access, change status or transfer a caseload. Suspend rather than delete a clinician whose audit history must remain linked.
CheckpointEvery active person has the correct role and hospital. - 04
Configure wards and visibility
Create wards, assign staff and verify who can see which cases. Keep free-text ward names aligned with the configured directory so adoption reporting stays meaningful.
- 05
Review adoption and usage
Use Adoption to monitor uptake and completed decisions by ward. Use Usage to review monthly limits and enabled hospital-facing features. Suppressed small numbers are not zero.
- 06
Manage integrations and exceptional access
Create integrations as drafts, test them, then activate intentionally. Review MedBoard access requests and grant only one case, one reason and a bounded duration when justified.
- 07
Export your records
Use Records for your hospital’s full audit trail and data export. Investigate unexpected access, enrolment, status and integration events promptly.
CheckpointAudit entries explain who changed what and why.
Good practice
Do this
- Check the hospital name before every staff or access action.
- Use single-use enrolment codes and approved delivery channels.
- Review active staff, wards and access grants on a regular schedule.
Avoid
Pause before this
- Do not reuse or email enrolment codes in open distribution lists.
- Do not activate an integration before its destination and scope are verified.
- Do not infer staff performance from small or suppressed adoption counts.