Epic ClinDoc Explained: Inside Epic’s Inpatient Documentation Module

Posted in EPIC

Epic ClinDoc is the inpatient documentation module inside Epic’s EHR, and for most hospital nurses it is where the largest share of their EHR time goes. KLAS put Epic at 56.9% of U.S. acute care beds in its 2026 market share report, covering contracts through December 2025, so ClinDoc is the most widely deployed inpatient documentation system in American hospitals. This guide covers what the Epic ClinDoc module includes, how it differs from Epic Ambulatory and Epic Orders, where its data ends up, how ambient AI started changing it in 2026, and what nurse informaticists, analysts, and integration teams should know before they build on it or connect to it.

What is Epic ClinDoc?

Epic ClinDoc is the clinical documentation application within EpicCare Inpatient. Epic splits inpatient work into two applications that share one chart: ClinDoc, which handles nursing and clinician documentation, and Orders (Inpatient Orders, or CPOE), which handles order entry and management. Hospitals usually license them together and end users rarely notice the seam, but the build, the certification tracks, and the analyst teams are separate, which is why many analysts end up certified in both.

If a bedside clinician records something during a hospital stay, it almost certainly lands in a ClinDoc record: the flowsheets where vitals and assessments go, the navigators that walk a nurse through an admission or discharge, the medication administration record, care plans, notes, and the nurse’s task list.

You will see the module called ClinDoc, Inpatient ClinDoc, IP ClinDoc, or just EpicCare Inpatient in job postings and Epic documentation. Many organizations also run ClinDoc documentation in emergency, rehab, long-term care, and behavioral health units, since those areas document in flowsheets and navigators the same way a medical-surgical floor does.

	Epic ClinDoc	Epic Orders
What it covers	Nursing and clinician documentation: flowsheets, notes, care plans, MAR, lines and drains, navigators	Order entry and management: order sets, CPOE, order questions, transmittal to ancillary systems
Who documents in it	Nurses first, then hospitalists, therapists, case management	Physicians and advanced practice providers; pharmacists verify in Willow
Analyst certification track	Inpatient ClinDoc	Inpatient Orders
Where the two meet	The MAR shows what Orders placed; navigators embed order reconciliation	Order sets can trigger care plans and required documentation in ClinDoc

Epic ClinDoc: What Clinicians Use Every Shift

The module is less a single screen than a set of activities that share the patient’s chart. These ones shape a nurse’s day.

Flowsheets

Flowsheets are time-stamped grids for vital signs, intake and output, assessments, pain scores, lines and drains, patient education, and anything else a unit decides to capture in discrete rows. They are the workhorse of nursing documentation and the single largest source of documentation burden. A 2018 AMIA study by Collins and colleagues found nurses making 631 to 875 manual flowsheet entries per 12-hour shift on acute care units, roughly one data point per minute, before device feeds were counted. A 2025 study at NYU Langone Health put flowsheet time at 31.11% of a 12-hour shift, using EHR vendor time data from February 2023. Good flowsheet build (fewer required rows, sensible groupings, cascading rows that appear only when a prior answer makes them relevant) is where a ClinDoc analyst earns their keep.

Doc Flowsheets extend the same grid to structured procedural and specialty documentation. Device integration pushes monitor, ventilator, and pump data into the same rows through a Data Validate activity, so the nurse confirms a reading rather than retyping it.

Navigators

Navigators string activities together in the order a workflow needs them. The admission navigator collects history, screenings, belongings, and medication reconciliation. The discharge navigator assembles the medication list, After Visit Summary, and follow-up instructions, and tracks discharge milestones and delays. Units add their own: pre-procedure checklists, restraint documentation, transfer handoffs. A well-built navigator is the difference between a nurse remembering fourteen admission tasks and the system remembering them.

Notes and SmartTools

Physicians, advanced practice providers, and nurses write H&Ps, progress notes, procedure notes, and shift summaries in the Notes activity, usually through NoteWriter templates. SmartTools do the assembly work: SmartText for templated note bodies, SmartPhrases for personal or shared shortcuts, SmartLinks that pull live data such as the last set of vitals or the active medication list into the text, and SmartForms for structured data capture inside a note. Organizations tend to accumulate large libraries of these over time, and pruning them is a standing optimization task.

The Brain, Worklists, and the LDA Avatar

The Brain is the nurse’s home screen in ClinDoc: a shift timeline of due medications, scheduled assessments, tasks, and results across the whole assignment. It replaced the older habit of hopping between patient lists and activities. The LDA Avatar sits alongside it, a body diagram where lines, drains, airways, and wounds are placed, assessed, and removed. Both are standard stops in inpatient nursing training, which is why ClinDoc onboarding for new nurses usually starts with them.

The MAR and Barcode Administration

The Medication Administration Record is where each dose is documented as given, held, refused, or missed, with time, route, site, and the administering user attached. Barcode scanning of the wristband and the medication happens at a workstation or on a handheld, and the scan either confirms the five rights or fires a warning. Epic Rover extends the same scan-and-document workflow to a handheld at the bedside.

Care Plans and Interdisciplinary Documentation

ClinDoc care plans tie nursing problems (fall risk, impaired skin integrity, pain) to goals and interventions. The same structure is open to therapy, dietary, case management, and chaplaincy, so the plan of care is one document rather than five. Templates can be assigned automatically by admitting diagnosis, unit, or assessment result, and the care plan feeds the handoff report and the end-of-shift note.

Communication and Handoff

Secure Chat and In Basket handle messaging inside the chart. Handoff tools pull current status, pending results, and open care plan items into a shift-change summary (I-PASS or SBAR formatted, depending on the build) so the incoming nurse sees what the outgoing nurse saw. The structured handoff is meant to replace the paper report sheet, though plenty of units still keep one alongside it.

Decision Support and Safety Controls

Best Practice Advisories fire on documented values: a sepsis screen from vitals and labs, a fall-prevention prompt from a Morse score, a pressure-injury bundle from a Braden score. Break-the-glass access, audit trails, and role-based security apply to ClinDoc the same way they apply to the rest of the chart; our guide to Epic EHR security features covers those controls.

Epic ClinDoc vs Epic Ambulatory

The two documentation applications look similar in Hyperspace and share SmartTools, which is why “does Ambulatory experience transfer to ClinDoc?” comes up so often in analyst hiring. The honest answer is partly.

	Epic ClinDoc (inpatient)	Epic Ambulatory (outpatient)
Care model	Continuous, 24/7, shift-based	Episodic, appointment-based
Primary documenters	Nurses first, then physicians and therapies	Physicians and APPs, with MA or nurse rooming
Core artifacts	Flowsheets, MAR, navigators, care plans, the Brain	Visit navigator, SmartSets, problem-oriented notes, e-prescribing
Documentation volume	Hundreds of discrete flowsheet entries per shift	One note plus orders per visit
Inbound data	Monitors, ventilators, pumps, barcode scans	Patient questionnaires, MyChart, remote monitoring devices
Handoffs	Every shift change	Rare outside referrals
Build emphasis	Flowsheet rows, required documentation, nursing decision support	Visit templates, SmartSets, order preference lists

How Epic ClinDoc Connects to the Rest of Epic

No ClinDoc build stands alone.

• Grand Central: ADT events (admit, transfer, discharge). Prelude sits upstream of it, handling registration, patient identity, and insurance coverage. 
• Willow: Verifies orders that appear on the MAR. 
• Beaker: Lab results land in the chart and flowsheet rows. 
• Radiant / OpTime: Imaging and perioperative documentation hand off when the patient leaves those areas, such as PACU to the floor. 
• ASAP: Carries ED documentation forward on admission. 
• Stork: Labor-and-delivery flowsheets share ClinDoc’s structure. 
• MyChart Bedside: Patient-facing schedule and care-team view. 
• Care Everywhere: Brings outside records in.

Our complete guide to Epic modules maps where each of these sits; for the platform as a whole, start with what the Epic system is. 

Where Epic Data Goes

Every flowsheet value, MAR action, and signed note is written to Chronicles, extracted to Clarity overnight, and modeled in Caboodle. That is the path nursing quality data takes. Falls, pressure injuries, CLABSI and CAUTI bundle compliance, restraint hours, and pain reassessment timeliness all come from ClinDoc rows. Regulatory reporting depends on the same path: CMS electronic clinical quality measures and Joint Commission chart audits read documented values, not intentions. Researchers use it too; a 2025 study of flowsheet macros measured nurse documentation time directly from Caboodle.

Our Epic Cogito guide explains the Clarity and Caboodle layers in detail. For organizations combining ClinDoc extracts with non-Epic sources, Folio3’s healthcare data analytics services cover the warehousing and modeling side.

One practical warning. Flowsheet rows that get renamed, retired, or duplicated during an optimization project break downstream reports unless the analytics team is told. Every change to a ClinDoc build should carry a “which reports read this row?” check before it goes to production.

Ambient AI and Epic ClinDoc in 2026

Documentation burden was the main complaint about ClinDoc for a decade, and 2026 is the first year the module itself started to answer it. In February 2026, Epic released AI Charting as part of Art, its clinician-facing assistant. It listens to the encounter, drafts the note inside the chart, and queues orders for review. That first release targeted physician encounters rather than inpatient nursing documentation. Bedside nursing workflows followed a few months later. Mount Sinai Medical Center in Miami Beach turned Chart with Art on for inpatient nurses in July 2026, the fourth U.S. health system to do so, with the tool drafting care plan documentation in English and Spanish that a nurse reviews before it enters the record.

Separate from ambient listening, Art also drafts end-of-shift care plan summaries from data already in ClinDoc: vitals, flowsheets, MAR, orders, and prior notes. At Mercy, one of the fifteen largest U.S. health systems, Epic reports that end-of-shift note time fell from 3.5 minutes to about 32 seconds and on-time completion rose 225%. Epic’s chart-summary Insights feature is now used more than 16 million times a month.

Two things follow for anyone running ClinDoc. First, the review step is the control. Nothing enters the legal record until a clinician signs it, so organizations need policy on who reviews AI-drafted nursing documentation, how edits are audited, and how patients are told the tool is running. Second, third-party ambient scribes still write into ClinDoc through Epic’s APIs, so the integration and governance questions are the same whether the model is Epic’s or a vendor’s.

What It Takes to Run Epic ClinDoc Well

The software ships with Epic. The program does not. A few realities separate calm ClinDoc environments from noisy ones.

Documentation burden is a build problem before it is a culture problem. Every required flowsheet row, hard stop, and advisory was added by someone for a reason that may no longer apply. An HHS graphic on EHR time puts nurses at up to 41% of their time on EHRs and documentation, a summary figure rather than a dated study, so treat it as directional. Mature organizations run periodic required-documentation reviews with nursing leadership and retire rows nobody reads.

Training is role-specific and delivered by the hospital. Epic ClinDoc training for end users usually combines e-learnings with classroom or lab time, followed by super users on the floor at go-live. Epic’s credentialed trainer program prepares the hospital’s own trainers, and a playground environment lets nurses practice against test patients before they touch a live chart. Training that focuses on clicks instead of a unit’s real workflows tends to produce workarounds quickly.

Analysts need Epic ClinDoc certification, and the route runs through a sponsoring organization. Epic does not sell certification to individuals. A hospital or consulting firm sponsors the analyst, who completes Epic’s coursework, a build project, and exams for the Inpatient ClinDoc track, often paired with Orders. Proficiency, a lighter credential available to staff at Epic customers, is a common first step. Our guide to how much Epic costs covers what certification typically runs and who pays for it.

Optimization never ends. Epic’s quarterly releases change ClinDoc activities, ambient tools are arriving unit by unit, and every specialty wants its own flowsheet. Budget for a standing ClinDoc team rather than a go-live project. The list of hospitals that use Epic shows the scale at which this work now happens.

Integrating Devices and Apps With ClinDoc

For device makers and digital health vendors, the practical question is how their data gets into ClinDoc and how they read it back.

• Inbound device data (monitors, pumps, ventilators, wearables) typically arrives as HL7 v2 ORU messages or through Epic’s device integration, lands in flowsheet rows, and waits for a nurse to validate it.
• Outbound, FHIR R4 resources such as Observation, MedicationAdministration, CarePlan, and DocumentReference expose flowsheet values, MAR events, care plans, and notes to SMART on FHIR apps, subject to the organization’s app review and security process.
• Decision support apps can return results to the workflow through CDS Hooks, and ambient documentation vendors write draft notes back through the same API layer.
• Most of the engineering effort is mapping: which flowsheet row, which LOINC code, which unit of measure, and which documentation event should trigger an outbound message.

The organization, not the vendor, owns the build decisions on the Epic side, so any integration project needs a ClinDoc analyst in the room from the first requirements session.

Working With Epic ClinDoc Data? Folio3 Digital Health Can Help

Most Epic ClinDoc integration projects stall in the same place: the mapping. The device vendor knows its data, the hospital’s analyst knows the flowsheet rows, and nobody owns the space between. Folio3 Digital Health works in that space as a member of Epic’s Vendor Services program. We build the HL7 v2 and HL7 FHIR connections that put device readings into the right ClinDoc flowsheet rows, expose MAR, care plan, and note data to SMART on FHIR apps, and carry it through to Caboodle for reporting, with HIPAA compliance designed into the first interface spec rather than checked at the end. If your app or device needs to live inside a nurse’s shift, that is the work we do.

Closing Note

Every hospital running Epic’s inpatient suite is running ClinDoc, whether the org chart says so or not. It is the layer where clinical work becomes a legal record, a quality metric, and a billing event, all from the same keystroke. AI is changing how that record gets written in 2026, not what it’s for. Understanding ClinDoc, its build, its data path, its review controls, is table stakes for anyone building on Epic, not a nice-to-have.

Frequently Asked Questions

1. Is ClinDoc Epic’s nursing module only?

No. ClinDoc Epic documentation is nurse-heavy, but hospitalists write progress notes in it, therapists and case managers document in its care plans and flowsheets, and rehab, long-term care, and behavioral health units use the same tools.

2. What is the difference between Epic ClinDoc and Epic Orders?

ClinDoc is documentation; Orders is order entry. They share one chart and one Hyperspace session, but they are built by different analysts and carry separate Epic certifications. The MAR is where they meet: Orders places the medication, ClinDoc documents that it was given.

3. How do you get Epic ClinDoc certification?

Epic ClinDoc certification is earned through a sponsoring organization, usually a hospital that runs Epic or a consulting firm. The analyst completes Epic’s Inpatient ClinDoc coursework, a build project, and exams. Individuals cannot buy the certification directly, though staff at Epic customers can pursue a proficiency credential first.

4. Which Epic applications does the Epic ClinDoc module work with?

The Epic ClinDoc module exchanges data with Grand Central (ADT), Prelude (registration and coverage), Willow (pharmacy), Beaker (lab), Radiant (imaging), OpTime (surgery), ASAP (emergency), Stork (obstetrics), MyChart Bedside, and Care Everywhere, and its data flows to Clarity and Caboodle for reporting.

5. Can third-party apps read and write ClinDoc data?

Yes, within the organization’s governance. Device data enters through HL7 v2 or Epic’s device integration; apps read flowsheet values, MAR events, care plans, and notes through FHIR R4 resources and SMART on FHIR, and can return decision support through CDS Hooks.

About the Author