Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: Healthcare

Walkthrough playbook: Healthcare

A walkthrough of CMDash for healthcare organizations, run in the live sandbox in about 18 minutes. It is written for the CMDash sales team and for partners who present the product.

Who this is for

A security or compliance lead at a provider group, a health plan, a health-tech vendor or a business associate. They answer to HIPAA, are being asked for HITRUST, and field security reviews from every health system and payer they work with.

What they are tired of

  • "Every health system, payer and partner wants proof we protect patient data, and each one asks in its own format."
  • "We documented the HIPAA safeguards, and now we are documenting the same things again for HITRUST."

What it costs them: The same safeguards written up several times a year, and a risk analysis that is out of date when the reviewer asks for it.

The line to open with: "Answer every payer and partner security review from one record." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.

The walkthrough

1. Start on Home (2 min)

  • Go to: Overview → Home (/home)
  • Show: The grade, what needs attention and the frameworks in scope.
  • Say: "One page for where you stand. I'll go from here to HIPAA, then to how HITRUST reuses it."

2. HIPAA, control by control (4 min)

  • Go to: Compliance → Frameworks (/compliance), open HIPAA
  • Show: The Security Rule safeguards as controls, each with an owner, a status and evidence.
  • Say: "The safeguards are tracked as controls with a named owner and the evidence behind each. This is what you show when someone asks how you protect patient data." If HIPAA is not in scope in the sandbox, open the framework list and use a framework that is, and say which.

3. Work once, carry it (3 min)

  • Go to: Compliance → Control mappings (/control-mappings)
  • Show: The mapping from HIPAA to HITRUST and NIST CSF.
  • Say: "HIPAA and HITRUST overlap. On Command, a status you record on a HIPAA control carries to the HITRUST and NIST CSF controls it maps to, so the second framework starts part done."

4. Evidence from IT's tools (3 min)

  • Go to: Compliance → Evidence (/evidence), then Integrations → Connections (/integrations)
  • Show: An evidence item with its source, then the connected tools.
  • Say: "MFA, patching and endpoint evidence comes from the tools your IT team already runs, with a date on it, instead of a screenshot taken the week before the review."

5. The risk analysis (3 min)

  • Go to: Security → Risk register (/risks)
  • Show: Risks with owners, treatment plans and loss estimates.
  • Say: "The Security Rule asks for a documented risk analysis. This is one that stays current: each risk has an owner, a plan and a figure."

6. Business associates and reviewers (3 min)

  • Go to: Security → Vendors (TPRM) (/vendors), then Settings → External assessors (/settings/assessors)
  • Show: The vendor register, then the assessor grant.
  • Say: "The business associate list lives here with owners and criticality. And when a reviewer or assessor needs to look, they get a scoped, expiring, read-only login."

Questions you will get

"Can we store PHI in CMDash?"

CMDash holds the record of the security program: controls, statuses, risks and evidence about safeguards. It is not a system for patient records, and they should not upload PHI as evidence. For what CMDash commits to contractually, send them to the Trust Center at www.cmdash.com/trust and to sales; do not improvise an answer about a business associate agreement.

"Does this make us HIPAA compliant or HITRUST certified?"

No. It keeps the controls, evidence and risk analysis those rest on. HITRUST certification is issued through a HITRUST assessor.

"We are a small practice."

Then Command is more than they need on day one. Starter tracks HIPAA with a posture grade and risk register, and Essentials adds board reports. Say so.

"How many vendors can we track?"

The register holds five on Starter to Command. Continuous monitoring and questionnaires for a longer business associate list are part of third-party risk management on Enterprise.

Command. The reasons, as they appear at the foot of the public page:

  • The framework crosswalk engine: work once against HIPAA and the status carries to the HITRUST and NIST CSF controls that overlap.
  • Audit evidence packages: every control's evidence in one bundle for an assessor, a payer or a health system.
  • Unlimited integrations, so MFA, patching and endpoint evidence all come from the tools IT already runs.

Enterprise adds monitored third-party risk management for a long business associate list.

Next step: Offer the 30-day trial on Command and ask which review is due next. Book a follow-up two weeks before it.

This page is the product manual, published from the repository at docs/user/playbooks/healthcare.md. Customers read the same text inside CMDash under Help. Last updated November 15, 2026.

Walkthrough playbook: Healthcare — CMDash Docs