GlossCap

Platform reference · Epic EHR · Hyperspace training · HealthStream · HIPAA workforce training · Joint Commission · WCAG 2.1 AA

Epic EHR training captions: Hyperspace walkthroughs, clinical workflow video, and Joint Commission readiness

Epic Systems is the dominant electronic health record in the United States — present in more than 37% of US hospitals and responsible for more than half of patient health records in the country. Every hospital that runs Epic must train its clinical and operational staff on how to use it: at go-live, at every semi-annual upgrade, when new modules are activated, and when staff join or change roles. The training content produced by Epic training teams and Epic implementation consultants is almost entirely screen-capture video — Camtasia recordings of Hyperspace workflows, Articulate Storyline modules with embedded Hyperspace simulation, Loom recordings of configuration walkthroughs — and it carries the highest combined medical-plus-software proper-noun density of any training video type. The result is that generic STT auto-captions are systematically unreliable on Epic training content: they mis-transcribe Epic module names, SmartSet names, dot phrases, Dragon Medical commands, clinical workflow identifiers, and the medical vocabulary that the videos discuss in context. For hearing-impaired clinical staff who rely on captions to access mandatory Epic training, this creates a HIPAA § 164.530(b) workforce-training documentation gap and, at public hospitals, an ADA Title II WCAG 2.1 AA compliance failure.

TL;DR

Epic training video — Hyperspace walkthroughs, go-live training, upgrade training, SmartSet/SmartPhrase configuration tutorials — is screen-capture content with dense Epic-specific and medical vocabulary that generic STT systems fail on consistently. The distribution platforms vary by hospital: Epic training content is most commonly distributed via HealthStream, Relias, SharePoint/Microsoft Stream, or a hospital-specific LMS alongside the Epic Learning Home portal. Caption files (SRT for most platforms, VTT for Stream-on-SharePoint and Workday Learning) must be produced externally — none of these platforms auto-caption Epic training content with Epic-vocabulary accuracy. The compliance framework: HIPAA § 164.530(b) (mandatory workforce training documentation for all covered-entity staff), Section 1557 § 92.207 (effective communication for covered healthcare providers), ADA Title II (for public hospital systems), and Joint Commission HR.01.05.03 (competency-based training with documented completion). Glossary-biased captioning fed with Epic module names, SmartSet names, Dragon commands, and the clinical vocabulary in use at the specific hospital produces caption accuracy that satisfies all four frameworks simultaneously.

Epic training content types and volume

An Epic implementation at a mid-sized hospital system generates a training library measured in hundreds of hours of video. The training content falls into several categories:

Caption distribution platforms for Epic training

Epic training video is not distributed through a single platform — hospitals use a mix of systems depending on their L&D infrastructure:

HealthStream

HealthStream is the most common dedicated clinical LMS for required training distribution at US hospitals. Epic onboarding courses, annual HIPAA awareness training, and regulatory-required compliance modules are frequently hosted in HealthStream and assigned via HealthStream learning campaigns. Caption upload in HealthStream: SRT/VTT sidecar attached to the HealthStream course media resource. See the HealthStream captions reference for the platform-specific upload workflow.

Epic Learning Home

Epic Learning Home is Epic's built-in training portal that lives within the Epic Hyperspace application itself. Training coordinators can create e-learning content, link to external video, and assign training from within Learning Home. Video content in Epic Learning Home follows the same SRT/VTT sidecar approach — a caption file is uploaded alongside the video, and Learning Home's built-in player renders the CC track. For hospitals that distribute all Epic training through Learning Home rather than a third-party LMS, the caption workflow is entirely within the Epic tenant.

SharePoint / Microsoft Stream

Many hospital systems that run M365 distribute Epic training videos as SharePoint pages with embedded Stream-on-SharePoint video. Microsoft Stream on SharePoint supports VTT sidecar upload for caption tracks. The VTT is managed in SharePoint's video player settings; the CC toggle appears in the Stream player embedded in the SharePoint page. For M365-heavy health systems, this is often the lowest-friction distribution path for ad-hoc Epic training walkthroughs (especially Loom and Teams-recorded walkthroughs that auto-land in Stream).

Workday Learning

Health systems that run Workday HCM alongside Epic (a common combination at large health systems) may distribute Epic onboarding training through Workday Learning. The VTT caption-upload workflow in Workday Learning applies; see the Workday Learning captions reference.

SCORM packages distributed via multiple LMS

Many Epic training modules are packaged as SCORM 1.2 or SCORM 2004 packages built in Articulate Storyline or Camtasia with embedded Hyperspace simulation screencasts. The caption track is embedded in the SCORM package at authoring time. SCORM packages run in whichever LMS the hospital uses (HealthStream, Relias, Cornerstone, SAP SuccessFactors, a home-built SCORM player); the caption quality is determined by the authoring-time caption import, not by the LMS. A SCORM package of an Epic Hyperspace walkthrough that uses Articulate's built-in auto-caption and has not been reviewed for Epic vocabulary accuracy will fail WCAG 2.1 AA SC 1.2.2 on nearly every Epic-specific term.

The Epic vocabulary failure mode — why generic STT produces wrong captions

Epic training video is among the most challenging content for generic STT systems because it combines three distinct vocabulary failure domains simultaneously:

Epic application vocabulary

Dragon Medical / speech recognition integration vocabulary

Many hospitals run Dragon Medical One (Nuance/Microsoft) integrated with Epic for physician documentation. Epic training for physicians who use Dragon Medical includes Dragon Medical command vocabulary — "Insert Dragon Encounter," "Show microphone," "Go to sleep," "New line," "Select [word]," "Scratch that," "Bold [word]," "Cap on / Cap off" — as well as the medical vocabulary that Dragon Medical processes for clinical note dictation. When Epic training video walks through Dragon Medical integration, the training content references Dragon commands by name, and generic STT systems that have not been trained on Dragon's specific command vocabulary produce consistent transcription errors.

Clinical vocabulary specific to the hospital's specialty mix

Epic training content at a tertiary academic medical center references a different vocabulary subset than training content at a community hospital or a specialty-focus facility. Common failure categories:

Joint Commission HR.01.05.03 and Epic training documentation

The Joint Commission's Human Resources standard HR.01.05.03 requires that hospitals assess and document staff competency for their job responsibilities. For clinical staff using Epic, this means that Epic training competency — the ability to correctly use Hyperspace for documentation, order entry, medication administration, care planning, and communication — must be documented. Epic training video is the primary mechanism for initial and ongoing competency training; completion records in HealthStream, Epic Learning Home, or the hospital's LMS are the audit artefact that survives a triennial Joint Commission survey.

The captioning connection: during a Joint Commission triennial survey, the survey team may request evidence that training was provided in an accessible format to staff who required accommodation. If hearing-impaired clinical staff completed Epic training that included video with inaccurate captions, the hospital may not be able to demonstrate that the training was "appropriate" for those staff members under HR.01.05.03's competency standard. Accurate caption tracks on Epic training video are part of the complete competency-training-documentation package.

The same logic applies to ACGME (Accreditation Council for Graduate Medical Education) requirements for residency and fellowship programs that use Epic for resident documentation training: ACGME program requirements include accessible educational resources for residents with disabilities.

HIPAA workforce training and Epic training video

HIPAA § 164.530(b) requires covered entities (hospitals, health plans, healthcare clearinghouses) to "train all members of its workforce on the policies and procedures with respect to protected health information." Epic training video frequently overlaps with HIPAA training content in two ways:

  1. HIPAA modules embedded in Epic onboarding training. Most hospital Epic onboarding programs include a HIPAA awareness module — explaining the Privacy Rule, Minimum Necessary standard, the patient's right of access under § 164.524, and the hospital's specific HIPAA policies. These modules are often video-based and hosted in HealthStream or Learning Home alongside the Hyperspace workflow training. They carry explicit HIPAA § 164.530(b) documentation requirements.
  2. Epic Hyperspace training that inherently involves PHI handling. Training on Epic documentation, order entry, and results review involves demonstrating how to handle PHI correctly in Hyperspace. The training content itself teaches HIPAA-relevant skills (de-identification, Break-the-Glass access logging, patient proxy management, release of information workflows). Hearing-impaired staff who cannot access this content via accurate captions may not receive the "appropriate" HIPAA training that § 164.530(b) requires.

The practical guidance: every video in the Epic training library that covers HIPAA awareness, PHI handling, or privacy/security compliance should be captioned to WCAG 2.1 AA SC 1.2.2 accuracy before being assigned via HealthStream or Learning Home as required training. The HIPAA training documentation record must include evidence of accessibility — and an SRT/VTT file attached to the HealthStream course resource serves as that evidence.

See GlossCap pricing

The GlossCap Epic glossary approach

Because Epic vocabulary is standardised across all Epic customer sites (every Epic site uses the same module names, the same SmartSet framework, the same InBasket architecture), a shared Epic base glossary handles the majority of Epic-specific vocabulary failure modes. The hospital-specific layer — custom SmartSet names, custom order set names, hospital name and department names, the specific drug formulary in the Willow build, the specific integration partner names (Vocera, Imprivata, QGenda, etc.) in use — is added as a tenant-specific overlay. The result is a two-layer glossary:

This glossary structure applied to GlossCap's Whisper-large glossary-biased decoding produces caption accuracy on Epic training content that satisfies WCAG 2.1 AA SC 1.2.2's "accurately convey the audio" standard for the vocabulary the training discusses — the standard that generic STT output routinely fails.

FAQ — Epic EHR training captions

Does Epic Learning Home auto-generate captions for uploaded video?

Epic Learning Home does not auto-generate speech-to-text captions. Caption files (SRT or VTT, depending on the Learning Home version) must be produced externally and uploaded to the Learning Home course or e-learning resource alongside the video. For Articulate SCORM packages hosted in Learning Home, captions are embedded in the package at authoring time. For raw video files uploaded to Learning Home, a separately uploaded caption file is required. The absence of auto-captioning in Learning Home means that most Epic training video that has not been deliberately captioned plays without any caption track.

Is HealthStream or Epic Learning Home the better platform for distributing captioned Epic training?

Either works for caption distribution; the choice depends on the hospital's infrastructure. HealthStream is better for required, compliance-tracked training that must be assigned to specific role populations and have completion records for Joint Commission and HIPAA documentation purposes. HealthStream's SRT sidecar upload produces a CC toggle in the HealthStream player. Epic Learning Home is better for just-in-time Epic workflow reference content (upgrade FAQs, department-specific workflow guides) that doesn't need formal completion tracking. For a hospital that uses both, the practical approach is: required training (HIPAA, annual competencies, onboarding) in HealthStream with captioned video; workflow reference in Learning Home with captioned video; screen-capture walkthroughs for the Epic training team's own reference in SharePoint/Stream with VTT sidecars.

Why do Articulate auto-captions fail on Epic training video specifically?

Articulate Storyline 360's built-in auto-caption generator uses the same generic speech-to-text model that all general-purpose STT systems use — it has no awareness of Epic's proprietary vocabulary. SmartSet names, InBasket, BPAs, Dragon Medical commands, EpicCare module names, and the medical-plus-clinical-informatics vocabulary that Epic training narrators use are all out-of-distribution for the Articulate auto-caption model. The result is substitution errors on nearly every Epic-specific term — "SmartSet" → "smart set" or "smart sit," "InBasket" → "in basket" or "embed basket," "ASAP module" → "A SAP module," "Stork" → "stork" or "stark," "Beaker" → "beaker" or "baker." For a Hyperspace workflow tutorial that references 15-20 distinct Epic-specific terms in a 5-minute video, these errors are pervasive enough that the caption track is actively misleading to a hearing-impaired clinician relying on it for training.

What captioning obligation exists for Epic patient-portal video (MyChart)?

MyChart is Epic's patient-facing portal. Video content on MyChart — patient education videos, procedure prep instructions, telehealth visit recordings — is public-facing content that carries ADA Title III obligations for private hospitals (place of public accommodation) and ADA Title II for public hospitals. Section 1557 (ACA nondiscrimination, 2024 HHS final rule) applies to covered healthcare providers' web and mobile content including MyChart, requiring WCAG 2.1 AA SC 1.2.2 for all prerecorded video. Patient education video on MyChart is not "training video" in the L&D sense, but it carries the same WCAG 2.1 AA captioning standard — and its vocabulary (diagnosis explanations, procedure descriptions, medication instructions) has the same medical-terminology failure mode as clinical staff training video.

How does captioning for Epic training video compare to captioning for non-Epic healthcare training?

Epic training video has higher vocabulary specificity than most other healthcare training content types. General HIPAA awareness training or hand-hygiene compliance training has relatively lower proper-noun density — the compliance vocabulary is standardised and appears in generic STT training data. Epic Hyperspace training is different because it references a proprietary software system's specific architecture: SmartSet names and configurations differ between Epic sites; Dragon Medical commands reference a separate proprietary vocabulary; the navigation elements (InBasket, Navigators, Storyboards, Snapboard) are Epic inventions without common-language equivalents. The combination of medical vocabulary (drug names, procedure names, diagnostic codes) with Epic-proprietary vocabulary (module names, Smart* feature names, integration partner names) creates the highest compound vocabulary failure rate of any training content type we've analysed.

Further reading