FDE Interview Questions: The Health Data Hub
Examine common interview follow-up questions about the Health Data Hub design. Evaluate feeds that appear healthy despite underlying failures, incorrect patient record associations, delayed source reports, and undetected changes in data semantics. Assess outage recovery, backfill processing, and recovery acceptance criteria using verifiable evidence.
We'll cover the following...
"The connector is reporting a healthy status again. Can the National Health Data Office consider the workflow recovered?" One patient record association remains unresolved, and an earlier report is queued for replay. Determine which workflows can safely resume, assign owners to unresolved exceptions, and identify the evidence required to confirm recovery in the receiving workflow.
What a healthy feed actually establishes
Identify the affected source time range, reports, destinations, authoritative report versions, unresolved holds, and downstream impact. A healthy connection does not confirm complete source ingestion or safe access for authorised consumers.
Structure each interview follow-up response around five steps:
Clarify the changed constraint.
State the safety invariant that must hold throughout recovery.
Describe the specific design changes required.
Identify who is responsible for each recovery action.
Specify the evidence required to confirm recovery.
For example: "The receiving system is reachable, but report version ordering remains unresolved. An older report must not overwrite a newer, authoritative correction. I would validate source-confirmed revision ordering before replay and verify that the destination retains the correct report version. Operations manages replay, the source owner confirms which report version is authoritative, and the receiving owner approves workflow recovery."
Recovery must be verified against the current system state, not just the completion of queued processing. The Health IT Playbook addresses governance, data integrity, contingency planning, test-result follow-up, change management, training, and support as part of safe health IT implementation. Recovery acceptance requires confirmation from the responsible workflow owners, supported by infrastructure and downstream verification.
When the patient association is wrong
The SAFER Patient Identification Guide focuses on ensuring that information entered into or displayed in an EHR is associated with the correct patient. The Test Results Reporting and Follow-Up Guide covers the safe communication and management of test results. Patient identification and test-result follow-up require separate verification.
Preserve source-scoped patient identifiers throughout the integration workflow. Morgan coordinates the review of unmatched records and potential duplicate patient matches through the approved identity authority. Integration workers must not merge patient records based solely on matching local identifiers or similar demographic and clinical data.
Hold deliveries that depend on an ...