A separate active MedBoard platform administrator account
For MedBoard platform administrators
Operate the MedBoard platform console
Run the hospital fleet, release controls and assurance signals without routine access to hospital patient records.
Who this is forAuthorised MedBoard platform administrators
- Fleet
- Hospitals
- Assurance
- Controls
- Audit
Before you begin
Three things to have ready
An enrolled time-based authenticator
A documented change or support reason for any operational action
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.
Platform console
KAFleet health · last 30 days
Hospitals8
Healthy8
Open gates0
Demo General HospitalService healthy · last activity 4m agoActive
Release assuranceRequired evaluation and runtime checksPassed
Operator reviewQuarterly access review due in 12 daysPlanned
- 01
Sign in and complete step-up authentication
Open the shared console, enter your platform credentials and the current authenticator code. Confirm the violet Platform console label before proceeding.
CheckpointThe console shows fleet data, not a hospital’s staff directory. - 02
Review fleet health
Start on Fleet. Check hospital status, activity, spend and service health. Aggregated or suppressed values intentionally prevent routine patient-level drill-down.
- 03
Onboard or change a hospital
Use Hospitals to create a tenant, generate its first administrator activation code, suspend a site or reactivate it. Record the reason for every state change.
- 04
Check assurance before release decisions
Use Assurance to inspect required evaluation checks, safety gates and calibration. A healthy service alone is not evidence that a clinical claim still holds.
CheckpointRequired gates are current and tied to the intended release. - 05
Apply feature and quota controls
Use Feature control to manage site capabilities, limits and cost controls without redeploying. Change the smallest possible scope and confirm the affected hospital.
- 06
Use break-glass only by request
Request access to one case for one support reason and bounded time. The hospital must approve it. Routine platform administration cannot read patient records.
- 07
Audit, manage operators and offboard safely
Review platform-visible events, keep operator accounts current, and offboard in the required order: export, tombstone, then purge.
CheckpointNo destructive offboarding step occurs before the approved export.
Good practice
Do this
- Use the smallest change scope and record the operational reason.
- Treat assurance gates as release prerequisites, not dashboard decoration.
- Keep platform and hospital administrator accounts separate.
Avoid
Pause before this
- Do not ask hospitals to share patient data through ordinary support channels.
- Do not bypass a failed safety or readiness gate.
- Do not purge a hospital before export and tombstone are complete.