Completed missions are easy to count and easy to misunderstand. A rising total may reflect demand, expanded availability or a different mix of cases; it does not by itself demonstrate safer care. For a board overseeing healthcare connectivity, the dashboard should explain the service's readiness, the referrals it could not support and what the organisation learned from its operating experience.
Use measures that fit the stage
Before launch, report foundations: defined scope, partner agreements, qualified staffing, equipment readiness, permissions and completed corrective actions. After operations begin, add activity and process measures with clear definitions. Mixing development milestones and patient activity can make a proposal appear more mature than the evidence supports.
ALFA’s October 2026 whitepaper sets out healthcare workstreams and a staged operating framework. Its present reporting should therefore concern preparation and verified milestones rather than simulated or implied patient-service statistics.
Show the referrals that did not become missions
A completed-transfer count leaves out requests declined, cancelled or directed elsewhere. With appropriate definitions and privacy controls, those categories can help managers understand whether a service is meeting its agreed scope or encountering repeated coordination problems. Record reasons consistently before attempting to interpret trends.
A clinical decision that transport is inappropriate should not automatically be treated as a commercial failure. The board needs to distinguish suitable decisions from avoidable barriers, and qualified clinical oversight is essential to that interpretation.
Define clocks before comparing speed
Response time can begin at the first call, receipt of a complete referral, clinical acceptance or dispatch. Those are different measures. A useful dashboard names its starting and finishing points, explains exclusions and separates stages of the pathway. Otherwise, an apparent improvement may simply reflect a changed definition.
WHO's emergency care framework covers functions across the care journey. It supports a view of performance that examines the connections between services rather than rewarding one segment's speed in isolation.
Treat incident data as learning evidence
WHO's incident reporting guidance warns that such data need careful interpretation. Reporting can reveal hazards and opportunities to improve, but the number of reports alone is not a reliable measure of the underlying harm rate. Increased reporting may reflect a stronger reporting culture or a change in access to the system.
For governance, ask what was reviewed, what action followed and whether the action was checked. A dashboard should connect important findings to responsible owners and closure evidence, while protecting confidential patient and staff information.
Keep publication narrower than oversight
Boards may need detail that public reporting should not contain. Publish defined, appropriately aggregated information with context and clear limitations; avoid identifiable case detail or unsupported outcome claims. A small early service may need particular care because route and timing information can make cases recognisable. The goal is a record that enables informed oversight and honest communication, with clinical performance interpreted by the people qualified to assess it.
