AA

Smart Tools & Care Everywhere – Lecture Review

Creating a Placeholder SmartPhrase

  • Begin by building a personal placeholder SmartPhrase.
    • Include your own name in the title so you can retrieve it easily.
    • Purpose: A quick “stub” you can later refine inside the full SmartPhrase tool.
  • Once the phrase is inside the dedicated editor you gain:
    • Many more formatting options (fonts, tables, section headers, etc.).
    • Ability to expand, restructure, and polish content before sharing with others.
  • Practical tip:
    • Think of the placeholder as “rename-and-claim.” You claim ownership first, then flesh it out later.

Pulling External Results with Care Everywhere

  • Question raised: “Why can’t we pull in Care Everywhere results into our patient chart?”
  • Clarification by trainer:
    • It is possible if everything is configured correctly.
  • Key configuration elements
    • Use universal component names / codes so data map cleanly between systems.
    • Acts like a shared “Rosetta Stone.”
    • Example standard: SNOMED (mis-heard as “Snowman” in audio).
    • Ensure both sending and receiving orgs tag data with the same discrete code set.
  • Conceptual model
    • Care Everywhere merely transports data; it does not transform it.
    • Correct mapping at both ends → discrete results (e.g., labs, imaging) become available to SmartLinks/SmartPhrases.
  • Action items
    • Verify your organization’s config with an Epic Technical Services (TS) contact.
    • Many features may already be live or coming “around the corner.”

User-Level vs. System-Level Parameters

  • Earlier exercise: Editing user-level parameters (custom to the individual).
  • Current focus: System-level parameters (shared enterprise-wide).
    • Add a new line in your code snippet.
    • Example shown: Pulling CT scan results.
    • Components embedded here are pre-configured.
    • End user does not modify them; they auto-populate.
    • Result becomes part of a system SmartPhrase available to all clinicians.

Embedding SmartLinks & Components

  • Analyst workflow
    • Write the narrative portion manually.
    • Insert appropriate SmartLinks to surface discrete data (labs, vitals, imaging).
  • Distinction
    • Narrative text ≠ SmartLink. You can’t “pull” narrative, you compose it.
    • SmartLinks pull structured data instantly.

Quick Heuristic From the Instructor

  • When in doubt about feature availability:
    • “They’ve either already done it and you don’t know, or it’s right around the corner.”
    • Always loop back to Epic TS for definitive answers.

Upcoming Class Flow

  • Reference points mentioned
    • Workbook page 69 – mid-page marks start of system parameters section.
    • Lunch scheduled at 11:45.
  • Planned timeline
    • Finish two-thirds of Flow Sheets chapter before lunch.
    • Post-lunch: Matt will lead review.
    • A 10-minute break, then a game of “What Beats Rock Naturally,” followed by a session in BlueJeans.
  • Exercises
    1. “Easy” practice exercise (immediate).
    2. An optional “if-you-have-time” advanced exercise.

Practical & Ethical Implications

  • Consistent data mapping protects data integrity and patient safety.
  • Shared system phrases reduce documentation variance → better quality metrics.
  • Encourages interoperability: a foundational goal in modern health IT.