Hospital Security Questionnaire and MDS2 Response demo
Product security officers answer each hospital from the release's parts list, threat model and pen test, and set straight any hospital told something different. 1:24
What the demo shows
Answers hospital security questionnaires and MDS2 forms from the device's own security evidence
Seven agents read each questionnaire in whatever form it came, pin every question to the layer of the device that answers it, draft from approved answers for that exact software version, and check every draft against the SBOM, the threat model, the pen test summary, the MDS2 and every earlier answer. A contradiction blocks the package until the product security officer settles it; the settled answer becomes the one answer for every hospital, open drafts are refreshed, the MDS2 keeper drafts a revision for document control, and each hospital told the earlier answer gets a correction. Questions with no approved answer go to product security and questions about the hospital's own setup go to the sales engineer; nothing is guessed.
Transcript
- This answers hospital security questionnaires, often hundreds of questions each, for device makers' product security teams.
- Larkmoor Health sent 214; the agents pin each to the pump layer that answers it.
- Every draft is checked against the SBOM, threat model and past answers.
- Six disagree, so nothing can be sent.
- Larkmoor asks if the pump stores patient data. Two hospitals were told no.
- But the SBOM lists an event log database, and that log holds the patient ID.
- The product security officer approves the corrected answer and signs.
- The MDS2 keeper finds four dependent form lines; both hospitals are queued for a correction.
- She reads a sample record before signing; every step is audited.
- One answer for every hospital: six contradictions found, one settled, two corrections queued.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.