Epic Bridge

How doctors open this guide

Faster routes from Census

1. Select and verify the correct patient, then click Epic Intake beside Add Data. This opens the Epic → somaNotes snapshot instructions directly.
2. If Add Data is already open, click Set up the interim Epic snapshot phrase near the top of the window.
3. For a bookmark or typed address, use /help/epic-smartphrase. No patient information is stored on this help page.

Epic → somaNotes — interim chart intake

The draft proposal's generic .VITALS[24H], .RECENTRESULTS[24H], and .ENCOUNTERNOTES names are not verified in the Avera build. This baseline uses only names found in Avera's in-Epic index and leaves site-dependent labs and notes as explicit stops. That is deliberate: a compact partial snapshot is safer than a phrase that silently omits data or dumps every note in the encounter.

Verified name set: .now, .id, .los, .dol, .vsranges, .meds, .hprobl, and .llcbc3. Test the assembled phrase once on a training patient; if a token renders literally, remove it and reinsert the matching SmartLink from Epic's Insert SmartLink search.

One-time setup in Epic

1. Open SmartPhrase Manager, create a personal phrase named SOMASNAPSHOT (no leading dot), and paste the template above.
2. For the lab stop, insert only the trends you actually act on using Avera's verified .ll<lab>3 family. Keep the stop if the needed aliases are not yet verified.
3. Keep the encounter-notes stop manual until an Avera analyst verifies a compact, signed-note, encounter-scoped SmartLink or report. Do not substitute a guessed all-notes command.
4. On a training patient, confirm every cyan token resolves and that the output is compact enough to review before copying.

Daily use

1. In somaNotes, select the destination patient first and verify the displayed name and MRN.
2. In that same patient's Epic chart, insert .somasnapshot in an organization-approved scratch or documentation workspace. Add only the relevant signed consult/nursing narrative and any decision-relevant lab trends at the two stops.
3. Review the rendered snapshot, copy it, then return to somaNotes → Add Data.
4. Set Service Date to the clinical day represented by the data, paste once, and choose Process & Save.
5. Before moving on, verify the selected patient did not change and scan Parsed Results for obvious omissions or misclassified values.

Department SmartText upgrade ticket

Once the personal phrase works, send this narrower request to the Avera build team instead of asking them to implement unverified names.

How to read this

The three-stage roadmap

Stage 1 is entirely in your hands today. Stages 2 and 3 need a builder ticket — this page gives you copy-ready request text for both.

Quick start — for physician partners

The strict structured phrase preserves every required v3.5 section and uses eleven visible F2 stops. Date of Service and Objective stay clinician-controlled until Avera validates compact, context-correct SmartLinks. The exact-note fast path pastes the complete canonical note as one normalized document without relocating sections.

One-time setup in Epic (~10 minutes)

1. In Epic: Epic button → Tools → SmartPhrase Manager (or type "SmartPhrase Manager" in the toolbar search).
2. Click New. Name it DISPO5 — exactly that, no leading dot (Epic adds the dot). Build this one first: the master phrase references it by name, so it has to exist before the master phrase can nest it.
3. On this page, scroll to Nested phrase, hit Copy, paste the block into Epic's compose box, save. Leave every *** exactly as triple-asterisk — Epic natively treats it as a fillable stop.
4. Create SOMAPROBLEM35 from the repeatable problem block. Keep it standalone; invoke it as many times as the patient needs.
5. Create SOMAPROGRESS35 from the structured master.
6. Optional: create HOSPPROGRESSPASTE35 from the exact-note fast path. It contains one wildcard and never relocates Date, Vitals, Chronic Stable, or Code status.
7. Open a note on a test/training patient and type .somaprogress35. Confirm every canonical header appears in order and .DISPO5 unfolds at the bottom.
8. Confirm @CODESTATUS@ resolves in this note type. If it renders literally or as bare @@, delete it and reinsert the matching SmartLink through Insert SmartLink.
9. Practice the keys: F2 jumps to the next *** stop, Shift+F2 goes back.
10. Resolve or delete every wildcard, verify the five disposition lines, and confirm no content follows Follow-ups before signing.

Daily use

1. Generate the note in somaNotes; copy it; paste it into the paste chain on this page.
2. Fast path: click Copy full canonical note, then paste into a blank Epic progress note or the single stop in .hospprogresspaste35. Copy full is enabled only when the canonical v3.5 structure is present.

For section-level control with visible Epic sign-blocking stops:

1. In Epic, type .somaprogress35.
2. F2 to the first stop → click Copy next here → Ctrl+V in Epic → F2 → repeat. The button names each chunk as you go and stops at "All chunks copied".
3. A missing Chronic Stable value is not optional: enter None. Generated Disposition may contain only the supported fields, so an omitted Disposition value is not a rail placeholder; the static .DISPO5 phrase still leaves its physician-fillable *** stops for you to complete or clear before signing.
4. Cross-check the note's Code status reference against the value rendered by @CODESTATUS@.
5. Sign.

Upgrade a wildcard only after the candidate output passes the Avera training-patient checks below. Index presence alone is not enough.

Paste chain — split a generated note now

Paste the full somaNotes progress note here. Canonical v3.5 notes split into the exact eleven wildcard stops used by .SOMAPROGRESS35. Legacy headings are recognized only to help migrate old text; Copy full stays disabled until the canonical structure is present.

The deterministic copy gate checks exact headers and spacing, CC shape, one-paragraph Course Summary, three-paragraph Subjective, ordered Objective subsections, numbered A&P problem blocks with 1–4 supported actions (up to 6 for Worsening), one-line Chronic Stable, ASCII-safe text, and a final Disposition containing any supported subset of its five fields in canonical order. The bare final DISPOSITION heading may be empty; present fields may not be empty, duplicated, invented, or reordered. It is a paste-safety check, not a substitute for clinical review.

Runs entirely in this tab — nothing you paste is uploaded, stored, or logged. Reload the page and it's gone.

Structured master — canonical v3.5

The Subjective stop receives all three required paragraphs. The Objective stop carries Vitals, timestamped Labs, optional Imaging/Microbiology/Pathology, and Exam in v3.5 order. The A&P stop preserves the opening synthesis plus any number of #n Problem [Status] blocks. Chronic Stable stays separate and must contain a pipe-delimited line or None. Date and Objective remain visible stops until Avera proves replacement SmartLinks in this note context.

Repeatable problem helper

First stop: number. Second: concise problem name. Third: exactly Worsening, Active, Improving, Stable, or Resolved. Fourth: a 2–4 sentence assessment. The static helper seeds two physician-fillable action rows for convenience, but generated problems need only one supported action; delete an unsupported extra row rather than padding it. Keep this helper standalone and invoke it repeatedly when authoring the A&P manually.

Nested phrase

Built standalone so the canonical master can nest it. This static physician-fillable phrase intentionally keeps all five lines and every *** hard stop; generated rail output separately emits only supported Disposition fields. Under therapeutic anticoagulation, document that supported state as the DVT value rather than suppressing it.

Exact-note fast path — .HOSPPROGRESSPASTE35

Paste the complete canonical v3.5 note into one wildcard. This phrase intentionally adds no wrapper: moving Date, Vitals, Chronic Stable, or Code status outside the generated document would violate the immutable section order.

Copy full canonical note returns the normalized complete note. It never reconstructs the document from chunks and remains disabled for noncanonical legacy input.

Captured in our build — existence is not output proof

The captured Avera index proves that a name exists, not that it renders the right semantics, time window, shape, or label in this progress-note context. The strict master therefore hardwires only @CODESTATUS@, which also has signed-note round-trip evidence.

This is a small fraction of what the build actually has. Treat it as a discovery list. Every candidate still needs a training-patient expansion test before it replaces a visible wildcard.

Baseline and candidates

Labs — the .LL family (this build's version of the Foundation lab links)

The .LL family is an optional discovery aid, not part of the canonical baseline. Use a specific lab link only after its Avera expansion stays compact and preserves the Objective ordering; prune anything over the <5-lines rule below.

Also captured in the index — validate output before use

Stage 1 — candidate discrete-data SmartLinks

The baseline wildcards are deliberate. Of the outbound fields, only @CODESTATUS@ has signed-note output proof. Treat every other captured name and catalog entry as a discovery lead until it expands correctly on a training patient in this exact progress-note context.

Promote a candidate into a *** stop only after checking its meaning, time window, timestamp, compactness, oxygen-device handling where relevant, and whether it prints its own label. Mnemonics, parameter order, identifiers, and context availability can vary by Epic build; use the in-note help text and insert/search tools rather than typing an identifier from this page into production.

Labs — trended & most-recent values

Flowsheet rows — the workhorse for Objective data

Imaging — impressions only

Micro / culture & sensitivity

Meds, allergies, problems, diagnoses

Stage 2 — make the dispo schema discrete (builder ticket)

A plain SmartList only inserts text. It becomes a discrete-data capture tool when its record has "use discrete data" enabled and its options are mapped to a SmartData Element (SDE — HLX master file; values stored in HLV). This is the mechanism that turns a VTE-ppx or code-status pick into reportable, auditable data instead of dead text in a note — and it's the clearest safety/quality payoff of anything on this page, since code-status confirmation and VTE prophylaxis are Joint Commission core-measure territory.

Mechanical constraint: an SDE cannot link directly to a SmartPhrase — the phrase must contain an SDE-linked SmartList (or a SmartForm/NoteWriter block) to actually file discrete data.

For a value already captured elsewhere in the chart that you just want to display inline (not re-capture), the retrieval tools are CUIPAT (patient-level), CUIENC (encounter-level), and CUIEPI (episode-level), with option flags N (label only if a value exists), L (always show label), M (message if no value), and B (break to a new line only if data exists — lets you stack several SDE links without blank-line gaps). DBLINK retrieves arbitrary master-file items. These are builder-level tools, illustrated (not literal for your build) below:

Copy-ready request for your informatics/Bridges team:

Stage 3 — conditional logic: the reality

Epic has no inline .if/.el/.end or @if@...@else@...@endif@ token inside SmartPhrases or SmartText. Branching output is delivered only through CER-rule-driven SmartLinks:

• RULESMARTLINK / RULESMARTLINKREFRESH (HHS 60402 / 60404) — displays information based on a rule record. Documented parameters, verbatim: "Parameter 1 - Enter the ID number of the rule to evaluate. Parameter 2 - Enter the mnemonic of the SmartLink to display if the rule is true. Parameter 3 - Enter the mnemonic of the SmartLink to display if the rule is false," plus formatting flags in parameters 4–7.
• CERMSG / CERMSGREFRESH (HHS 64343 / 14042) — evaluates one or more CER rules and returns either the rule's error message or specified SmartTexts.

A CER rule is a configurable rule-logic record evaluated as TRUE/FALSE. Building rules (CER) and new SmartLinks (HHS) is typically restricted to project-team members — you'll need physician-builder access or your informatics/Bridges team, and every rule should be validated with the Rule Tester before it goes live.

Lower-effort partial conditionality that doesn't need a CER rule: SDE display flags can self-suppress optional content inside an existing section. They must never suppress one of the five required Disposition lines.

Copy-ready request for your informatics/Bridges team:

If you want to own this logic directly instead of ticketing it every time, Epic Physician Builder certification (e.g. CLN150-level coursework) is the fastest route — it's the credential that grants CER-rule and HHS SmartLink build access.

What NOT to add

The same anti-boilerplate discipline that governs somaNotes' own generated text (nothing ungrounded, nothing the doctor didn't ask for) applies to the Epic side of this template too:

• Reflexive line-day counts, generic goals-of-care language, and "defensive" normal-template prose add volume without discrete value — leave them out.
• Let empty fields self-suppress (the SDE M/B flags from Stage 2) instead of printing "none" or "n/a" on every field, every note.
• Benchmark to change course: if a given SmartLink dumps more than ~5 lines of noise, or frequently returns stale/blank data, drop it or narrow its lookback window — don't keep it "just in case." A published intervention that cut routine lab-SmartLink use from over 90% of notes to under 18% shortened notes in the process (see Evidence, below) — pruning auto-imported data is the empirical win, not a compromise.

Field crosswalk

Discovery & verification workflow (do this before building anything)

1. In-note help text: type the dot-command (e.g. .LASTLAB, .FLOW) and read the *** HELP TEXT *** it returns — it lists your build's exact parameters.
2. SmartLink/SmartList search: in SmartPhrase Manager or the SmartTool editor, type . plus a few letters to search available SmartLinks. Check the link's available contexts — a link that renders as bare @@ isn't evaluating in that context; make it available to all contexts if you need it everywhere.
3. FLO IDs: the .FLOW+Tab picker (newer Epic versions), the Report & Print Group Assistant's "Debug Print Group," or right-click a flowsheet cell → Properties.
4. SDEs: SmartData Manager (searchable; supports category: / sws: search syntax).
5. CER rules & new HHS SmartLinks: require physician-builder privileges or your informatics/Bridges team — validate with the Rule Tester before deploying.
6. Cross-org portability: SmartPhrase Manager can upload/download personal SmartPhrases and SmartLists between organizations, but IDs won't translate across sites — re-verify everything if you move builds.

Stage 1 upgrade path (after the baseline works)

1. Swap any wildcard for a SmartLink from the catalog above once you've verified its mnemonic/ID for our build via the discovery workflow.
2. In .DISPO5, click into the DVT ppx wildcard, use the toolbar's Insert SmartList, search "VTE prophylaxis" or "DVT," pick our build's list. Epic resolves the real ID — you never type one.
3. Stage 2/3 aren't self-service — file the copy-ready request text above with the informatics/Bridges team and reference this page.

Evidence for the discrete-data-first approach